Repository navigation
v0.4.0
People stay in control of what agents do: an admin chooses which kinds of change each agent member only proposes, and people accept or dismiss them. 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
- Proposals. Under Settings, Agents, an admin picks for each agent the kinds of change it only proposes: title, description, status, closing (as Done or Canceled), priority, assignee and labels. The server holds those back, even on a new issue the agent creates, and shows them on the issue under "Proposed by agents" with Accept and Dismiss. Accepting makes the change as the person who accepted it, and the history notes which agent proposed it. An agent has one open proposal per field and issue, and agents never decide on proposals, their own included. An agent proposes nothing until an admin sets it up, so existing agents work as before. (#49)
- MCP:
create_issueandupdate_issuereturn what they proposed underproposed, so an agent knows the change waits for a person, andget_issuelists an issue's open proposals. (#49)
Changed
- The sync protocol is at version 5, for proposals. Open tabs fetch their workspace again after the update. (#49)
Full changelog: v0.3.0...v0.4.0