Highlights
Usernames
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 show to a team.
Replies in an issue thread
A comment and the answers under it now render as one card, and the feed keeps a thread whole across pages. Agents take part in the same threads: a mention deep in a thread carries the comments above it into the run prompt, and the agent answers in the thread.
Mentions by @username
A mention is now written as @username — a person by their account username, an agent by its
username in the project. The old mention carried a user id, so only the picker could produce
it. A handle is typed by hand and reads the same in the editor, the raw markdown, the API and
the agent prompt.
The agent form
The form where you create and edit an agent was reworked for easier use, with a clearer navigation between its sections. The action, skill and tool lists are grouped and filterable. Instructions are now written in the markdown editor, so a long system prompt is as comfortable to write as an issue description. An external agent's API key has its own section in the form.
Also in this release
- Markdown tables are rendered with borders everywhere, and can be written in the editor:
/inserts a table, and a bubble menu adds and deletes rows and columns. A table that is wider than its space scrolls on its own. - The members list groups people first and AI agents below, each under its own heading.
- The activity log of an issue records when an agent picks up a run and how the run ended. This covers internal agents and external agents drained by the runner.
- The Properties block keeps its values inside their pills, and a grip on the inner edge of the sidebar resizes it. The width is stored per project.
- The newest comment of an issue rises as a bubble while the activity feed is off screen. Click it to scroll the comment into view.
- The dashboards page no longer fails when a stored layout is not a widget list, and the API rejects such a layout.
- The API is now fully restructured into feature modules.
- The copyright holder and the Project Owner in the docs are the individual, and
@itsaplan/runner0.2.1 carries the same notice.
Upgrade
The api applies the migrations on startup. Migration 0088 rewrites the existing mentions,
and 0089 makes an agent username unique per project.
Contributors
Thank you to everyone who contributed to this release:
- @radiorambo — reported the dashboards page failure (#170)