Tri-State Relay Service is useful today as a local macOS relay inbox for coding-agent status updates. This roadmap captures likely directions without promising timelines.
The current integration model is intentionally simple: put one short TSRS instruction near the top of global or project agent instructions, and have agents call the local relay CLI at meaningful work transitions.
That has been working well for personal use, but there is room for smoother integrations:
- Agent hook examples for common CLI agents.
- Project templates that set line naming and update etiquette.
- MCP tools that let compatible agents enqueue relays without hand-writing shell commands.
- Safer defaults for when agents should send
update,complete,blocked, orneeds-inputrelays.
The goal is not to make agents chatty. The goal is to make important state changes easy to notice without watching every terminal.
Different voices per line would make TSRS easier to understand at a glance: your ear could learn which work stream is speaking before the message even finishes.
TSRS 2.1 adds optional provider line voices without making them part of the core product. Speechify can be configured with a user-owned API key, and Kokoro can be configured with a user-installed local venv and warm helper server. TSRS should still work well with the built-in macOS voice path and should not require a cloud or local model provider for normal use.
Future work could make provider setup easier, improve local voice quality, or add another optional provider for people who want richer per-line voices and are comfortable with the privacy, cost, and license tradeoffs.
When many lines have queued updates, TSRS should help summarize what matters instead of making you hear every stale message.
Possible directions:
- Better inactive-line rollups.
- A catch-up view for lines that accumulated several relays.
- Explicit blocked/needs-input prioritization.
- Local-first summaries where possible, with opt-in external summarizers for power users.
TSRS already tracks line-scoped source context. Future versions could make it easier to jump back to the right terminal, editor, browser tab, or project folder.
Any source action should stay user-initiated and line-scoped so TSRS does not act on the wrong agent context.
The active distribution direction is signed direct download with a standard installable relay CLI.
Future polish could include clearer update checks, better first-run diagnostics, and release notes that explain compatibility, voice behavior, and any Pro/customization features.