Skillsync is built around the CLI publishing flow. If you want to share a session, this is the path that matters: install the CLI, sign in once, then upload the session you want to publish.
Skillsync has full support for Claude Code transcripts. Codex and OpenCode uploads are available in beta.
Install the CLI
If you do not have the CLI yet, install it first:
curl -sSL https://install.skillsync.com | sh
Once the install finishes, confirm the binary is available:
replay --help
Fastest start
replay init does the setup for you: it logs you in and offers to turn on background auto-upload. It is idempotent, so you can re-run it anytime.
replay init
If you would rather do it by hand, follow the steps below.
Sign in
Uploads require an authenticated Skillsync account.
replay login
That command opens your browser, sends you through the Skillsync sign-in flow, then returns control to the CLI once authentication completes.
If you want to confirm the current account before uploading, run:
replay whoami
Upload a session
Use replay upload with either a session ID or the exact session title:
replay upload <session-id-or-title>
Example with a session ID:
replay upload 7f0a6c47-0a63-4af6-88c3-2a9156a0f2fd
Example with a title:
replay upload "ship docs layout"
On the first successful upload, Skillsync creates a private thread and prints the share URL in your terminal.
What gets published
When you upload, Skillsync sends the session transcript and its metadata to the server:
- Transcript messages
- Timestamps
- Agent type
- Session title when available
- Project path when available
- Git branch when available
- CLI version when available
- Model metadata when available
What happens on later uploads
Skillsync treats the same local session as the same published thread.
If you upload that session again later, Skillsync updates the existing thread instead of creating a second URL.
Keep it automatic
Instead of uploading by hand, you can let the CLI sync changed sessions in the background:
replay auto enable
From then on, sessions that change sync on a timer. See /docs/cli-reference for auto, workspaces, and the rest of the commands.
Next steps
- Read /docs/upload-command for the exact command behavior.
- Read /docs/cli-reference for every command and flag.
- Read /docs/transcript-support for Claude Code, Codex, and OpenCode coverage details.
- Read /docs/troubleshooting if an upload fails.