Show HN: Claudraband – Claude Code for the Power User (github.com)
Claudraband wraps a Claude Code TUI in a controlled terminal to enable extended workflows. It uses tmux for visible controlled sessions or xterm.js for headless sessions (a little slower), but everything is mediated by an actual Claude Code TUI.
One example of a workflow I use now is having my current Claude Code interrogate older sessions for certain decisions it made: https://github.com/halfwhey/claudraband?tab=readme-ov-file#s...
This project provides:
- Resumable non-interactive workflows. Essentially `claude -p` with session support: `cband continue <session-id> 'what was the result of the research?'` - HTTP server to remotely control a Claude Code session: `cband serve --port 8123` - ACP server to use with alternative frontends such as Zed or Toad (https://github.com/batrachianai/toad): `cband acp --model haiku`. - TypeScript library so you can integrate these workflows into your own application.
This exists cause I was using `tmux send-keys` heavily in a lot of my Claude Code workflows, but I wanted to streamline it.
13 comments
[ 3.1 ms ] story [ 33.5 ms ] threadThis needs to support at least Gemini CLI, Codex and OpenCode as well, preferably by being generic as much as possible.
But they're not well designed, and some things just have to go in through the terminal interface like slash commands (i.e. `/clear`)
All it would take is implementing their own forked version of VSCode (like Cursor did) and making Claude the default choice.
Obviously I'm simplifying here, but they definitely have the capability to do it.