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

OmniRecall Beta: FAISS-Powered Memory Injection for Cloud LLM Chats
OmniRecall is a local mitmproxy bypass that intercepts traffic to cloud chat interfaces like DeepSeek, adding a permanent memory layer using FAISS indexing and sentence-transformers MiniLM-L6. It's currently in beta, requires CPU-only operation, and uses an aggressively restrictive source-available license.

SkyClaw: An Open Agent Runtime Written in Rust
SkyClaw is an open-source agent runtime written in Rust with 34 new features across 7 development phases. It includes task checkpointing, SQLite-backed persistent queues, parallel tool execution, and multi-tenancy support.

Vibeyard adds P2P session sharing for Claude Code
Vibeyard, an open-source IDE for Claude Code, now supports peer-to-peer session sharing. Users can share live terminal sessions with teammates over encrypted WebRTC connections with read-only or read-write access modes.

Open Source Dashboard Reveals Actual Claude Code Compute Costs
A developer reverse-engineered Claude Code's rate limit formula to build a local dashboard that shows real-time usage percentage, actual dollar costs, burn rate, peak hours, and which skills/hooks are firing. The tool revealed a $100/month plan consumed $13,286 in equivalent API compute in one month.