Repository navigation
Replies: 2 comments 2 replies
|
+1, with a use case that needs one more thing from I keep my PC from auto-suspending while agents work (context in #7049). A small user service checks every 30 s whether any run is active. Today the only way to answer that across all projects is to read
Could Drafted with Claude Opus 5.5 (Claude Code) in T3 Code on my behalf. |
|
Whichever default you pick for Keeping |
Uh oh!
There was an error while loading. Please reload this page.
Hey! I'd like to get maintainer feedback on direction and scope for PR #32979, which adds read-only discovery commands to the
t3CLI.The problem
I run T3 Code on a headless home server, and a few personal bots and agents on the same machine and network talk to it. They can start and send to threads, but they can't find out what already exists without the app window or going through the cloud. Right now:
t3 projecthas no list commandt3 thread listonly covers the current projectt3 connect statusdoesn't show the environment's public MCP addressSo a local agent that wants to answer something simple like "what's running on project X" has no CLI way to do it. The only option is routing through MCP/OAuth over the relay, which feels like overkill when the agent is sitting right next to the server.
What the PR does
t3 project list [--json]lists project ids, titles, workspace paths, default provider/model and active thread counts by statust3 thread list [--project] [--status] [--json]lists threads across all projects by default, most recently updated firstt3 connect statusaddspublicAddressandmcpUrl, and never makes up an address when the link is missing or the lookup failsIt's all read-only. It uses the existing authenticated HTTP snapshot APIs with the local CLI session limited to orchestration read scope, so auth, pairing, exposure and Connect behavior don't change, and it doesn't touch SQLite directly.
What I'm asking
Is this direction OK, especially changing
thread listto cover all projects by default? I'm happy to narrow the scope, split it up or rework the interface. Things like worktree listing, scheduled tasks and full thread search are deliberately left out for later.Maria already merged
maininto the branch and checks pass, so it's in good shape if the direction works for you. Thanks!All reactions