Developer kkrausse has released Faplex, an early alpha tool that acts as a status multiplexer for AI coding harnesses including Claude Code, Codex, and OpenCode. Unlike competitors that attempt to become your terminal or wrap your session, Faplex simply reads what the harness daemons report and opens the native CLI when you select a session. The tool is designed to work across any machine accessible via SSH, providing a unified view of active, waiting, and finished sessions without requiring complex setup or plugins on remote hosts.

Zero-Intrusion Architecture

The core philosophy of Faplex is that it owns neither the terminal nor the conversation. It does not install hooks, plugins, or wrappers, and it does not keep persistent panes for every session. When you open a row in the Faplex dashboard, it executes the harness's native attach commandβ€”such as claude attach or codex resumeβ€”handed directly to your terminal. This ensures that every harness feature works exactly as it would without Faplex. Idle sessions cost no extra resources because Faplex does not maintain live CLI instances for them; it only opens a client when you actively view a session, closing it after 15 minutes of inactivity.

Multi-Machine Visibility and Control

Faplex aggregates sessions from multiple machines into a single, real-time list categorized by status: Working, Needs Input, Finished, and Archived. The interface displays critical context like token counts and active subagent numbers directly in the row. Configuration is minimal; users can specify SSH aliases or hosts directly in the command line (e.g., faplex devbox pi) without writing a config file. For persistent setups, a config.json allows defining machines, default directories, and display colors. The tool relies on shared SSH connections using ControlMaster sockets to minimize overhead, though users must be aware of default sshd limits on concurrent sessions per connection.

Harness Compatibility and Limitations

The tool currently supports Claude Code, OpenCode 2.x, and Codex, with specific requirements for each. Claude Code requires the agents --json flag and background jobs; interactive sessions are listed but marked as view-only. OpenCode relies on its background service HTTP API, while Codex uses the app-server daemon via a WebSocket socket. Faplex explicitly notes that it does not parse terminal output or speak the harness's conversation protocol, making it resilient to UI changes in the underlying tools. However, it depends on recent daemon features, meaning older versions of these harnesses may not be supported. An e2e testing rig using Docker is available for developers to verify compatibility with specific harness versions.

Key Takeaways

  • Faplex is a status list and launcher, not a terminal multiplexer; it opens native harness CLIs for full feature access.
  • It supports multi-machine aggregation via SSH without requiring any software installation on remote hosts.
  • The tool is in early alpha and relies on recent daemon APIs from Claude, Codex, and OpenCode.
  • It minimizes resource usage by closing inactive session clients after 15 minutes, unlike tools that keep panes alive.
  • Configuration is optional and can be done entirely via command-line arguments for temporary multi-host setups.

The Bottom Line

For developers juggling multiple AI coding agents across different machines, Faplex offers a refreshing 'hands-off' approach that respects the native workflows of Claude and Codex. It solves the visibility problem without the baggage of becoming a new terminal dependency. While still in alpha, its architecture suggests a sustainable path for agent orchestration that doesn't fight against the rapid evolution of the harnesses themselves.