@pify/cli 0.1.2 → 0.2.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.
package/README.md CHANGED
@@ -21,6 +21,7 @@ npx @pify/cli setup
21
21
  ```
22
22
  pify setup # install the pi coding agent (safe to re-run)
23
23
  pify setup --pi-version 0.84.4 # pin the version your team has tested
24
+ pify setup --installer # run pi's official interactive installer (ps1/sh)
24
25
  pify list # show the @pify catalog with install state
25
26
  pify install goal task # short names resolve to @pify/goal, @pify/task
26
27
  pify install goal -l -a # project scope, pre-approved (CI-friendly)
@@ -33,11 +34,20 @@ pify init my-extension # scaffold a new Pi Package
33
34
 
34
35
  Every command supports `--help`; `install`/`remove`/`update` support `--dry-run`; `list`/`doctor` support `--json`.
35
36
 
37
+ **Tab completion** — generated from the live command registry (commands, aliases, flags, and package names all complete):
38
+
39
+ ```bash
40
+ eval "$(pify completions bash)" # bash — add to ~/.bashrc
41
+ eval "$(pify completions zsh)" # zsh — add to ~/.zshrc
42
+ pify completions fish > ~/.config/fish/completions/pify.fish
43
+ pify completions powershell | Out-String | Invoke-Expression # add to $PROFILE
44
+ ```
45
+
36
46
  ## How it relates to `pi`
37
47
 
38
48
  `pify` deliberately does **not** replace pi's package manager. Every package operation delegates to `pi install` / `pi remove` / `pi update`, which own `~/.pi/agent/settings.json` and the extension npm workspace — pify never edits pi's settings. What `pify` adds:
39
49
 
40
- - **Bootstrap** — `pi update` can't run when pi isn't installed yet; `pify setup` closes that gap (`npm install -g --ignore-scripts @earendil-works/pi-coding-agent`, matching pi's own self-update invocation).
50
+ - **Bootstrap** — `pi update` can't run when pi isn't installed yet; `pify setup` closes that gap with the same invocation as pi's official installers (`npm install -g --ignore-scripts --min-release-age=0 --no-fund --no-audit`), falling back to `bun add -g --ignore-scripts` when npm is absent and to `--prefix ~/.local` on POSIX when npm's global prefix is not writable (never sudo). `pify setup --installer` hands off to the official interactive installer (`install.ps1` on Windows, `install.sh` on Unix), which can bootstrap Node and Git Bash too.
41
51
  - **Catalog** — `@pify/*` short names, discovery (including packages that are planned but not yet published), and install state at a glance.
42
52
  - **One-pass update** — `pify update` chains pi's self-update with per-package updates of everything from this org, without touching non-Pify packages you manage separately.
43
53
  - **Doctor** — environment sanity checks for support requests.
package/catalog.json CHANGED
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": 1,
2
+ "version": 12,
3
3
  "org": "pifydev",
4
4
  "scope": "@pify",
5
5
  "remote": "https://raw.githubusercontent.com/pifydev/cli/main/catalog.json",
@@ -8,78 +8,78 @@
8
8
  "name": "btw",
9
9
  "npm": "@pify/btw",
10
10
  "repo": "https://github.com/pifydev/btw",
11
- "description": "By-the-way notes: capture asides during a session without derailing the agent",
12
- "status": "planned"
11
+ "description": "By-the-way side conversations: a read-only, codebase-aware side agent in a widget",
12
+ "status": "published"
13
13
  },
14
14
  {
15
15
  "name": "goal",
16
16
  "npm": "@pify/goal",
17
17
  "repo": "https://github.com/pifydev/goal",
18
- "description": "Pin a session goal and keep the agent anchored to it",
19
- "status": "planned"
18
+ "description": "Pin a session goal and keep the agent anchored to it: settled-idle continuation with safety limits",
19
+ "status": "published"
20
20
  },
21
21
  {
22
22
  "name": "memory",
23
23
  "npm": "@pify/memory",
24
24
  "repo": "https://github.com/pifydev/memory",
25
- "description": "Persistent memory across pi sessions",
26
- "status": "planned"
25
+ "description": "Persistent memory: two-tier markdown storage, FTS5 search, secret-scanned writes",
26
+ "status": "published"
27
27
  },
28
28
  {
29
29
  "name": "plan-mode",
30
30
  "npm": "@pify/plan-mode",
31
31
  "repo": "https://github.com/pifydev/plan-mode",
32
- "description": "Read-only planning mode with an explicit approve-then-execute gate",
33
- "status": "planned"
32
+ "description": "Read-only planning mode with an enforced approve-then-execute gate: tool policy, plan files, fresh-session handoff",
33
+ "status": "published"
34
34
  },
35
35
  {
36
36
  "name": "pretty",
37
37
  "npm": "@pify/pretty",
38
38
  "repo": "https://github.com/pifydev/pretty",
39
- "description": "Prettier TUI rendering for tool calls, diffs, and markdown",
40
- "status": "planned"
39
+ "description": "Compact theme-aware rendering for built-in tools: summaries, highlighted reads, colorized diffs",
40
+ "status": "published"
41
41
  },
42
42
  {
43
43
  "name": "subagent",
44
44
  "npm": "@pify/subagent",
45
45
  "repo": "https://github.com/pifydev/subagent",
46
- "description": "Spawn scoped subagents from within a pi session",
47
- "status": "planned"
46
+ "description": "Spawn scoped subagents: agent_run/agent_result, custom agent types, turn caps and tool allowlists",
47
+ "status": "published"
48
48
  },
49
49
  {
50
50
  "name": "swarm",
51
51
  "npm": "@pify/swarm",
52
52
  "repo": "https://github.com/pifydev/swarm",
53
- "description": "Coordinate multiple pi agents working in parallel",
54
- "status": "planned"
53
+ "description": "Coordinate multiple pi agents in parallel: fan-out with auto-routing, concurrency queue, aggregated reports",
54
+ "status": "published"
55
55
  },
56
56
  {
57
57
  "name": "task",
58
58
  "npm": "@pify/task",
59
59
  "repo": "https://github.com/pifydev/task",
60
- "description": "Track tasks and progress inside pi sessions",
61
- "status": "planned"
60
+ "description": "Task tracking with dependency graph, evidence-gated completion, live widget, CC-style reminders",
61
+ "status": "published"
62
62
  },
63
63
  {
64
64
  "name": "usage",
65
65
  "npm": "@pify/usage",
66
66
  "repo": "https://github.com/pifydev/usage",
67
- "description": "Token and cost usage reporting for pi sessions",
68
- "status": "planned"
67
+ "description": "Token and cost reporting: live footer, /usage dashboard over local session history, zero network",
68
+ "status": "published"
69
69
  },
70
70
  {
71
71
  "name": "workflow",
72
72
  "npm": "@pify/workflow",
73
73
  "repo": "https://github.com/pifydev/workflow",
74
- "description": "Deterministic multi-step agent workflows for pi",
75
- "status": "planned"
74
+ "description": "Deterministic agent orchestration: CC-style workflow scripts with agent()/parallel()/pipeline()",
75
+ "status": "published"
76
76
  },
77
77
  {
78
78
  "name": "yolo",
79
79
  "npm": "@pify/yolo",
80
80
  "repo": "https://github.com/pifydev/yolo",
81
- "description": "One toggle to auto-approve everything, with an undo trail",
82
- "status": "planned"
81
+ "description": "One toggle to auto-approve everything, with an undo trail: three-tier bash guard, file pre-images",
82
+ "status": "published"
83
83
  }
84
84
  ]
85
85
  }