Launching today
Termexo
A local Windows workbench for Claude Code and Codex
32 followers
A local Windows workbench for Claude Code and Codex
32 followers
Termexo brings Claude Code and Codex into one recoverable Windows workspace. Arrange real PTY terminals in custom grids, search and resume native sessions, get notified when an agent needs approval, and switch Claude-compatible model profiles without rebuilding environment variables. Local-first, no Termexo account required.
Termexo
Alerting when an agent needs attention is the right primitive. The one nobody builds is the opposite alert, for the agent that's quietly burning your tokens on a loop going nowhere. The profiles already hold the API key, so you could put spend per session next to each PTY tab, and that number changes behaviour faster than any layout feature will. Running two agents at once and having no idea which one ate the budget is the part that actually costs me.
Windows-native is the underserved half of this space ā most of the agent tooling assumes macOS, and the WSL workaround means your agent and your editor disagree about what a path is.
Does it run the agent inside WSL, on native Windows, or does it let you pick? I ask because the path translation is where I'd expect the friction to actually live. An agent that writes /home/user/... into a config a Windows tool has to read is the kind of thing that works in the demo and breaks in week two.
Storing API keys in Windows Credential Manager instead of a config file is the kind of detail that gets this trusted fast.