@sjawhar/pi-envoy 9.7.1 → 10.0.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 +51 -17
- package/dist/dispatch.js +643 -225
- package/dist/envoy.js +870 -317
- package/dist/skills/dispatch/references/api.md +16 -3
- package/dist/skills/dispatch/references/issues.md +5 -1
- package/package.json +1 -1
|
@@ -6,9 +6,22 @@ commands do not cover.
|
|
|
6
6
|
## Agent authentication
|
|
7
7
|
|
|
8
8
|
Use a personal Dispatch token: a human mints it in Dispatch **Settings → Agent tokens** and supplies
|
|
9
|
-
it to the agent through `dispatch.token` in
|
|
10
|
-
|
|
11
|
-
|
|
9
|
+
it to the agent through `DISPATCH_TOKEN` or `dispatch.token` in the `envoy.json` the agent's
|
|
10
|
+
session reads. Under an Oh My Pi profile other than `default`, a Claude Code `CLAUDE_CONFIG_DIR` or
|
|
11
|
+
an OpenCode `OPENCODE_CONFIG_DIR`, that is the `envoy.json` in the session's own directory; any
|
|
12
|
+
other session reads the file `ENVOY_CONFIG_FILE` names when it is set, else
|
|
13
|
+
`~/.config/legion/envoy.json` (under `$XDG_CONFIG_HOME` when set). The plugin hands the path it
|
|
14
|
+
chose to the session's commands in `ENVOY_CONFIG_FILE` beside `DISPATCH_HOST`, and the `dispatch`
|
|
15
|
+
command reads the file `ENVOY_CONFIG_FILE` names whenever `DISPATCH_HOST` is set, else its host
|
|
16
|
+
plugin's rule; in a Claude Code Bash that lacks both, as a subagent's can,
|
|
17
|
+
`CLAUDE_CODE_CHILD_SESSION=1` makes the host `claude`, so the command reads `CLAUDE_CONFIG_DIR`'s
|
|
18
|
+
file. A `dispatch.token` written `!<command>` is a command whose output is the token. A checkout's
|
|
19
|
+
`.envoy/envoy.json` may set `dispatch.serverUrl` only with the `dispatch.token` beside it, and
|
|
20
|
+
`dispatch.token` only with its own `dispatch.serverUrl` beside it; an `envoy` section there is not
|
|
21
|
+
read. The file's token goes only to its own `dispatch.serverUrl`: a
|
|
22
|
+
`DISPATCH_URL` naming another server needs `DISPATCH_TOKEN` or `DISPATCH_TOKEN_FILE`. The server
|
|
23
|
+
records the minting human as the owner of that session's writes.
|
|
24
|
+
`DISPATCH_AGENT_TOKEN` is the shared devbox fallback; do not configure it for an individual agent.
|
|
12
25
|
|
|
13
26
|
The deployed Dispatch server's browser origin is configured separately with
|
|
14
27
|
`DISPATCH_SERVER_URL` in the deployment `compose/.env`. Do not change an
|
|
@@ -107,7 +107,11 @@ Link the pull request that delivers the issue with `--external-link` when you op
|
|
|
107
107
|
renders its state and checks from that link, and `dispatch read` lists it under `External links:`.
|
|
108
108
|
The command is authenticated with the same bearer as every
|
|
109
109
|
other `dispatch` command: a Legion pane reads it from the `DISPATCH_TOKEN_FILE` path the daemon sets on
|
|
110
|
-
the pane;
|
|
110
|
+
the pane; any other session's `dispatch` command reads `dispatch.token` from the `envoy.json` its
|
|
111
|
+
host's plugin read, which the plugin hands it in `ENVOY_CONFIG_FILE`. By that plugin's rule, that
|
|
112
|
+
is an OMP session's profile directory under an omp profile other than `default`, a Claude Code
|
|
113
|
+
session's `CLAUDE_CONFIG_DIR` (its subagents' too) or an OpenCode session's `OPENCODE_CONFIG_DIR`,
|
|
114
|
+
else the file `ENVOY_CONFIG_FILE` names, else `~/.config/legion/envoy.json`.
|
|
111
115
|
|
|
112
116
|
A write to an issue still in `triage` answers once with `… is still in triage …`; move the status
|
|
113
117
|
when work has started.
|