v0.3.0

Agents that work on their own: they join a workspace under their own name, and webhooks tell them about changes as they happen. Updating a self-hosted copy applies a new D1 migration (pnpm run deploy does it) and a migration in each workspace's database, which runs on its own.

Added

• Agent members. An admin creates one under Settings, Agents for an AI agent that works on its own, such as one that triages new issues. It joins the workspace with the new agent role, connects to MCP with a key instead of signing in, and reaches that one workspace only. It can do what members do and nothing only admins can, and everyone sees its changes as its own. (#45)
• Webhooks. Admins add them under Settings, Webhooks: each change (an issue created, changed or deleted, a comment added, edited or deleted) is posted to a URL, signed per Standard Webhooks, and retried for about 17 hours while the receiver fails. A webhook can be limited to one team, and one made for an agent is not sent the agent's own changes. Each workspace's Durable Object sends them, so there is no new binding to set up. (#46)

Changed

• The sync protocol is at version 4, for the new role. Open tabs fetch their workspace again after the update. (#45)

Full changelog: v0.2.0...v0.3.0