Coming
An ask comes in. A fix is waiting for your review.
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 nowShipped, and it works on a fresh install with the default settings.
Your team's view of the sprint isn't Jira's, and it isn't GitHub's.
Start from the ready-made sprint analysis and kickoff console, or write the page you want, such as blocked stories with their PRs and tickets: an HTML page that reads your plans and your agents’ routine results.
Your agents fetch outside data with their own tools and publish it as a routine result. The page reads that result and never sees a token.
It's a file in your team's context repo, versioned in git like the rest of it.
From the moment it starts to done. Each flow carries its own label.
<meta name="cs:type" content="dashboard">
<h2>Blocked stories</h2>
<ul id="blocked"></ul>
<script type="module">
// In a trusted workspace, reads need no grant.
if (window.codesense) {
const res = await window.codesense
.queryContext({ where: { kinds: ["story"] }, match: { status: "blocked" } })
.catch(() => null);
document.getElementById("blocked").replaceChildren(
...(res?.rows ?? []).map((d) => Object.assign(document.createElement("li"), { textContent: d.id })),
);
}
</script> What ships, what needs setup, and what isn't built yet.
Try it on your own repos, with your own agents.