Commit Context
- Desktop app
- All plans
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 ia-agents-conversation-history: <url> line 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.
Video (1:20): Commit Context, shown in the real app. An agent fixes a cart under a constraint the diff never shows, the commit carries a link, the link opens the conversation, and a new agent finds the reason through it.
Where to find it
- Right panel > Changes tab > Working tree, next to Commit and Commit + Close: the conversation icon, tooltip Attach agent conversation to commit (on by default, highlighted when on). The buttons appear once the agent has changed files.
- First use: the dialog Attach the conversation? explains what is uploaded, then remembers your consent.
- The link itself: in the full commit message (
git log -1). The commit window of the History tab shows the subject and the files, not the rest of the message. A link clicked in a terminal opens in your system browser, or in the browser built into AgentsRoom with the "Open terminal links in" setting (shift-click does the other one). - 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
- Commit from the Changes tab with the toggle on. The first time, read the consent dialog and click Enable and continue (Not now commits without the link).
- 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. - The commit is created. Afterwards the resulting SHA is attached to the gist so the page can point back at the commit.
- Anyone with the URL reads the conversation as a document, or hands it to the next agent with Copy markdown.
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 icon next to the commit buttons; 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
Each CLI's transcript goes through its own reader: Claude Code, Codex, Grok Build, Mistral Vibe, oh-my-pi, Pi and Antigravity CLI. For a CLI without an addressable transcript, 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.
- Only the readable page is uploaded. Tool outputs and what the CLI injects behind the scenes (account e-mail, project instructions, git status, environment details) are not. Your own prompts and the agent's replies are published as written.
- Gists created before November 2026 can still offer a Raw JSONL download, unless the cleanup of November 2026 emptied it.
- Requires a signed-in account to upload; no plan quota, gists are free.
- The readable page leaves out what the CLI injects (system reminders, environment prompt, skill bodies). The Raw JSONL download is the complete transcript: it still holds them, including the account e-mail the CLI received. Think of it before sharing a link widely.
- Rate-limited creation and viewing to prevent abuse.
Common questions
- How do I attach the agent's conversation to a commit? It is on by default: the icon next to the Commit buttons of the Changes tab, tooltip "Attach agent conversation to commit". Commit as usual, accept the one-time dialog, and the link is in the commit message. The video shows it: https://youtu.be/3KTQDa8GD88
- 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,
.envvalues) are masked before upload, best effort. Keep the link private. - What exactly is uploaded? The readable conversation: your prompts, the agent's replies and the tools it ran. Tool outputs and the context the CLI injects (account e-mail, project instructions, git status) stay out.
- Where did the Raw JSONL button go? New gists have no raw transcript any more. Use Copy markdown to hand the conversation to an agent.
- 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.
- Is there a video that shows it? Yes, 1:20, in the real app: https://youtu.be/3KTQDa8GD88
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 conversation itself.
- Per-Agent Review: the per-agent file mapping that decides whose conversation is attached.