sync

Do not read or inspect any files yourself.

The user cannot see tool output (Claude Code collapses it), so any output you are told to show or write verbatim is copied exactly into your reply text — never summarized or paraphrased.

AskUserQuestion, everywhere below: at most 4 questions in one call and at most 4 options in one question; multiSelect: true only with 2 or more options. Make one AskUserQuestion call per message and wait for its answers before the next (two calls in one message show the user only the last). A dismissed question runs nothing.

Step 1 — new workspaces, then repos and folders with no rule, then the upload

Run EXACTLY this one command, with the Bash tool's timeout set to 600000 (add --account <key> when the user named an account, and the --tenant override from Step 2 when the user asked for it):

node ${CLAUDE_PLUGIN_ROOT}/scripts/sync.mjs --review

It prints a <joined> block (new workspaces, below) and stops there when that block's last line is not joined=0. Otherwise it prints a <routes> block (repos and folders with no rule, below) and stops there when its last line is not routes=0. When both are 0 it goes straight on to the upload: everything after the </routes> line is Step 2's output, and no other command runs. A listing that fails shows a ✗ line inside its block instead and counts as nothing to ask: write that line verbatim.

First, new workspaces: the <joined> block, which workspace.mjs joined prints.

Its output is for you only. For an account that joined a workspace since it was last reviewed on this machine, it lists every repo and folder with where its analytics go now. Its lines:

• <email>: you joined <names> — <N> repos or folders to review account=<key> new=<ids> — starts the block; <names> names the new workspaces;
• W. <workspace> account=<key> tenant=<id> new=<yes|no> role=<role> — one per workspace; new=yes is one just joined;
• J<i>. <short> (<full label>), <k> sessions, now: <where> account=<key> kind=<repo|folder> match=<match> now=<ids|none|pending> — one repo or folder (a J line). <where> is where its analytics go today: workspace names, not tracked, or no rule yet. J<i>. outside a project, <k> sessions, now: <where> … kind=outside match=outside is one too: sessions in the home folder, / or a temp folder;
• J<i>-command=<command> — right after its J line: the command that adds one new workspace to it, ending in a literal <tenant>. It is not a J line;
• add-all-command=<command> — adds the new workspaces to every listed repo and folder that already sends somewhere;
• done-command=<command> — records that the new workspaces were reviewed, and keeps unpicked repos and folders sending where they send now;
• joined=<total> — the number of J lines, always last.

Run the printed commands unchanged; whatever they route gets its history uploaded.

joined=0 → nothing to ask; go to "Then, repos and folders with no rule" below.

For each account with J lines (with several accounts, end every question text with " ()"), using that account's W. lines and commands:

More than 4 J lines → first ask (single-select) "You joined . Where should analytics for these repos and folders go? Their past sessions will be sent there too." (<N> = that account's number of J lines) with the options "Add to all " (description "Repos you don't track, and ones with no rule yet, stay as they are"), "Choose repos" ("Pick which repos and folders go to each new workspace") and "Leave them as they are" ("Nothing changes, and you're not asked about again").

• "Add to all " → run the add-all-command= text EXACTLY ONCE.
• "Choose repos" → the per-workspace questions below.
• "Leave them as they are" → run the done-command= text EXACTLY ONCE.
• A dismissal → nothing; the next /beezi:sync asks again.

4 or fewer J lines → the per-workspace questions.

Per-workspace questions — for each W. line with new=yes of that account, in order, ask the multiSelect: true question "Which repos and folders should also send analytics to ? Their past sessions will be sent there too." <name> is the W. line's text after W. up to account=, and <tenant> its tenant= value. Options: one per J line of that account, in order — label = <short> (the J line's text after J<i>. up to ( or ,), description = "Now: " (<where> = the text after now: up to account=), or "No rule yet" when <where> is no rule yet; then "None of these" LAST (description "Nothing from these goes to "). So a question lists at most 3 places plus "None of these": more J lines → split them in order into questions of at most 3 places, each ending in " (part j of k)"; that workspace's answer is all of its parts together. "None of these" alone means no pick from that question. If it is chosen together with any place in the same question, ask that workspace's question again once (every part), starting with "None of these" can't be combined with repos — pick one or the other. A mixed answer is not an answer. A second mixed answer is a dismissal: no J<i>-command for that workspace and no done-command. At most 4 questions per AskUserQuestion call: more → further calls, one after another. The printed J numbers are global across accounts: preserve each to match its command.