Termexo

Termexo is a Windows desktop application that consolidates multiple AI coding agent terminals — Claude Code, Codex CLI, and compatible providers — into a single recoverable workspace. Built with Tauri 2 and Angular 22, it runs entirely on your local machine with no account or cloud service required. The current release is v0.3.9, described by the project as the "restored-session and attention workflow update."

What It Is

Termexo acts as a local control plane for AI coding agents. Instead of juggling separate terminal windows for each agent and project, it provides a unified workbench where developers can see all running agents at once, get notified when one needs input or approval, resume past sessions, and switch model providers without rebuilding their setup. The project describes its organizing unit as the Workspace, which persists folder paths, grid layouts, terminal tabs, model profiles, and themes across restarts.

How the Workbench Works

The core interface is a configurable grid of real PTY terminals — up to 6 rows by 6 columns — where each cell can host a Claude Code or Codex session. Key workbench behaviors include:

• Unlimited tabs: Every session stays alive in a tab; only selected panes are shown in the active grid.
• Per-workspace memory: Project folder, grid layout, open terminals, model assignments, and color theme all restore on reopen.
• Maximize modes: Individual terminals or the full workspace can be maximized and restored with Shift+Esc.
• No Termexo account: All state is stored in a local SQLite database; API keys go into Windows Credential Manager, never a plain-text config file.

Agent Status and Attention System

A central design goal is making agent state observable across all open projects simultaneously. Termexo maps agent-specific lifecycle events into common states — thinking, waiting for input, waiting for approval, completed, and failed — and surfaces them in three ways: a persistent in-app banner, a native Windows notification, and a taskbar flash. The v0.3.9 release added Codex lifecycle hooks covering prompts, tools, permissions, compaction, subagents, completion, and session boundaries to bring Codex status tracking in line with Claude Code.

Session Recovery and Model Routing

Termexo reads Claude Code and Codex session files as read-only and uses the CLIs' own resume commands (claude --resume and codex resume) to restore full historical context. The session center lets developers search across all projects by name, path, branch, or model. For model routing, the same Claude Code CLI can be pointed at Anthropic, DeepSeek, MiniMax, GLM, or any Anthropic-compatible endpoint by saving provider credentials as named profiles and switching them in two clicks — applying the change to every Claude terminal in a workspace at once.

Architecture and Security Boundaries

The application is built on Tauri 2 (Rust core) with an Angular 22 frontend. The internal data flow runs: Angular UI → Tauri IPC commands → PTY Service → agent processes, with a hooks pipeline receiving agent lifecycle events and writing deduplicated state to SQLite. Security boundaries are explicit by design: API keys are stored only in Windows Credential Manager, the frontend can only read whether a key exists (never its value), and native agent session files are never modified or deleted by Termexo.

Update: v0.3.9 — Restored-Session and Attention Workflow

The latest release (published 2026-08-01) focuses on two areas. First, session restoration: Claude launch commands, model profiles, credentials, provider URLs, and hook environments are now rebuilt before mounting terminals, and a legacy MiniMax profile naming issue that caused restored sessions to fall back to Claude Sonnet is fixed. Second, attention: persistent waiting/approval banners, Windows notifications, and taskbar alerts are added for blocked agents, while completed-task feedback is kept concise. The roadmap shows v0.4 in active development, targeting one-click CLI installation/upgrades, network proxy profiles, and plan quota monitoring, with multi-agent collaboration and remote/mobile access planned for v0.5–v0.7.