Skip to main content
This guide shows you how to get your Claude Code sessions into a to11 project. For what a session is and what the dashboard shows, see Sessions.

Before you start

  • The to11 CLI 0.36.0 or later. Check with to11 version; Receiving skills has the install commands.
  • To be signed in, with to11 login or a bare to11. On a machine where nobody signs in, set TO11_API_KEY to a key with the ingest:write scope.
  • The ingest:write permission on the project, which the developer, admin, and owner roles hold.

Choose the project your sessions go to

Linking a repository with to11 or to11 link writes .to11/sessions.yaml in it, naming the project the skills come from. Linking your home writes ~/.to11/sessions.yaml. In most cases there is nothing more to do. To send a repository’s sessions to a different project, edit project in its .to11/sessions.yaml:
The file is yours, not the team’s: the CLI keeps the repository’s sessions.yaml out of git. A repository’s file comes before the one in your home, and --project, TO11_PROJECT, or TO11_PROJECT_ID come before both for a single run. See sessions.yaml for every key.

Send sessions by hand

Run to11 session sync inside the repository:
It sends the sessions started at the repository’s root, in a subdirectory, or in one of its worktrees, and only the lines added since the last run. The link opens the project’s Sessions page. To narrow a run: A run covers the newest sessions whose transcripts come to 512 MB together. If older sessions were left out, the CLI says so on stderr; to11 session sync --max-size 0 sends every session.

Send sessions automatically

Turn on auto-sync for the repository you are in:
From then on, the to11 plugin sends the session after each Claude Code response and when the session ends, as to11 session sync would. To turn it on for every repository, add --global; a repository’s own setting still comes before the global one. Auto-sync needs the to11 plugin 0.5.0 or later in Claude Code. to11 and to11 link offer to install it, and to11 ui installs or updates it. If the plugin is missing, to11 session autosync on says so. To see the setting that applies in the current repository, run the command without an argument:

Turn auto-sync off

Use --global to turn off the setting for every repository. Sessions already uploaded stay in the project.

If a sync stops

Next steps

Sessions

What the Sessions page shows, the cost estimate, and who can read it.

CLI commands

Every flag of to11 session sync and to11 session autosync.