Claudraband: Persistent Sessions and Programmatic Control for Claude Code

Claudraband is a wrapper for the Claude Code TUI that introduces session persistence and programmatic control. It features an HTTP daemon for remote access and an ACP server for integration with external editors like Zed. By leveraging tmux, it allows users to resume sessions, answer pending prompts, and automate AI workflows through a TypeScript library.

Key Points

• Enables persistent and resumable Claude Code sessions that can be continued or interrogated later via the 'cband' CLI.
• Provides an HTTP daemon and ACP server to allow remote access and integration with third-party frontends and code editors.
• Includes a TypeScript library for programmatically driving Claude Code workflows and building custom AI-powered tools.
• Utilizes tmux as the primary terminal runtime to manage live sessions, with an experimental xterm backend for headless fallbacks.
• Requires a pre-authenticated installation of the official Claude Code TUI, as it does not bypass OAuth or the core TUI logic.

Sentiment

The discussion is generally positive toward Claudraband, with most commenters appreciating the problem it solves. The main criticism around vendor lock-in is acknowledged constructively by the author, who explains why Claude Code specifically needs this tooling. The community is supportive but pragmatic, raising valid concerns about licensing and ToS that the author addresses promptly.

In Agreement

• Claude Code uniquely lacks the programmatic control and session persistence that competitors like Codex and Gemini CLI already offer, making a wrapper like Claudraband a necessary solution
• The tool wraps the official TUI without bypassing authentication or impersonating the client, making it ToS-compliant and a legitimate extension of Claude Code's capabilities
• The tmux-based approach to session control is cleaner and more streamlined than ad-hoc shell scripting alternatives that other developers have independently built
• Power users of Claude Code genuinely exist and benefit from tools that enable hooks, custom commands, agent teams, and automated workflows beyond basic chat interaction

Opposed

• By only supporting Claude Code, the tool contributes to Anthropic lock-in and should be generic enough to support Gemini CLI, Codex, and OpenCode as well
• The concept of a 'Claude Code power user' is questioned as potentially oxymoronic, implying that heavy tooling around an AI coding assistant may be over-engineering the workflow
• Wrapping a TUI in tmux is a fragile approach — Claude Channels or other native APIs would be more robust, though they have their own limitations