Attyx

Attyx has a clear thesis and executes it narrowly, which is the right approach for a terminal. The core observation is that a terminal emulator used to be judged on rendering speed and keybindings; once your panes are running Claude Code, Codex, opencode, or pi.dev, the thing you actually need to see is which agent is working, which is waiting on you, and what each one is costing. Attyx answers that with a per-pane colored dot and a cross-session dashboard listing state, elapsed time, input/output tokens, context-window fill (the sample shown reports values like 82k/200k and 55k/256k), and estimated dollar cost per agent with a session total. Strengths. The agent-awareness is sourced properly rather than guessed: Claude and Codex lifecycle come through JSON hooks and opencode and pi.dev through event-bus extensions, so the status is deterministic instead of scraped from screen text. The programmability layer is unusually deep for a terminal — stable pane IDs, a Unix-socket IPC layer, an attyx CLI with split/send-keys/get-text/watch subcommands, and a native MCP server over stdio or 127.0.0.1:7333/mcp, plus attyx skill install to hand Claude Code typed control of the terminal. The engineering footprint is small and honest: Zig 0.15, a single binary under 5 MB, Metal and OpenGL rendering, no Electron or Chromium. Standard terminal expectations are not sacrificed — Kitty graphics and keyboard protocols, OSC 8 hyperlinks, bracketed paste, IME support for CJK, synchronized output, DECSTBM scroll regions, reflow on resize, 24-bit true color, and a tmux-style daemon backing sessions. Weaknesses and fit. This is an operator console for people running agents, and the configuration story assumes you are comfortable editing attyx.toml — there is no GUI settings panel. Agent lifecycle detection is explicitly scoped to Claude Code, Codex, opencode, and pi.dev; an agent outside that list gets no status dot. GPU acceleration means Metal on macOS and OpenGL on Linux, and the documented platforms are macOS (Apple Silicon and Intel) and Linux (x64 and ARM64), with no Windows build described. Users migrating off iTerm2, tmux, or Kitty for their plugin ecosystems will find Attyx deliberately has no plugin marketplace — instead you get the CLI and MCP surface as the extension mechanism. Where it fits. Solo developers or small teams running several agents in parallel who want one screen showing what needs attention and what it costs. Where it doesn't: someone who wants a friendly general-purpose terminal, someone on Windows, or someone whose workflow depends on a large third-party plugin library rather than scripted control.