Projects now belong to a team. What was set up per project is set up once on the team, and every project of the team uses it: A team has owners, managers, and members. An invite can reach a team, and SCIM provisions team membership. God mode has a Teams…
Specs, notes, and decisions now live next to the work they describe. Pages nest into a tree, keep their version history, and can stay private. A page and a work item link both ways. Recurring work no longer gets retyped. A template fills a new issue with its…
An instance connects to one OIDC provider — Keycloak, Authentik, GitLab, Okta, Entra, or any other standard one. SCIM 2.0 lets the provider create, update, and deactivate accounts, and map its groups to project membership. An owner can then turn off email and…
A project turns on story points, time, or both in Settings → Configuration. The kinds you turn on appear in the issue properties, and you can show them on the cards, the rows and the Table columns. Time accepts 1h 30m and reads back the same way. The activity…
The full chat page and the floating chat are replaced by one panel. The panel stays open while you move between the pages of a project, so you see the work and the chat together. It holds several sessions as tabs: open a tab from the history, rename it, drag…
The GitHub integration is now a repository integration. GitLab, Gitea, Forgejo and Bitbucket send their pull request events to the same URL. Your automations work with all of them: magic words, move on merge, move on open. An agent can draw a chart in its…
Every account now has a username next to its email address. It is derived at sign-up from the address, the owner changes it on the profile page, and the sign-in screen takes either identifier in one field. An address is not something people want to type or…
An external agent can now answer in the chat, the same as an internal one. Before this it could only take an issue by a mention or a delegation. The answer arrives while the coding agent writes it, and the tools it calls appear in the transcript with the…
support deploying outside the compose stack ( #151 ) ( 6245e8d )
An agent can now run on a machine that you control, with your accounts and your model keys. This can be your laptop, a server or a VPS. Install the @itsaplan/runner package and start it. It takes the tasks of the agent and sends each one to Claude Code…