@akagilnc/pi-workflow-roles 0.1.2439 → 0.1.2442

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@akagilnc/pi-workflow-roles",
3
- "version": "0.1.2439",
3
+ "version": "0.1.2442",
4
4
  "description": "Soul-bound workflow roles for Pi",
5
5
  "type": "module",
6
6
  "license": "Apache-2.0",
@@ -19,7 +19,11 @@ grok --prompt-file /path/to/labor-prompt.md -m grok-4.6 --always-approve --outpu
19
19
 
20
20
  - `-m grok-4.6` selects the model; `grok models` lists valid ids (currently
21
21
  `grok-4.6` default, `grok-4.5`).
22
- - `--always-approve` keeps the run non-interactive (documented).
22
+ - `--always-approve` (equivalently `--yolo` or `--permission-mode
23
+ bypassPermissions`) keeps the run non-interactive (documented). Headless
24
+ permissions otherwise default to interactive approval, where an `ask`
25
+ decision has no UI to answer; alternatively, use an explicit permission
26
+ setup that auto-approves the required call.
23
27
  - Official docs list `-p/--single` as the canonical headless prompt input;
24
28
  `--prompt-file` exists in the installed CLI (`--help`) and is smoke-verified
25
29
  on this host — prefer it for long prompts, fall back to `-p` if absent.
@@ -39,3 +43,24 @@ grok --prompt-file /path/to/labor-prompt.md -m grok-4.6 --always-approve --outpu
39
43
  - Feeding raw JSON directly through `--prompt-file` is rejected by the CLI as
40
44
  non-ACP JSON (`JSON object must have a type field`; live-verified
41
45
  2026-08-21).
46
+
47
+ ## MCP host behavior
48
+
49
+ - Repository MCP entries live under `[mcp_servers.<name>]` in
50
+ `.grok/config.toml`. They take effect only after the folder is trusted; pass
51
+ `--trust` on unattended/headless invocations. Without it, the project server
52
+ may be absent even though the file is present (`live-1787838141494`), and
53
+ `grok mcp doctor` reports `folder untrusted…re-run with --trust`
54
+ (`live-1787838491136`).
55
+ - Diagnose server startup with `grok mcp doctor [<server>]`, then inspect
56
+ `~/.grok/logs/mcp/<server>.stderr.log`; Grok truncates that stderr log on
57
+ each stdio server launch.
58
+ - MCP tools are exposed to the model as `<server>__<tool>` (for example,
59
+ `ak_489_coder__ak_coder_output`). Use the fully qualified name in prompts;
60
+ a bare tool name relies on the host's loose discovery/matching behavior.
61
+ - The headless permission setting described above also covers MCP calls.
62
+ - Grok launches a stdio server from the task cwd. Make `command` and `args`
63
+ cwd-independent: use absolute entrypoint paths and do not rely on resolving
64
+ a task-local `node_modules` binary. A cwd-dependent `tsx` launcher failed in
65
+ `live-1787838491136`; the absolute-path form completed the MCP route in
66
+ `live-1787838776163`.