Repository navigation
v0.5.0
Projects group issues from any team toward a goal, and what agents propose has a page of its own. Updating a self-hosted copy applies a migration in each workspace's database, which runs on its own; there is no D1 migration this time.
Added
- Projects. A project groups issues from any team toward a goal, with a description, a status (planned, started, paused, completed or canceled), a lead, a target date and its progress: the issues done out of all that are not canceled. Projects have a list and a page with their issues as a list or a board, every issue has a Project property, and the command palette goes to them, creates them and sets them. People create and edit projects, admins delete them, and an admin can have an agent member only propose project changes. (#53)
- MCP:
create_issue,update_issueandsearch_issuestake aproject, by name or id, andget_workspacelists the projects. (#53) - A Proposals page lists the workspace's open proposals by issue, with a count in the sidebar, a filter by agent kept in the URL, and keys to move between them (J and K), accept (A) and dismiss (D). (#52)
- Webhook events for proposals:
proposal.created,proposal.updated,proposal.acceptedandproposal.dismissed. An agent's own webhook is sent a person's decision on what it proposed, and not its own proposals. A new webhook leaves them off until they are chosen. (#51)
Changed
- The sync protocol is at version 6, for projects. Open tabs fetch their workspace again after the update. (#53)
Fixed
- A tab left open on an older version no longer keeps a tab opened after an update on "Loading…". Tabs now pick the one that holds the connection among tabs of the same version. (#54)
Full changelog: v0.4.0...v0.5.0