@devries-cameron20 / t3code-1 / commits / 50e151c7a4
Fork 0

The best way to control Claude Code, Codex and more from any computer or phone

docs(connect): correct the relay webhook endpoint key (#23526)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Julius Marminge committed Oct 22, 2026 at 21:43 UTC 50e151c7a41460649ad7e63acbb00c03e5175c18
1 file changed +4 -3
docs/internals/t3-connect.md
+4 -3
@@ -5,9 +5,10 @@ credentials for reaching environments, and managed tunnel allocations. After
5 bootstrap, clients send application traffic through the environment's tunnel
6 hostname; the relay Worker does not proxy their HTTP or WebSocket sessions.
7 The one exception is automation webhooks: the relay forwards
8 -`/v1/hooks/:environmentId/:hookId/:token` to the environment's tunnel so
9 -senders get a stable URL. It keeps bodies and tokens out of its traces and
10 -leaves token and signature verification to the environment
8 +`/v1/hooks/:endpointKey/:hookId/:token` to the environment's tunnel so
9 +senders get a stable URL. `endpointKey` is the 16-hex hash suffix of the
10 +managed tunnel's name, not the environment id. It keeps bodies and tokens out
11 +of its traces and leaves token and signature verification to the environment
12 ([forwarder](../../infra/relay/src/hooks/HookForwarder.ts)).
13
14 By default the forwarder stores nothing. An environment can opt in to having