Available now
Day one, they just start working.
Every agent a new engineer launches gets the team's skills, agents and instructions, so it works your team's way from day one.
Seven jobs, in the order of a team's week: from a new engineer's first day to the fix that's waiting for your review. Labels say what's real today.
Available now
Every agent a new engineer launches gets the team's skills, agents and instructions, so it works your team's way from day one.
Available now Beta
Write each team convention as a skill once. Every agent whose context includes it gets it as a real file, in any repo; Claude Code agents do by default. In Beta, an agent publishes improvements back.
Available now
Stories are markdown or HTML files you or your agent write. CodeSense links them across epics and keeps one sprint across every repo.
Available now Coming
Click a story and its agent starts in the story's own worktree with your team's context. Coming next, a manager agent starts an agent on each ready story.
Coming
Coming next, a review request in Slack starts a review agent on the PR in its own worktree, with your team's review skill, while CodeSense is running.
Coming
Coming next, an ask in Slack, Jira or GitHub is filed once and handed to an agent in its own worktree. The fix waits for your review, and the reply goes back to the thread.
Available now
Open the ready-made sprint dashboards, or write a page over your plans and the results your agents’ routines publish.
A use case with more than one label shows each flow with its own, so you can see which part works today.