Skip to content

trace v0.15.0

Latest

Choose a tag to compare

@noble1911 noble1911 released this 12 Nov 21:49
· 12 commits to main since this release
74aead7

Your own boards

  • A Boards page for boards you make in trace. New board… sets one up from a template (Software, Research, Bug triage or Blank) with its columns, card types, a kickoff prompt and the repositories its agents run in. Everything can be changed afterwards.
  • Cards (local-12) start agents and move between columns like any ticket. A card type can have its own prompt, so a Bug and a Spike on the same board start differently.
  • A board can have its own icon.

Board settings, on every board

  • Any board, Jira's and Pylon's too, has ⋯ → Board settings…: its own kickoff prompt and its own repositories. With one repository trace never asks; with several it uses the default, or asks and offers only those.
  • The brief an agent starts with is the card type's prompt, else the board's, else the global one. New placeholders: {tracker}, {type}, {board}.
  • A ticket's agent is told which ticket it's working on every time it starts ("Jira ticket PM-1234"), including after a resume.

One Boards button in the sidebar

  • The board pages are grouped under one Boards button. The first click opens the board you last used; click again to open the list beneath it, and again to close it.
  • The list has Jira and Pylon once each, then each of your own boards. All boards lists every board by name. Settings → Sidebar turns the grouping off.

Connect Jira with your login

  • Integrations → Jira has Connect with your Atlassian login: no API token needed. It uses Atlassian's MCP server (v2). An API token still works, and is used if one is saved.
  • Reading boards this way was checked against a real Jira site. Moving a card and commenting haven't been run against one yet, so tell us if a move fails. Two differences from an API token: no linked pull requests, and "hide completed issues older than" follows Jira's default, not your board's setting.
  • Pylon has the same option, but it hasn't been tried against Pylon's real server yet. Treat it as experimental.

MCP servers

  • Atlassian moved to its v2 server; an existing login gets a Move to new server button.
  • Pylon and Intercom have EU servers. With the Pylon tracker connected, only your region's is offered.
  • A Metabase card: enter your instance's address and a name. Add one per instance (staging, production).
  • A server already in your Claude config keeps its name instead of being added twice.

Agents can work with every board

  • trace's tools for agents now cover all boards: list_boards, get_board for any board with its columns and setup, and moving, commenting on and starting agents for cards on boards that aren't on screen. On your own boards they can also create and update cards.

Also new

  • Scheduled prompts can run as a chat, not only in a terminal. Thanks Lembit (#101).
  • Pull requests is always in the sidebar and lists pull requests from sessions and ticket workspaces, not only Jira-linked ones.
  • trace keeps the computer awake while an agent is running (the display can still sleep). Settings → Agents turns it off.
  • A finished subagent's tab closes by itself five minutes after it ends if you never opened it. Its card in the chat brings it back. Settings → Tabs turns it off.
  • The assistant's model is picked from the models your Claude Code offers (Settings → Assistant).
  • Import from Conductor is offered on the empty Sessions page and at the top of Settings → Repositories, and imported sessions show at once.
  • The Fleet page says Jira ticket or Pylon ticket.

Fixes

  • Buttons that show a busy label ("Start" / "Starting…") centre their text instead of leaving a gap on the right.
  • The homepage's download buttons point at the newest release that has a file for your platform.