chore: update llm-agents for T3 Code 0.1.0 #7

Merged
marti merged 1 commit from chore/update-llm-agents into main 2026-10-19 14:47:47 +02:00
Owner

Why

After #5 and #6, T3 Connect sign-in works, but making this machine a server fails: relay.t3.codes answers the environment link with 503 managed_endpoint_provisioning_failed (trace IDs 15885ada4acab140a693c3e83c6f8d12, 6c25f1c3e2d38149588aa18fa25177e8). The cause is likely the version: this flake pinned T3 Code 0.0.45, while the hosted relay runs the 0.1.0 code.

Between v0.0.45 and v0.1.0 upstream reworked managed endpoint provisioning: it verifies tunnels with Cloudflare and treats older hosts as legacy, and its error text says a host whose tunnel was released "needs a current T3 Code build to get a new one". The bundled relay client also moved from cloudflared 2026.5.2 to 2026.10.0.

Change

nix flake update llm-agents (42e4070 -> 8fa7ff4), which carries T3 Code 0.1.0 (llm-agents 4daedfc, "t3code: 0.0.45 -> 0.1.0"). Other agents move too:

Package Before After
t3code 0.0.45 0.1.0
claude-code 2.1.299 2.1.303
codex 0.162.1 0.163.0
opencode 1.19.0 1.19.3
pi 1.2.0 1.3.0

Upstream also renamed the app to "T3 Code (Beta)". Login and data in ~/.t3/userdata are unaffected; Electron's own profile directory may start fresh.

Testing

  • nix flake check passes.
  • Built the T3 Code 0.1.0 desktop output with this module's override: both --replace-fail patches from #5 still apply (execTarget: "t3code-desktop" twice in main.cjs), the web bundle has clerkJwtTemplate: `t3-relay` from #6, and the server pins cloudflared 2026.10.0.
  • Not yet tested: linking this machine through T3 Connect after switching. If it still fails on 0.1.0, it is a relay-side issue to report upstream with the trace IDs.

🤖 Generated with Claude Code

## Why After #5 and #6, T3 Connect sign-in works, but making this machine a server fails: `relay.t3.codes` answers the environment link with 503 `managed_endpoint_provisioning_failed` (trace IDs `15885ada4acab140a693c3e83c6f8d12`, `6c25f1c3e2d38149588aa18fa25177e8`). The cause is likely the version: this flake pinned T3 Code 0.0.45, while the hosted relay runs the 0.1.0 code. Between v0.0.45 and v0.1.0 upstream reworked managed endpoint provisioning: it verifies tunnels with Cloudflare and treats older hosts as legacy, and its error text says a host whose tunnel was released "needs a current T3 Code build to get a new one". The bundled relay client also moved from cloudflared 2026.5.2 to 2026.10.0. ## Change `nix flake update llm-agents` (42e4070 -> 8fa7ff4), which carries T3 Code 0.1.0 (llm-agents 4daedfc, "t3code: 0.0.45 -> 0.1.0"). Other agents move too: | Package | Before | After | | --- | --- | --- | | t3code | 0.0.45 | 0.1.0 | | claude-code | 2.1.299 | 2.1.303 | | codex | 0.162.1 | 0.163.0 | | opencode | 1.19.0 | 1.19.3 | | pi | 1.2.0 | 1.3.0 | Upstream also renamed the app to "T3 Code (Beta)". Login and data in `~/.t3/userdata` are unaffected; Electron's own profile directory may start fresh. ## Testing - `nix flake check` passes. - Built the T3 Code 0.1.0 desktop output with this module's override: both `--replace-fail` patches from #5 still apply (`execTarget: "t3code-desktop"` twice in `main.cjs`), the web bundle has ``clerkJwtTemplate: `t3-relay` `` from #6, and the server pins cloudflared 2026.10.0. - Not yet tested: linking this machine through T3 Connect after switching. If it still fails on 0.1.0, it is a relay-side issue to report upstream with the trace IDs. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
The hosted T3 Connect relay no longer provisions a managed endpoint for
0.0.45 hosts (managed_endpoint_provisioning_failed), so this machine could
not be made available as a server. 0.1.0 reworks endpoint provisioning and
moves the relay client to cloudflared 2026.10.0.

Also moves claude-code 2.1.299 -> 2.1.303, codex 0.162.1 -> 0.163.0,
opencode 1.19.0 -> 1.19.3 and pi 1.2.0 -> 1.3.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
marti merged commit e63ea7cdf7 into main 2026-10-19 14:47:47 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
marti/agent-env!7
No description provided.