projmux 0.12.2 → 0.13.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/docs/agent-workflow.md +183 -20
- package/docs/ai-agent-shortcuts.md +22 -3
- package/docs/architecture.md +1291 -90
- package/docs/cli-guide.md +499 -57
- package/docs/cli.md +236 -64
- package/docs/configuration.md +197 -35
- package/docs/hooks.md +17 -3
- package/docs/keybindings.md +2 -2
- package/docs/legacy-cli-retirement.md +37 -8
- package/docs/operational-diagnostics.md +58 -2
- package/docs/session-restore.md +73 -157
- package/docs/settings-ia.md +48 -24
- package/docs/statusbar.md +10 -2
- package/docs/testing.md +80 -4
- package/docs/upgrading.md +243 -5
- package/docs/usage-tracking.md +56 -10
- package/package.json +5 -5
|
@@ -14,6 +14,23 @@ Provider shortcuts (`projmux create codex|claude|antigravity`) normalize to the
|
|
|
14
14
|
same Agent route. Keep machine-local policy, private prompt text, and personal
|
|
15
15
|
workflow recipes in user config or dotfiles rather than tracked project docs.
|
|
16
16
|
|
|
17
|
+
Every form above is resource-backed. With no `--project` the command runs
|
|
18
|
+
against the **active managed Project's active Window** and splits from the
|
|
19
|
+
active Pane, so a shortcut invoked from inside a projmux Window lands where you
|
|
20
|
+
are. Registered shortcuts therefore need no scope flag. Add `--project <ref>`,
|
|
21
|
+
and optionally `--window <ref>` with `--create-window`, when a shortcut must
|
|
22
|
+
target something other than where it was invoked. See
|
|
23
|
+
[Create scope](cli-guide.md#create-scope) for the full rule and its refusals.
|
|
24
|
+
|
|
25
|
+
Two consequences matter for shortcut authors:
|
|
26
|
+
|
|
27
|
+
- **A shortcut invoked outside tmux, or from a Home/control/unattributed pane,
|
|
28
|
+
exits `2` and names `--project`.** It creates nothing. Give such a shortcut an
|
|
29
|
+
explicit `--project`.
|
|
30
|
+
- **The client does not move.** Every create is detached. Follow with
|
|
31
|
+
`projmux focus pane uid:<uid>` — or take `-o pane-id` and move the client
|
|
32
|
+
yourself — when the shortcut should end up in the new pane.
|
|
33
|
+
|
|
17
34
|
## Command contract
|
|
18
35
|
|
|
19
36
|
Choose a direct provider when a shortcut must always open that provider:
|
|
@@ -55,9 +72,10 @@ as a stable follow-up handle:
|
|
|
55
72
|
pane_id="$(projmux create codex --placement right -o pane-id -- "prompt")"
|
|
56
73
|
```
|
|
57
74
|
|
|
58
|
-
Success prints exactly one `%N` Pane id
|
|
59
|
-
|
|
60
|
-
id is nonzero rather than a false
|
|
75
|
+
Success prints exactly one `%N` Pane id -- the managed Pane's raw tmux handle.
|
|
76
|
+
Without `-o`, the default projection is the `<kind>/<name> created` summary
|
|
77
|
+
line. Failure to obtain a valid tmux Pane id is nonzero rather than a false
|
|
78
|
+
success.
|
|
61
79
|
|
|
62
80
|
## Naming pattern
|
|
63
81
|
|
|
@@ -119,4 +137,5 @@ project roots, permission policies, or model choices in shared docs.
|
|
|
119
137
|
- Put provider arguments after `--`; omit it when the payload is empty.
|
|
120
138
|
- Use `create pane` for a shell Pane.
|
|
121
139
|
- Use `-o pane-id` only when automation consumes the returned `%N` handle.
|
|
140
|
+
- Add `--project <ref>` to any shortcut that can run outside a managed Window.
|
|
122
141
|
- Keep private workflow policy outside tracked project docs.
|