title: Resuming a session description: How a teammate can pick up a finished agent session and continue it locally. order: 3

Resuming a session

Because every gild session ends with a full transcript file uploaded to its Slack thread, a session is portable. A teammate — on a completely different machine — can resume where you left off.

What's in a transcript

The transcript is a *.gild.jsonl file, one JSON object per line:

  • a header — session id, gild, provider, repo, branch, base commit, and the Slack thread
  • the prompt(s)
  • steps — the user-valued reasoning, each linked to its Slack reply
  • tools — name, input, result, and duration
  • a result — the final commit, files changed, and status

How resume works

  1. Open the finished session in gild and choose Resume.
  2. gild fetches the transcript file from the Slack thread.
  3. It recreates a fresh git worktree from the recorded base commit and branch.
  4. It replays the transcript into the provider's state — Claude's query resume or Codex's resumeThread — so the agent has the full prior context.
  5. You continue the session on your machine, and new work flows back into the same thread.

Why this is the point

This is what makes gild team-native. Agent work is no longer trapped on one laptop. The whole team sees the session in Slack, and anyone can take the baton and keep going.