Idea: Headless / Terminal companion interface (t3 prompt / t3 exec) over WebSocket RPC

[OmarAlaaeldein]

Motivation

T3 Code provides a great experience across desktop, web, and mobile. However, in certain environments—such as SSH sessions, remote devcontainers, or quick terminal-focused tasks—launching a browser or Electron desktop window adds friction.

Concept

An optional terminal interface harness that interacts directly with an existing local T3 Code server instance using the established WebSocket RPC (WsRpcGroup) and HTTP snapshot APIs:

• Zero server changes: Connects to the existing running server daemon just like the web or mobile clients.
• Interactive turns: Streams tokens directly to stdout, handles tool activity & approvals interactively, and attaches to existing project threads.
• Non-breaking CLI: Strictly scoped under dedicated subcommands (t3 prompt / t3 exec), preserving t3 as the server entrypoint.

Question for Maintainers

Before opening any PRs, we wanted to check:

1. Would the maintainers be open to an official terminal subcommand in the core repo if kept minimal (<400 lines) and easily maintainable?
2. Or would you prefer terminal interfaces to live as external companion packages outside the core monorepo?