Coming
Review requests start a review agent first. You review when it's ready.
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.
ComingNot built yet. Unlocks with a triage agent you start with a slash command.
An ask comes in. A fix is waiting for your review.
Someone posts "the export button 500s" in Slack. Coming next, a triage agent reads the channel through the Slack MCP server your team already runs, files the ask once, and starts an agent on it in its own worktree.
When the fix is done and checked, it will wait in the Activity panel for you. Approve it and the reply goes back to the thread.
How it goes
From the moment it starts to done. Each flow carries its own label.
Asks from Slack, Jira and GitHub
Alerts
The Activity panel tells you what needs you
Beta Needs an agent that posts to Activity
The Activity panel lists what you owe your agents and what they owe you, with a count of what needs you and a notification when you’re away from the app.
Activity is a tab in the right pane. It sorts the work into what you owe your agents, what they owe you, what's on an agent, what's parked, and what's done and waiting for you to look.
- You owe a review, an approval, a decision
- Owed to you results an agent owes you
- On the agent work an agent is doing now
- Parked waiting on something else
- Done finished, not yet looked at
Rows come from agents that report to Activity. Sessions you run yourself don't add rows yet.
What's real today
What ships, what needs setup, and what isn't built yet.
Coming Not built yet
Limits today
- Where we’re behind: agents run on your machine only; routines run only while the app is running; Claude Code and Codex are built in while other tools launch more agents from their own UI; no open-a-pull-request button yet; no enterprise identity, roles or central audit; sessions don’t survive quitting the app yet.
Read more
Try it on your own repos, with your own agents.