spooling push
Ship local sessions to Spooling Cloud. Filter by project, cwd, or title, and optionally copy across workspaces.
spooling push [--limit N] [--batch N] [--project NAME]
[--cwd SUBSTR] [--title SUBSTR]
[--copy] [--dry-run]Pushes sessions from the local database up to the Spooling Cloud workspace your CLI is currently logged into. Workspace ownership is determined by the API key you used in spooling cloud login.
Flags
| Flag | Description |
|---|---|
--limit N | Max sessions to push per run. Default: 100. |
--batch N | Sessions per HTTP request. Default: 20. |
--project NAME | Only push sessions whose project column matches exactly (case-insensitive). |
--cwd SUBSTR | Only push sessions whose cwd contains this substring (case-insensitive). |
--title SUBSTR | Only push sessions whose title contains this substring (case-insensitive). Useful when the cwd is generic (e.g. Claude Code launched from ~). |
--copy | Share sessions you've already pushed to another workspace. The cloud writes them as fresh rows here under deterministically rewritten IDs. Idempotent. |
--dry-run | List which sessions would be pushed and exit. No network call. |
Filters combine with AND.
The two scoping patterns
Pattern A: separate per workspace
The cleanest separation. Personal sessions stay personal, team sessions stay in team.
spooling cloud login --key sk_<team-key>
spooling push --cwd toebox --dry-run # preview which sessions match
spooling push --cwd toeboxPattern B: share via copy
Sessions you've already pushed to one workspace can be mirrored into another without removing them from the source. The cloud rewrites session IDs deterministically so the same source session lives in both workspaces.
spooling cloud login --key sk_<team-key>
spooling push --cwd toebox --copy --dry-run
spooling push --cwd toebox --copy--copy is idempotent. Re-running it updates the same target rows; it does not create duplicates.
When the cwd is generic
If you launched Claude Code from your home directory, every session captured there will have cwd=/Users/<you>. The --cwd filter can't tell IsletIQ work apart from anything else. Use --title instead. The project name typically appears in the session title.
spooling push --title islet --copy --dry-run
spooling push --title islet --copyYou can combine filters too:
# IsletIQ work specifically inside ~/Documents
spooling push --cwd ~/Documents --title isletCleaning up
If sessions ended up in the wrong workspace and you want them only in the right one (not duplicated), delete from the wrong workspace first.
# log into the workspace that currently owns the sessions
spooling cloud login --key sk_<wrong-workspace-key>
spooling cloud delete --cwd toebox --dry-run
spooling cloud delete --cwd toebox
# then log into the right one and push as usual
spooling cloud login --key sk_<right-workspace-key>
spooling push --cwd toeboxspooling cloud delete reference →
Reading the output
pushed 20 sessions
pushed 11 sessions
Done. 31 sessions synced to https://api.spooling.aiIf sessions get rejected, you'll see:
pushed 0 sessions rejected 20
Done. 0 sessions synced to https://api.spooling.ai (100 rejected: IDs already owned by another workspace)The cross-tenant defense in Spooling Cloud refuses to silently move a session from one workspace to another. To resolve:
- Want it in both workspaces? Re-run with
--copy. - Want it only in this workspace?
spooling cloud deletefrom the source first, then push here.
Gotchas
Always paste the full command on a single line. zsh treats line breaks as command separators, so a wrapped spooling push \\ --cwd toebox \\ --copy will run spooling push with no flags and then fail on --cwd as a separate command.
Without filters, spooling push ships everything. It pushes the most recent --limit sessions from every project on this laptop. If your CLI is logged into a team workspace, that includes work that isn't relevant to the team. Always filter when pushing to a team workspace.