Menü
Assigns a friendly tag to a session for easy recall and cross-device restore.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Removes synced session data from the local staging directory with double confirmation. All cleaned sessions are tombstoned to prevent re-sync.
Deletes a specific session from the sync repository. Requires double confirmation before deletion.
Lists all synced AI CLI sessions. Pulls latest from remote first, then displays.
Prune old synced sessions that exceed a retention period.
Restores a previous AI CLI session — either hot-loads into current context or prepares for /resume.
Shows the current status of Synctx — sync directory, audit log, prerequisites, and CLI paths.
| name | tag-session |
| description | Assigns a friendly tag to a session for easy recall and cross-device restore. |
To tag a session:
First list available sessions so the user can identify which one to tag:
node ./scripts/sync-engine.js list
Ask the user which session they want to tag and what tag name to use. They can provide:
e0e9f4b8-495b-4db7-a997-e03abb610a62e0e9f4b8Run the tag command:
node ./scripts/sync-engine.js tag <session-id> <tag-name>
Examples:
node ./scripts/sync-engine.js tag e0e9f4b8 auth-refactor
node ./scripts/sync-engine.js tag current my-feature
Tag names must be:
If the tag already exists on another machine for a different session, it will be auto-suffixed with the hostname to prevent conflicts.
The tag is committed and pushed to the remote sync repository so it's available on all machines.
Present the result to the user. Tags can then be used with restore, delete, and other commands.