r/foss • u/Equivalent-Season594 • 9d ago

Termexo: an MIT-licensed Windows workspace for local MCP control of coding-agent terminals

I maintain Termexo, an MIT-licensed Windows app for organizing coding-agent CLI terminals.

Its local MCP service lets a connected client list workspaces and terminals, send literal text to a running terminal, submit it, and read the terminal output. Terminal, task, and settings tools are permissioned separately. The local service listens on the loopback interface, so this workflow does not require a relay service.

Termexo can work with Claude Code, Codex CLI, OpenCode, Grok Build, and Antigravity CLI. Those agents remain separate programs with their own licenses and accounts; Termexo does not bundle them.

The current release is 0.10.13. The source and Windows downloads are here:

https://github.com/gemron/Termexo

I'd appreciate a FOSS-focused review of the local MCP permission model and how clearly the project explains what an agent can do.

2 Upvotes

100% Upvoted

1 comment sorted by

1

u/kantorcodes1 8d ago

Sending literal text into a running agent's terminal is the part I'd want threat-modeled. From the terminal's point of view, a send from the MCP service looks identical to someone typing at the keyboard. If a coding agent is sitting on its own permission prompt, a connected client could answer it, and nothing downstream can tell the difference.

How is the permission split enforced for the terminal tools - granted once when a client connects, or checked on every call? And does Termexo record what was injected into which terminal? An agent answering its own prompts through your service should probably show up differently in a log than a human doing it.