Claudraband provides power users with enhanced control over the Claude Code TUI, enabling persistent, resumable, and remotely accessible AI workflows. It addresses the need for non-interactive, automated interactions with Claude Code by wrapping the official TUI in a managed terminal environment. This allows for advanced use cases such as background processing, remote control via an HTTP daemon, and integration with other tools through an ACP server, benefiting developers and advanced users seeking to automate or extend Claude's capabilities.

How It Works

Claudraband acts as a sophisticated intermediary, managing live Claude Code sessions. It leverages tmux by default for robust session persistence and recovery, offering an alternative experimental xterm.js backend for headless scenarios. Core functionalities include maintaining session state, allowing resumption of interrupted conversations, and exposing sessions via an HTTP daemon for remote access or an ACP server for integration with editors and other clients. All interactions are routed through a real, authenticated Claude Code session, ensuring fidelity without bypassing the official client.

Quick Start & Requirements

• Primary install/run command:
  • One-off: npx @halfwhey/claudraband "your prompt" or bunx @halfwhey/claudraband "your prompt"
  • Global install: npm install -g @halfwhey/claudraband
• Prerequisites: Node.js or Bun runtime, an already authenticated Claude Code instance, and tmux (for the default backend).
• Links: CLI Docs, Library Docs, Daemon API Docs, Examples.

Highlighted Details

• Enables resumable, non-interactive workflows via session management (cband prompt --session <session-id>).
• Provides an HTTP daemon (cband serve) for remote or headless session control.
• Integrates with editors and other frontends using an ACP server (cband acp).
• Includes a TypeScript library for programmatic workflow construction.
• Supports advanced features like self-interrogation of past Claude sessions.

Maintenance & Community

The project is marked as "Experimental" and is subject to ongoing evolution alongside Claude Code and ACP client changes. No specific community channels (e.g., Discord, Slack) or notable contributors/sponsorships are detailed in the provided README.

Licensing & Compatibility

The license type and any compatibility notes for commercial use or closed-source linking are not specified in the provided README text.

Limitations & Caveats

This project is experimental and may undergo significant changes. It is not a replacement for the official Claude SDK and requires an authenticated Claude Code TUI session, not bypassing its interactions or handling OAuth. The xterm.js backend is experimental and generally slower than the default tmux integration.