Skip to content
Source
Sign inSign up

Share the why of a change

Work with agents

Share the why of a change

A pull request shows what changed, but not why. src uploads the conversation with your agent (the transcript) to the pull request, and the forge writes an intent summary from it on the Intent tab.

2 min read

You need src, and one of these agents: Claude Code, Codex, Cursor or OpenCode. T3 Code runs Claude Code and Codex, so their hooks upload its sessions too.

1. Log in

src auth login --web

src agent setup installs the upload hooks only when you are logged in. When an agent on your computer has no hook, the login tells you so: To upload your agent transcripts to pull requests, run: src agent setup.

2. Install the upload hooks

src agent setup

It installs the transcript upload hooks of the agents on your computer, for each forge that you are logged in to.

3. Start a new session of your agent

The hooks work in the sessions that start after the setup.

Done

Each pull request of your agent shows why you made it. The forge writes the intent summary on the Intent tab within a minute or two after each upload.

What src removes before the upload

src removes these secrets from the title, the messages and the tool calls of the transcript:

  • Keys and tokens of known services, from the gitleaks rule set, and TanStack Source tokens.
  • Authorization: Bearer values.
  • The values of .env lines with a secret name, for example API_KEY or DB_PASSWORD.
  • Private keys.
  • Password and token values in code or config that look random.

A removed value shows as [redacted: <kind>]. A value that contains EXAMPLE stays.

Caution

Do not put names, emails or other personal data in the conversation with your agent. src does not remove them.

Who reads the transcripts

Turn the uploads off

  • To set up your agents with no hooks, run src agent setup --no-transcripts.
  • To turn uploads off for your account, open Agent transcripts.