Show HN: Claudraband – Claude Code for the Power User
61 points - today at 4:55 PM
Hello everyone.
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.
That's cool but by only supporting Claude Code you are contributing to the Anthropic lock-in problem.
This needs to support at least Gemini CLI, Codex and OpenCode as well, preferably by being generic as much as possible.
It isn't ones duty to develop for everybody. If someone makes something for their own use case and shares it, that's fine.
And that's the beauty of open source and code. You can share it freely and easily. There's no thing that can be made for everyone.
Maybe some irony is everyone tells me they "just care that it works". Yet it can work and you'll always have the comments like above because it works for the reason it was made but not for things it wasn't made for. But it's open, so modify the code and put in what you want ¯\_(ツ)_/¯
I guess I should clarify its source available, not "Open Source". There's no license on the project so it's default theirs. But no harm if you're just editing it yourself. @OP should put up some license to let others know how what is allowed and what isn't
Codex and Gemini have ACP servers already:
https://github.com/zed-industries/codex-acp
https://geminicli.com/docs/cli/acp-mode/
In fact Codex, in OpenAI fashion, have their own protocol as well:
https://developers.openai.com/codex/app-server
Opencode too. These tools are already so programmable and embeddable, it's just Claude Code is a sticking point. But maybe it would be useful to provide a unified CLI and Daemon for all of them.
They have ACP servers but they might apply different rate limits or policies if they notice ACP use, while a solution like yours would not trigger that unless it becomes popular enough to specifically detect. It also seems this provides more features them just an ACP server.
That's a good point, I'll look into tackling this soon
Any idea of how this interacts with Anthropic's ToS for subscription-based use?
cortesoft
today at 7:39 PM
It looks like it shouldn’t be an issue… it is just a wrapper around CLI calls to the official Claude code. It would be indistinguishable from the Anthropic side, and it isn’t even doing anything hacky or impersonating the official client.
This is my interpretation as well, Anthropic wants to be in full control of the connection between the client and their servers, and that's compatible with what
I'm trying to do.
Nor is it flooding servers with open claw type use.
mikeroySoft
today at 8:12 PM
License? I see none listed in the repo.
mr_johnson123
today at 8:44 PM
[dead]