Code is cheap, show me your talk.

Git for AI agent sessions — save, resume, hand off, and reuse every conversation.

Get started → Browse public agents →

Install with your agent

?

Copy. Paste. Let your agent take it from here.

Install according to https://agent-git.com/docs/quickstart/

01 · Hand off the conversation, not a summary.

12s
mira · ~/tz-fix · claude · day 3

> try pytz first

↳ 3 tests failed · turn 12

> switch to zoneinfo

↳ passes on mac, fails on windows · turn 27

> reproduce the DST edge case

↳ tests/dst_transition.rs · fails as expected · turn 44

> the DST case is the last one. leaving for the day

● Noted. The repro is tests/dst_transition.rs; the fold flag is lost on the Windows path.

> ! agit push

↳ ✔ published mira/tz-fix · 61 turns

kenzo · ~/tz-fix · claude

$ agit clone mira/tz-fix

↳ ✔ 61 turns · opening claude with the full session

> mira: the DST case is the last one. leaving for the day

> finish the timezone fix

● Picking up at turn 61. pytz and plain zoneinfo already failed here; the fold flag is the open item.

● Update(src/tz.rs)

↳ 9 additions, 2 removals

● Bash(cargo test dst)

↳ 22 passed

● Windows path keeps the fold flag now. Ready for review.

The dead ends travel with the session. Your teammate starts from the last turn, not from a meeting.

The dead ends travel with the session. Your teammate starts from the last turn, not from a meeting.

Works with

  • Claude Code
  • Codex
  • OpenCode
  • Cursor

Why the session

Code is regenerable.
The conversation that produced it isn't.

An agent can rewrite a module in a minute. What it can't rewrite is the three days of decisions, dead ends and context that made the module right — that lives only in the session, in a temp directory, on one machine, until the runtime cleans it up.

AgentGit versions the session itself: every prompt, tool call and result, kept whole. Push it, pull it on another machine, hand it to a teammate, share it as a link. The talk becomes an asset you can keep and move — the same way code already is.

auth.ts
  1. export async function refreshToken(token: string) {
  2.   const res = await fetch(`/api/refresh`, {
  3.     method: `POST`,
  4.     headers: { Authorization: `Bearer ${token}` },
  5.   });
  6.   if (!res.ok) throw new Error(`Unable to refresh token`);
  7.   return res.json();
  8. }
TODO.PY
  1. #!/usr/bin/env python3
  2. """Tiny JSON-backed todo CLI.
  3. method: `POST`,
  4. Usage:
  5. todo.py add "buy milk" [--due 2026-09-05]
  6. todo.py list [--all] [--tag home]
  7. todo.py done <id>
  8. todo.py rm <id>
  9. todo.py --test    # run built-in tests
  10. """
  11. from __future__ import annotations

Get started

Four commands, then work as usual.

~/agentgit-demo
$ agit new Session started
Claude
Fix the checkout flow
Reading repository…
AgentGit · Recording
$ npx -y create-agit install the CLI
$ agit setup configure your agent
$ agit init initialize the repo
$ agit new start a session

Public agents

Read how other people got there.

Loading public agents…

Browse public agents →

FAQ

Questions people ask first.

What happens to secrets in my sessions?

Secrets can appear in prompts, tool calls and command output, so treat shared sessions like code review material. Before publishing or sharing a session, review it and remove anything sensitive. Read-only links do not grant write access.

Where is my data stored?

Sessions live in git repositories on the hub you push to — by default agent-git.com. Your machine keeps a local store under ~/.agit/. Visibility follows the agent settings you chose at first push.

Does AgentGit run in the background?

No daemon watches your disk. Sessions enter version control when you import or push them; turns settle at the end of each user turn via hooks you install with agit setup.

Which agent runtimes work?

Claude Code, Codex, and OpenCode support native resume. Cursor sessions can be imported read-only. Cross-runtime handoff may be lossy — agit states losses before converting.

Can I delete or rewrite history?

Published history is append-only: no rebase or force-push. To undo, fork a new branch from an older turn and continue there.

How does sharing a link work?

Share a read-only web link to a published session. Anyone with the link can read the full transcript without an account; write access still requires auth and grants.

Ready to get started?

Bring your agent sessions
with you.

Start with the CLI, or browse public sessions before you sign up.

$ npx -y create-agit
Get started →