@use-aistack/cli 0.7.1 → 0.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +7 -7
  2. package/dist/index.js +3419 -1512
  3. package/dist/index.js.map +1 -1
  4. package/package.json +2 -1
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  Measure and share your AI stack. The CLI scans your local Claude Code transcripts, shows you exactly what would go up, and publishes only after you approve in your terminal.
4
4
 
5
- Run on-demand with `npx` — no install required:
5
+ Run on-demand with `npx` - no install required:
6
6
 
7
7
  ```sh
8
8
  npx @use-aistack/cli sync
@@ -12,17 +12,17 @@ npx @use-aistack/cli sync
12
12
 
13
13
  ### `npx @use-aistack/cli sync`
14
14
 
15
- The default command. Scan your local transcripts (rolling 30 days), review the full summary, and publish the measured layer to your stack. Nothing leaves your machine without your explicit approval at the prompt. Raw transcripts, prompts, and paths never leave at all — only aggregates.
15
+ The default command. Scan your local transcripts (rolling 30 days), review the full summary, and publish the measured layer to your stack. Nothing leaves your machine without your explicit approval at the prompt. Raw transcripts, prompts, and paths never leave at all - only aggregates.
16
16
 
17
17
  ```sh
18
18
  npx @use-aistack/cli sync
19
19
  ```
20
20
 
21
- On an unlinked machine, `sync` starts the login flow inline — your browser opens to approve the machine, then the sync continues. One command is the whole onboarding.
21
+ On an unlinked machine, `sync` starts the login flow inline - your browser opens to approve the machine, then the sync continues. One command is the whole onboarding.
22
22
 
23
23
  ### `npx @use-aistack/cli sync --auto on` / `off`
24
24
 
25
- Optional: keep your stack fresh without manual syncs. `on` asks your stack for the permission, then writes a `SessionStart` hook into the harnesses you actually use — `~/.claude/settings.json` for Claude Code, `~/.codex/hooks.json` for Codex. The hook runs a silent sync at most once per day when a session starts. `off` removes the hooks and takes the permission back.
25
+ Optional: keep your stack fresh without manual syncs. `on` asks your stack for the permission, then writes a `SessionStart` hook into the harnesses you actually use - `~/.claude/settings.json` for Claude Code, `~/.codex/hooks.json` for Codex. The hook runs a silent sync at most once per day when a session starts. `off` removes the hooks and takes the permission back.
26
26
 
27
27
  ```sh
28
28
  npx @use-aistack/cli sync --auto on # enable, default every 24h
@@ -30,13 +30,13 @@ npx @use-aistack/cli sync --auto on --every 12 # custom frequency in hours
30
30
  npx @use-aistack/cli sync --auto off # revoke
31
31
  ```
32
32
 
33
- **Your stack owns the permission, not this machine.** The silent run asks aistack.to before it publishes anything, so the switch on your stack page is a complete revoke: it stops every machine, even one whose hooks are still installed. It works the other way too — turn the switch on, run one `sync`, and that machine installs its own triggers. A harness you adopt months later gets its trigger the same way.
33
+ **Your stack owns the permission, not this machine.** The silent run asks aistack.to before it publishes anything, so the switch on your stack page is a complete revoke: it stops every machine, even one whose hooks are still installed. It works the other way too - turn the switch on, run one `sync`, and that machine installs its own triggers. A harness you adopt months later gets its trigger the same way.
34
34
 
35
35
  The silent run (`sync --auto`) never prompts and never installs a hook. Each run appends one line to `~/.config/aistack/sync.log` (capped at 200 lines). The next interactive `sync` reports the last result. After 3 failures in a row, one visible message appears in Claude Code and names the fix. No email, no dialogs.
36
36
 
37
37
  ### `npx @use-aistack/cli login`
38
38
 
39
- Link this machine to your AI Stack account via browser. Optional — `sync` runs this inline when the machine is not linked yet.
39
+ Link this machine to your AI Stack account via browser. Optional - `sync` runs this inline when the machine is not linked yet.
40
40
 
41
41
  ```sh
42
42
  npx @use-aistack/cli login
@@ -44,7 +44,7 @@ npx @use-aistack/cli login
44
44
 
45
45
  ### `npx @use-aistack/cli connect claude`
46
46
 
47
- Optional: install the in-session sync surface for Claude Code — the `aistack` MCP server (user scope) plus the `aistack-sync` Skill. After that, say "sync my stack" in any Claude Code session. Both halves install together or not at all.
47
+ Optional: install the in-session sync surface for Claude Code - the `aistack` MCP server (user scope) plus the `aistack-sync` Skill. After that, say "sync my stack" in any Claude Code session. Both halves install together or not at all.
48
48
 
49
49
  ```sh
50
50
  npx @use-aistack/cli connect claude