Repository navigation
Pin T3 Code 0.1.9 on the agent host - #89
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pins
npm:t3to 0.1.9 inhomelab/agent-host/mise.tomlso 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.7andv0.1.9tags.ORCHESTRATION_PROTOCOL_VERSIONis 2 at both tags (packages/contracts/src/environment.ts). The runbook's rule stays: move the client and the host together.~/.t3/service.envneeds nothing new. The service launcher moved to a hidden__service-launcherentry point (binCli.ts), so re-runt3 service installbefore the restart. The runbook's "Update the pinned tools" section already does that, so the runbook does not change.080_ScheduledTaskThreadModeand081_ProjectionMessageSearchText. They are forward-only, so rolling back to 0.1.7 is not a clean pin revert.npx t3now offers to install at3command (#33150). It skips the offer when at3is already onPATH, as the mise shim is, and when not on a TTY.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
/v1/hooks/...forwarded over the managed tunnel), with an optional 24-hour hold while offline (internals)schedule_task, orchestrator MCP)t3 thread start/send/show/liston the host, wheresendqueues the next turn and--waitwaits for the reply (docs); remote MCP athttps://<env>/mcpwith OAuth; a webhook task bound to a thread posts into itt3 threadand 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 MCPThe full sourced summary is in the ticket note.