Code is cheap, show me your talk.

AgentGit makes every agent session easy to save, share, and continue. Explore how others solve problems, and share your agent experience with the world.

Explore Agent Hub

Import sessions from these AI agents

  • Claude Code
  • Codex
  • OpenCode
  • OpenClaw
  • Hermes
  • WorkBuddy

Why collaborate on sessions?

Files hold the result.Sessions preserve the full process.

Your instructions, reasoning, attempts, and decisions live in the session. Without it, switching agents or teammates means starting over.

AgentGit saves and transfers the complete session, so the work can continue from where it left off.

01 · HANDOFF & SHARE

One session. Two ways to pass it on.

Let someone continue the work or simply view it through a link. Copy a prompt and let your agent handle the rest.

Let someone continue

Copy this message into Claude Code, Codex, OpenCode, OpenClaw, Hermes or WorkBuddy.

Prompt

Use AgentGit to hand off this session so someone else can continue from where I stopped. Follow https://agent-git.com/docs/sharing/。

Explore features

02 · REMOTE CONTROL & COLLABORATION

Use your agent remotely—and invite others to work with you.

Open the workspace from your phone or another computer to start, continue, and follow the agent running on your machine.

Share an invite link so others can join, send prompts, follow progress, and handle approvals.

Ask your agent to set up remote collaboration

Copy this message into Claude Code, Codex, OpenCode, OpenClaw, Hermes or WorkBuddy.

Prompt

Set up AgentGit Remote Control so I can use the agent on this computer from another device. Then guide me to create a workspace invite link so others can join and collaborate. Follow https://agent-git.com/docs/remote-control/。

Explore features

03 · Agent Session Hub

The idea is just the beginning. See how it took shape.

Open any project to see the instructions, attempts, tool calls, results, and decisions behind it.

Paper2Ace

Put a paper on trial.

Turn a research paper into a courtroom game. Follow the evidence, the playtests, and the redesign.

View the full session

Game of Life Reborn

Make your GitHub graph play.

Bring an abandoned Game of Life extension back to life, from the first diagnosis to a working Play button.

View the full session

Platydiff

What would a better diff look like?

Follow Platydiff from “how does diff work?” to a Python text engine and a plan for comparing more than text.

View the full session

TableForge

From experiment to comparison table.

Build TableForge around a small image-segmentation experiment, with metrics, failed runs, and evidence behind every row.

View the full session

Explore more public sessions →

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, OpenCode, OpenClaw, Hermes, and WorkBuddy 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?

Keep your agent work moving.

Save the session, come back later, switch devices, or let someone else continue.

$ npx -y create-agit@latest