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.

Run three coding agents in real PTY terminals, turn tasks into agent sessions, resume native history, hand work across agents, and get notified only when a terminal needs attention. Local-first and MIT licensed.

Hi Product Hunt — I’m the maintainer of Termexo. The first release focused on putting Claude Code and Codex into one recoverable Windows workspace. Version 0.6 turns that workspace into a more complete agent workflow: - OpenCode is now a third first-class agent, with the same launch, resume, restart restoration, state tracking, and optional auto-confirm controls. - Tasks can carry a project, agent, model, priority, and acceptance criteria, then launch as real PTY terminals and move from backlog to running, completed, and accepted. - Prompt drafts and history are reusable assets, while sanitized handoff packages can carry Git context, verification, risks, and next steps between agents. - Claude background sessions can be inspected, forked, or attached instead of failing on the first message after a normal resume. - Tabs can be dragged, middle-clicked to close, switched with the wheel, and controlled from the keyboard. Termexo remains local-first: no Termexo account, no cloud relay, native session files stay read-only, and API keys stay in Windows Credential Manager. It is Windows-only today and available under the MIT License. I would especially value feedback from people who run several coding agents at once: where does your workflow lose the most context—task planning, approval, recovery, or handoff?

the session-resume story is what stood out - being able to close the laptop or have Windows update kick off a reboot and pick the Claude Code session back up by its native ID instead of starting a fresh context every time saves a genuinely annoying amount of re-explaining. the PTY grid layout for running several agents side by side is also just a nicer way to work than a pile of separate terminal tabs.

recovery only restores the layout and native session context, not a truly in-flight action - if the agent was mid-generation when the crash happened, that step still needs a manual restart. worth being upfront about in the onboarding rather than something you discover the first time it happens.

was just using raw Windows Terminal with a bunch of tabs and manually re-pasting context after any restart. also looked at running things through WSL to get a more Claude-Code-native feel, but wanted something that treats native Windows as a first-class target instead of a workaround.

Termexo

A local Windows workbench for Claude Code and Codex

A local Windows workbench for Claude Code and Codex

Termexo 0.6

Previous Termexo Launches

Previous Termexo Launches

What's great

What needs improvement

vs Alternatives

What's great

What needs improvement

vs Alternatives