AI agents

Work records

Read the proof of work an AI agent leaves on a card, including its checks, commits, model and usage.

Last updated

See what the agent did#

A work record is a short report an AI agent leaves on a card when it finishes. It says which agent and model worked, whether the checks passed, which commits it made, and a summary of what was done. The agent creates it with the record_work tool, after it commits and runs its tests.

Only project members see work records. Signed-out visitors of a public project, and visitors who joined a public project by themselves, do not.

Why your team wants it#

Without a record, an agent's "done" is only a status change. With one, a reviewer sees at a glance that the tests passed, which commits to read, and how much the run cost. It also helps you compare models and keep an honest history of what the agents did.

Read a work record#

  1. Open a card that an agent worked on.
  2. Scroll to the Work section, marked "reported by an AI agent".

The latest record shows in full.

  • A badge with the result. Checks passed means every check passed, Checks failed means at least one failed, and No checks means none ran.
  • The agent name, the model, and sometimes the number of subagents and how long the work took.
  • A tokens chip. Hover or focus it to see input, output and cache numbers per model. The total does not count cache reads.
  • The list of checks, each with pass, fail or skipped and a short note.
  • The summary, as plain text.
  • The commits. A commit is a link when Sprintree saw it in a connected GitHub repository. Otherwise it says "not seen on GitHub". See GitHub.
  • A footer saying who reported it, through which tool and when.

If the card has more records, press the line "N earlier records" to open them.

Delete a record#

Press Delete at the bottom of a record and confirm. The record is removed from the card for everyone. Only an editor who is the record's author, or the project owner, can delete it.

Ask your agent to record its work#

Add a line to your prompt, such as "When you finish, record your work on the card." The Sprintree plugin also reminds Claude Code to do it after a commit.

Tips and common mistakes#

  • A card keeps its newest 30 records. A 31st replaces the oldest.
  • A record holds commit hashes only, never commit messages, logs or test output. Text that looks like a secret is blanked.
  • The summary is limited to 500 characters, so it is a pointer, not a report. The full story belongs in the card comment.
  • A record needs edit access to the card. A read-only agent cannot record work.