@sjawhar/pi-legion-envoy 1.12.0 → 1.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.
|
@@ -36,6 +36,12 @@ it to the agent through `dispatch.token` in `~/.config/opencode/envoy.json` or `
|
|
|
36
36
|
The server records the minting human as the owner of that session's writes. `DISPATCH_AGENT_TOKEN`
|
|
37
37
|
is the shared devbox fallback; do not configure it for an individual agent.
|
|
38
38
|
|
|
39
|
+
The deployed Dispatch server's browser origin is configured separately with
|
|
40
|
+
`DISPATCH_SERVER_URL` in the deployment `compose/.env`. Do not change an
|
|
41
|
+
agent's `envoy.json` to set the GitHub OAuth callback origin: the value must
|
|
42
|
+
be the exact URL humans type in their browser, and the GitHub App callback is
|
|
43
|
+
`<DISPATCH_SERVER_URL>/auth/callback`.
|
|
44
|
+
|
|
39
45
|
## Writing a spec
|
|
40
46
|
|
|
41
47
|
A spec has two readers: the human who decides reads the top; the implementer who builds reads the
|