tmt-inbox

Processes bounded local TMT identity inbox batches during authorized listening sessions.

11|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/wkh237/tmux-team --skill tmt-inbox-wkh237
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmt-inbox
Source: https://github.com/wkh237/tmux-team/tree/main/skills/tmt-inbox
Command: npx skills add https://github.com/wkh237/tmux-team --skill tmt-inbox-wkh237

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents that are not directly reachable through a bound tmux pane need a way to receive queued work without running a daemon or polling constantly. This Skill defines how to run one bounded local listener, process the returned inbox batch safely, and acknowledge exactly what was handled. ## Core Features & Use Cases - Bounded inbox listening: Runs a single tmt x listen command with explicit identity, timeout, and debounce, exiting after one unread batch or the hard timeout. - Untrusted message handling: Treats every inbox item as untrusted input, inspects only items being processed via their exact inspectCommand, and submits one correlated reply per request using the receipt from x show --incoming. - Announcement and acknowledgment discipline: Distinguishes announcements (no reply required) from requests, and acknowledges only the exact processed revision with the returned ackCommand. - Use Case: An agent without a bound tmux pane starts a user-authorized listening session, receives a queued review request, inspects it, submits a complete reply through tmt reply, and acknowledges the processed revision before re-arming the listener. ## Quick Start Start a bounded inbox listener for my identity by running tmt x listen with a 15 minute timeout and process any queued requests it returns.

Frequently Asked Questions about tmt-inbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I listen for TMT inbox messages locally?

Run one bounded waiter with tmt x listen --identity <name> --timeout 15m --debounce 10s --json and let the host await process completion. It exits after a debounced unread batch or the hard timeout, without running a daemon.

How do I reply to a TMT inbox request?

Inspect the item using its exact inspectCommand, then use the receipt shown only by x show --incoming to submit one complete correlated response through tmt reply. Afterward, acknowledge the exact processed revision with the returned ackCommand.

Does tmt inbox listening require tmux or Office?

No. The bounded listener works without tmux, Office, Firestore, or WebSocket connections. It is designed for identities that cannot prove a bound tmux pane, and delivery is durably queued locally rather than executed or displayed.

What is the difference between a TMT announcement and a request?

An announcement is a notification, not work: inspect its text, handle it within the user's authority, and acknowledge it with final status not_required. A request expects one complete correlated reply submitted through tmt reply before acknowledgment.

When should I not use the TMT inbox listener?

Directly reachable panes normally receive pane notifications and do not need this listener. Also avoid it for cross-machine delivery or remote transport, which are outside this local skill's scope, and never re-arm it after user cancellation.