The code review verdict as a build status. On request, a code review routine sets its verdict as a build status on each commit it reviews, so your merge check can wait for Gunnie.ai’s review.
Approvals that ran out of time are hidden by default and can be shown on request; they can no longer be approved or rejected.
Roles shows which tools wait for approval before they change anything.
Try again when a page or a number could not be loaded, and Clear filters when a filter matches nothing.
From the keyboard: Skip to content on every page of the control panel, and the arrow keys move through the call log.
Deactivating a member asks first, and says it can be undone.
21 October 2026
Code review picks its pull requests. Narrow a code review routine to pull requests into chosen branches, or to those whose Jira ticket is in a chosen status such as Code Review. A pull request is reviewed again only when it has new commits.
A review queue. Reviews that cannot start yet wait their turn and start on their own; Routines and Reviews show them as Queued, with the reason.
Code reviews at a glance. A code review routine shows its repositories, the budget left and its last results with the verdict and findings per level. Reviews shows the pull request of every review, filters by status and repository, and links a routine’s review to its result.
A Slack post per review, with the verdict and how many findings, and on request a review that is posted on the pull request after someone approves it.
Clearer pages. Plain error messages, empty pages that say what will appear there, keyboard access to every list, stronger contrast, and every page fits a phone.
19 October 2026
More code hosts and trackers. Connect GitHub or GitLab as your code host, and Linear as your issue tracker; the same tools and routines work on them.
Sample data. A new organisation can try everything on a made-up shop, Northwind Outdoor, before connecting its own systems. A banner says so on every page.
New routines. Definition of ready checks tickets before refinement and proposes what to add; Standup digest prepares the daily standup; Release risk assesses the next release; QA pre-check opens the test environment’s pages with screenshots before a tester looks.
Code review results in the panel. A routine’s review is kept with its run, with findings by severity and the acceptance criteria met, not met or unclear. A review you start yourself shows its findings to you for two hours.
A first-login tour for admins and members, and a home page per role: the organisation overview for admins, Get started for members.
18 October 2026
Routines that propose, and approvals for every write. Pre-refinement, team estimation and the other routines turn their work into proposals; nothing is written until someone approves it. Approve one at a time or all proposals of a run after a confirmation. Admins can decide every member’s proposals.
Routines start when a ticket enters a status, besides on a schedule or a new pull request. Each routine shows when it runs next, what it is doing, and its last five results.
Tools and roles for the whole product team. New roles: product owner, business analyst and designer. New tools for sprints, the backlog, epics, releases, ticket history and dependencies, code status and pipelines, Confluence pages, and changes such as comments, status moves, field changes, sub-tasks and links, all after approval.
Value and an organisation home. Admins see calls, approvals waiting, spend and routines at a glance, with a setup checklist, and a Value page with the estimated time saved and its assumptions.
Get started and these docs. Every member has a page with the connector address, the steps in Claude and questions for their role, and this documentation explains connecting, asking, approvals, routines and the admin’s work.