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.