Commit Context

  • Desktop app
  • All plans
View as MarkdownFeature page

What it does

Attaches the agent conversation behind a commit to the commit itself. When you commit from AgentsRoom, the transcript of the agent (or agents) whose files are in the commit is rendered as readable Markdown, common secrets are redacted on a best-effort basis, the result is uploaded as an unlisted gist on the AgentsRoom backend, and an Agent-Conversation: <url> trailer is added to the commit message. Months later, a teammate or the next agent reading git history opens the link and recovers the prompts, reasoning, tools run and decisions, which is the scarce resource once a terminal closes. The same gist host works standalone at gist.agentsroom.dev.

Where to find it

  • Right panel > Changes tab, under the commit message: the checkbox Attach agent conversation to commit (on by default).
  • First use: the dialog Attach the conversation? explains what is uploaded, then remembers your consent.
  • Defaults: Settings > Git > Attach agent conversation to commit (the global default, next to the commit message and format rules settings); Folder settings > Git > Attach the conversation to the commit for a folder of projects.
  • Manual gists: gist.agentsroom.dev (create with a title and Markdown content, get an unlisted link).

How to use it

  1. Commit from the Changes tab with the checkbox on. The first time, read the consent dialog and click Enable and continue.
  2. AgentsRoom resolves the agents behind the included files, reads their session transcripts (sub-agents included), redacts API keys, tokens and .env-style values, uploads the gist and appends the trailer.
  3. The commit is created. Afterwards the resulting SHA is attached to the gist so the page can point back at the commit.
  4. Anyone with the URL reads the conversation as a document, or downloads the raw transcript to feed it back to an agent.

Uncheck the box to skip it for one project: the choice is remembered per project and follows the project across your machines.

Settings

  • attachConversationToCommit (global, Settings > Git; project override from the Changes checkbox; folder default in Folder settings > Git): attach the conversation to commits. Default on.
  • gistConsentGiven (global): set once you accept the consent dialog.

Agent tools (MCP)

None. Agents benefit as readers: the link is in git history, and a gist page is readable without authentication.

Providers

Provider-agnostic in principle: the conversation is rendered from the CLI's session transcript. Today Claude Code sessions are resolved and attached; for CLIs without an addressable transcript (Codex today) the commit goes through without a trailer.

Mobile

Commits made from the phone's Changes screen go through the desktop, but the conversation attachment and its consent dialog are desktop-side only; the phone's commit does not add the trailer.

Limits

  • The upload never blocks a commit: offline, signed out or on any error, the commit goes through without the trailer.
  • Unlisted, not private: anyone with the URL can read the gist. The link is a high-entropy slug, not listed, not indexed, not enumerable.
  • Redaction is a safety net, not a guarantee: review before sharing a link widely.
  • Requires a signed-in account to upload; no plan quota, gists are free.
  • Rate-limited creation and viewing to prevent abuse.

Common questions

  • Is it on by default? Yes, with a one-time explanation before the first upload. Uncheck the box per project to turn it off.
  • Where is the conversation stored? On the AgentsRoom backend, tied to your account, behind an unlisted link.
  • Are my secrets uploaded? Common patterns (API keys, tokens, .env values) are masked before upload, best effort. Keep the link private.
  • Does it slow down my commit? The upload runs just before the commit so the link can go in the message; a failure never blocks.
  • Can I create a gist without a commit? Yes, by hand on gist.agentsroom.dev.

Related

  • AI Commit Messages: the message itself, written from the diff or posted by the agent; same Settings > Git tab.
  • Project Memory: distilled knowledge that outlives sessions, where Commit Context keeps the raw conversation.
  • Per-Agent Review: the per-agent file mapping that decides whose conversation is attached.