Sessions

Exporting and sharing a session

Save the conversation as markdown, or hand a teammate a revocable link to the context behind it.

Code
/export                    the conversation as markdown
/export ./notes/debug.md   to a path you choose
/share                     a revocable link to this session's context

Export, for a file you keep

/export writes the conversation to markdown — prompts, answers, and the commands that ran. Good for attaching to a pull request, pasting into an issue, or keeping a record of a debugging session that took three hours to get right.

It's a file. Once written, nobody revokes it.

Share, for a link you can take back

/share mints a capsule: a scoped, revocable, expiring link to the context behind this session — the decisions, the relevant code, the thread.

The difference from an export is that the recipient gets working context, not a transcript. Another agent can be pointed at the link and start with what you had. And you can revoke it.

Code
/share                     link for this session
/share Billing migration   with a title
/capsule                   list what you've shared
/capsule create            one without sharing the whole session

Sharing context with a link covers scopes, expiry, and revocation.

Which to reach for

You wantUse
A record in the repository or a ticket/export
To hand a teammate what you know, now/share
To brief another agent/share
Something that can't be revoked later/export

If it doesn't work

The export is enormous. Long sessions are long. /compact first to fold older turns into a summary, then export.

The share link 404s for a teammate. It expired or was revoked. /capsule lists yours; make a new one.

I shared more than I meant to. Revoke it from the dashboard or with /capsule, then create a narrower one.

Next