Skip to content

Pin T3 Code 0.1.9 on the agent host - #89

Merged
janclem merged 1 commit into
mainfrom
agent-host-t3-0-1-9
Nov 14, 2026
Merged

janclem merged 1 commit into
mainfrom
agent-host-t3-0-1-9

Conversation

@janclem

@janclem janclem commented Nov 14, 2026

Copy link
Copy Markdown
Owner

Pins npm:t3 to 0.1.9 in homelab/agent-host/mise.toml so the host matches the owner's 0.1.9 client. Nothing else changes. Renovate PR #79 (t3 0.1.8 plus other tools) is left alone. Work Graph ticket: agent-host-t3-0-1-9.

What 0.1.8 and 0.1.9 change for the host

Sources: v0.1.8 notes, v0.1.9 notes, and a diff of the docs and server source between the v0.1.7 and v0.1.9 tags.

  • No protocol change. ORCHESTRATION_PROTOCOL_VERSION is 2 at both tags (packages/contracts/src/environment.ts). The runbook's rule stays: move the client and the host together.
  • No new service or config requirement. ~/.t3/service.env needs nothing new. The service launcher moved to a hidden __service-launcher entry point (binCli.ts), so re-run t3 service install before the restart. The runbook's "Update the pinned tools" section already does that, so the runbook does not change.
  • Database migrations run on first start: 080_ScheduledTaskThreadMode and 081_ProjectionMessageSearchText. They are forward-only, so rolling back to 0.1.7 is not a clean pin revert.
  • Changes that affect this host:
    • Provider status checks no longer make mise download missing CLIs (#33448, 0.1.9).
    • Inactive threads auto-settle after 7 days by default (#32325, 0.1.8).
    • The background service launcher uses 75% less memory (#29284, 0.1.8).
    • Interactive npx t3 now offers to install a t3 command (#33150). It skips the offer when a t3 is already on PATH, as the mise shim is, and when not on a TTY.
  • Apply per Update the pinned tools: mise install, t3 service install, t3 service restart, with no T3 work running, and update the client in the same sitting.

Coordinator-relevant capabilities in 0.1.9

Feature 0.1.9 Also in 0.1.7?
Webhook automations: a scheduled task with an On webhook trigger, prompt placeholders, signatures, filters, dedupe and coalescing (docs) yes yes (same docs section; migrations 057, 058 and 067 are already in 0.1.7)
Public webhook ingress: only through T3 Connect's relay (/v1/hooks/... forwarded over the managed tunnel), with an optional 24-hour hold while offline (internals) yes yes (doc unchanged)
Scheduled tasks: interval, fixed time, once, or webhook (docs; MCP schedule_task, orchestrator MCP) yes yes; new since then: a one-thread destination with a fresh session per run (#30326), moving a task to another thread (#31379), and tasks linking to their thread (#31764), all in 0.1.8
Waking a thread from outside: t3 thread start/send/show/list on the host, where send queues the next turn and --wait waits for the reply (docs); remote MCP at https://<env>/mcp with OAuth; a webhook task bound to a thread posts into it yes yes, t3 thread and remote MCP; 0.1.8 adds the "Use T3 Code in another app" wizard (#33196) and 0.1.9 adds code-free agent sign-in via T3 Connect (#33600). There is no documented REST API besides MCP

The full sourced summary is in the ticket note.

@janclem
janclem merged commit 538720f into main Nov 14, 2026
7 checks passed
@janclem
janclem deleted the agent-host-t3-0-1-9 branch November 14, 2026 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant