0.3.0 — desktop connections by default

The MCP now uses T3's desktop connections by default. Register t3code-thread-mcp with no arguments or tokens. Explicit direct-connection configuration still takes precedence.

Install:

npm install -g https://github.com/samdickson22/t3code-thread-mcp/releases/download/v0.3.0/t3code-thread-mcp-0.3.0.tgz

Desktop discovery requires a running T3 build containing pingdotgg/t3code#12148. This upstream change is not merged yet. Desktop mode supports macOS/Linux; Windows can use direct connections.

17 existing tests pass. Verified real Astra/Fable thread creation, messaging, settlement, and revival between a Mac mini and physical MacBook Air through T3 Connect. Screenshot attached.

Desktop connections preview 0.3.0-next.2

Preview of desktop connection-manager support. Requires a desktop build containing pingdotgg/t3code#12148; existing released T3 builds do not support this mode.

Install globally:

npm install -g https://github.com/samdickson22/t3code-thread-mcp/releases/download/v0.3.0-next.2/t3code-thread-mcp-0.3.0-next.2.tgz

Register t3code-thread-mcp --desktop with your MCP host. Keep the bridge-enabled desktop open. No parent thread, remote URL, or token is required. Direct-connection configuration remains available.

Validation: 17 standalone tests passed (one opt-in live test skipped); 32 native focused tests and three package typechecks passed. Independent Codex reviews signed off both implementations. A real Astra-low controller on a Mac mini used the desktop's T3 Connect connection to create and message a Fable 5.1-low thread on a physical MacBook Air, settle it, and revive it with retained history. The attached screenshot shows both replies. The packaged global install separately discovered both live environments.

Live SSH transport was not separately tested. This does not automatically register MCP tools in remote providers or add native conversation-fork support.

Desktop mode is enabled on macOS and Linux only. Windows desktop mode fails closed pending authenticated named-pipe support; direct connection configuration remains available.

Desktop connections preview 0.3.0-next.1

Superseded preview. Use v0.3.0-next.2, which disables unverified Windows desktop named-pipe connections. This version remains for provenance only.

Global T3 thread management 0.2.0

The MCP now starts in global mode without a parent/source thread ID. One installation can manage projects and threads across named, authenticated T3 environments.

Install globally:

npm install -g https://github.com/samdickson22/t3code-thread-mcp/releases/download/v0.2.0/t3code-thread-mcp-0.2.0.tgz

Configure one server with T3_URL and T3_ACCESS_TOKEN, or several servers through the config file described in the README. Register the executable with the MCP host on each computer where agents should use it. Remove T3_SOURCE_THREAD_ID to use global mode; setting it explicitly retains the original project-scoped tools for existing coordinators.

Added environment/project/provider discovery, project creation, cross-project and cross-environment operations, optional sender attribution, rename, pin/unpin, snooze/unsnooze, archive/unarchive, deletion, and pending-request management. Existing messaging, waiting, interruption, and settlement tools also work globally.

Validated through the globally installed executable on T3 0.0.40 and 0.0.42. Real Astra-low on one environment created Fable-low on another; Fable called the MCP to message Astra back. Browser screenshots and lifecycle evidence are in GLOBAL-E2E.md.

Limits: these tests used separate server environments on one Mac. Every remote computer needs a reachable authenticated T3 server. This release does not provide native conversation forks or session handoff between hosts. T3 requires unarchiving before its public API exposes a conversation's history. Same-thread provider migration remains subject to T3 restrictions.

T3 peer-thread MCP 0.1.3

Read consistency checks now use existing per-thread page watermarks when other projects advance the global sequence. Unrelated activity no longer exhausts read retries. Seven focused tests, exact native tool-contract comparison, and the real released T3 0.0.40 Astra low/Fable exchange and settle/revive matrix pass. Tool schemas are unchanged.

T3 peer-thread MCP 0.1.2

Thread reads now require matching shell/history projection sequences, with bounded retries if work changes during the read. Interrupt and settlement advertise destructive hints matching the native tools. Six focused stdio tests and the real released T3 0.0.40 Astra low/Fable exchange, settlement, and revival test pass. Exact native contract comparison passes.

T3 peer-thread MCP 0.1.1

Fix retry-ID collisions when caller IDs or retry IDs contain delimiters. Native and standalone implementations encode both components identically. Five focused stdio tests pass; the live provider test was not rerun for this patch. Tool schemas are unchanged. Earlier live provider and remote-browser evidence remains attached to v0.1.0.

T3 peer-thread MCP 0.1.0

Compatibility MCP for T3 Code 0.0.40. Includes the same seven peer-thread tools as the native proposal. Validated with real GPT-6 Astra low and Claude Fable 5.1 peer conversations; validation notes and remote-browser screenshots attached.