Repository navigation
Replies: 1 comment
|
Disclosure: I wrote Tellal (MIT), a local panel that reads T3 threads aloud. Its use case matches this proposal, so I'm adding it here instead of opening a second discussion. Below are one more measured use case and two additions: message text and request events. Problem, measured Tellal needs to know when a thread's status changes, when an assistant message finishes (with its text), and when an approval or question opens.
What exists already
Shape (building on the proposal above) The command prints one NDJSON line per event. Each line has
On start it prints one Auth It's local only, like Out of scope
PR If a maintainer approves the direction and scope, I'll implement it as one focused PR. It would include the command, a small versioned line schema in Drafted with Claude Opus via omp in T3 Code |
Uh oh!
There was an error while loading. Please reload this page.
Problem
I run a daemon on each machine that coordinates T3 threads (agent-board). It starts threads with
t3 thread start. When a thread finishes, fails or waits for an answer, it sends the next message witht3 thread send. To notice those changes it currently has to:t3 thread list --jsonfor each project;--wait(ort3_thread_wait) for each run, which means one blocked process per thread and misses threads it didn't start (user-started, scheduled or delegated); orstatev2.sqlite, which is private, and long reads on it can stall the server (Any read transaction left open on statev2.sqlite freezes every server write once the WAL passes 32 MB #23482).Proposal
t3 thread list --jsonalready prints, so there's no new schema.t3 threadcommands: no outbound HTTP, signing secrets, retries or stored subscriptions.Related
t3_thread_watchfor an agent inside T3. This is the same signal for a coordinator that runs outside T3 as a plain process. If the server-side watch lands, this command could read from it.--all-projectswould match the flag in feat(cli): t3 thread list reaches linked environments and every project #31020.Alternatives considered
t3 thread list --json: works, but costs a process and a full read per project on every tick, and latency equals the poll interval.Stop, Codex equivalents): only some providers have them, and they don't report T3's own states, such as a pending approval, a settled or archived thread, or a run T3 marks failed.If the direction and scope look right, I can send a PR with the command, focused tests and a short paragraph in
docs/user/outside-agents.md. I'm also fine with a different shape you prefer, such as a--followflag ont3 thread list.All reactions