Sharing Traces

Traces supports a few different sharing workflows depending on where you work. You can share one-off sessions from the CLI, ask your agent to share from chat, attach traces to commits with git hooks, or use API keys in CI and other headless environments.

Choose a sharing workflow

Sharing via CLI

Use the CLI when you want to manually publish a trace, choose its visibility, or script sharing from your terminal.

Read more: Sharing via CLI

Sharing via Agent Skills

Install the Traces share skill once, then ask your coding agent to share the current session without leaving the conversation.

Read more: Sharing via Agent Skills

Sharing via Git Hooks

Automatically attach traces to commits with git notes so collaborators can jump from code changes back to the traces that produced them.

Read more: Sharing via Git Hooks

Sharing via API Key

Use API keys when you need non-interactive sharing from GitHub Actions, Docker, CI/CD pipelines, or other sandboxed environments.

Read more: Sharing via API Key

Visibility levels

No matter how you share, each trace gets a visibility level:

• public for discoverable traces
• direct for link-only sharing
• private for namespace-only access

For CLI examples and visibility flags, see Sharing via CLI.

Related pages

• Sharing via CLI
• Sharing via Agent Skills
• Sharing via Git Hooks
• Sharing via API Key