Claudraband: Terminal Wrapper for Persistent Claude Code Sessions

What Claudraband Does
Claudraband is a wrapper for the official Claude Code TUI that runs it in a controlled terminal environment. This allows developers to maintain persistent Claude Code sessions, resume them later, answer pending prompts, expose sessions through a daemon, or drive them through the Anthropic Client Protocol (ACP).
Key Features and Commands
The tool provides several specific capabilities:
- Resumable non-interactive workflows: Essentially
claude -pwith session support. Example:cband continue <session-id> 'what was the result of the research?' - HTTP daemon for remote or headless session control: Start with
cband serve --host 127.0.0.1 --port 7842, then connect withcband --connect localhost:7842 "start a migration plan" - ACP server for editor and alternate frontend integration: Run
cband acp --model opusorcband acp --model haikuto enable integration with tools like Toad or Zed - TypeScript library for building these workflows into custom tools
- Session management:
cband sessionslists live tracked sessions,cband sessions close --allcloses all controlled sessions
Setup and Requirements
Requirements include Node.js or Bun, an already authenticated Claude Code installation, and tmux for first-class local and daemon-backed workflows. Installation options:
# one-off use
npx @halfwhey/claudraband "review the staged diff"
install globally
npm install -g @halfwhey/claudraband
The package installs both claudraband and cband (recommended shorthand). It bundles Claude Code @anthropic-ai/[email protected] but allows overriding with CLAUDRABAND_CLAUDE_PATH environment variable.
Workflow Examples
The source shows several practical use cases:
- Local persistent sessions:
cband "audit the last commit and tell me what looks risky" - Self-interrogation: Claude can interrogate an older Claude session and justify the choices it made
- Alternative frontends: Toad or Zed can use
claudraband acpas an alternative frontend for Claude Code - Library integration: TypeScript examples include code review, multi-session management, and session journaling
Technical Details
Sessions are tracked in ~/.claudraband/. The daemon defaults to using tmux as the terminal runtime. An experimental --backend xterm option exists for headless fallback but is slower than tmux. The project is marked as experimental and evolving as Claude Code and ACP clients change.
Important caveat: This is not a replacement for the Claude SDK and is geared toward personal, ad-hoc usage. It doesn't handle OAuth or bypass the Claude Code TUI - every interaction runs through a real Claude Code session.
📖 Read the full source: HN AI Agents
👀 See Also

2-Prompt System to Carry Context Between Claude Chats Without Token Waste
A developer shares two prompts for compressing an entire Claude conversation into a structured context block and loading it into a fresh chat, preserving decisions, work, and next steps.

OpenSwarm: Multi-Agent Claude CLI Orchestrator for Linear and GitHub
OpenSwarm orchestrates multiple Claude Code CLI instances as autonomous agents that pull Linear issues and run Worker/Reviewer/Test/Documenter pipelines. It uses LanceDB with multilingual-e5 embeddings for memory and includes Discord bot control, PR auto-improvement, and a web dashboard.

Comparing OpenClaw and Claude Cowork: Local Automation vs Sandboxed Workflows
OpenClaw is an always-on local agent that runs on your machine with shell command execution and browser automation, while Claude Cowork operates within Claude Desktop in a sandboxed environment focused on document and browser tasks.

Codeflash Analysis: 118 Performance Bugs Found in Two PRs Written with Claude Code
Codeflash measured performance of two major features built with Claude Code and found 118 functions running up to 446x slower than necessary. The analysis revealed patterns of inefficient algorithms, redundant computation, missing caching, and suboptimal data structures.