Watch a GitHub PR and notify an existing T3 Code conversation when something changes.
Three MCP tools: watch, list, and stop. watch automatically starts a background worker that polls every 60 seconds without invoking a model. It survives MCP disconnection and exits when there is nothing left to watch. No skill or service installation is required.
With T3 running:
npx t3poll@latest setupThe wizard discovers T3, configures Codex with T3-only tools, preserves existing launch arguments, backs up changed files, and verifies the connection. Add --dry-run to preview. Use npx t3poll@nightly setup to follow automatic nightly releases. Stable releases are promoted manually.
For development from a checkout:
npm ci
npm run build
node dist/cli.js setup --runtime-path ./dist/cli.jsSee the installer guide and release process.
Copy this into your coding agent:
Set up t3poll for Codex sessions inside my running T3 Code instance.
Read https://github.com/eimexdev/t3poll/blob/master/docs/agent-setup.md and follow it.
Use the published npm setup installer, preview the changes, then apply them.
Preserve my running T3 server, conversations, and unrelated configuration.
Verify the installation without creating a watch or sending a test message.
The agent setup guide covers discovery, credentials, configuration, and verification. Once installed, ask the agent to watch a PR and choose its destination conversation.
You need Windows x64, macOS, or Linux, Node.js 24.10+, GitHub CLI signed in, and a compatible T3 server. Use the setup installer for standard installations. For deliberate manual configuration or a development checkout, follow the manual steps and preserve T3-only scope.
No URL or token settings are needed for a standard local installation. If multiple instances are found, select one with T3POLL_BASE_DIR. Choose the destination thread when registering each watch.
Ask your agent to watch a PR, list watches, or stop one. It can find destination IDs with list { "threads": true }.
The CLI provides the same operations. From the checkout, with T3 running:
node dist/cli.js watch https://github.com/owner/repo/pull/123 --thread THREAD_ID
node dist/cli.js list
node dist/cli.js stop WATCH_IDNotifications contain a short description and links. The agent reads comments and logs with its existing GitHub tools. Running threads receive updates as steering through T3. Startup and approval/input prompts hold delivery, with a readiness check every 15 seconds. Watches expire after 24 hours or finish after notifying about closure/merge.
See monitoring behavior for notification examples, polling options, retries, and recovery after a reboot.
npm installations resolve their selected release channel when a new Codex session starts. A newer runtime takes over the shared worker after its current operation finishes. Watches keep their IDs, expiration, baseline, queued changes, and pending delivery IDs. Older sessions keep using the newer worker.
To trigger an update immediately, run npx --yes --prefer-online t3poll@nightly list, or use @latest for stable. This updates the worker; existing MCP sessions keep their loaded code until reconnected. MCP startup resumes saved watches and checks worker health every 30 seconds. There is no background registry polling.
Local rebuilds with an unchanged version require waiting for the worker to exit.
See update behavior for failure recovery, channel switching, and compatibility. State lives outside the package in ~/.local/share/t3poll by default.
Automatically created credentials last 30 days. t3poll replaces them on use during their last day or after expiration, including from the background worker. Explicitly supplied token files remain your responsibility.
npm ci
npm test
npm run checkSee compatibility and test evidence and the future webhooks decision.
Licensed under the MIT License.