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
Agree on the source-available clarification — this exact distinction matters on HN and I learned it the hard way recently.
I just went through the licensing decision for my own project and landed on BSL 1.1 with a 4-year conversion to Apache 2.0. Framing it as "source-available, auto-converts to Apache 2.0 in 2030" reads as transparent intent rather than "fake open source."
That said, BSL/FSL really only make sense if you plan to monetize a hosted version yourself. For wrapper tools like Claudraband that sit on top of an existing product ecosystem, MIT or Apache 2.0 might fit better — you're not protecting a competing SaaS, you're just sharing code.
MIT License added
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.
> they might apply different rate limits or policies if they notice ACP use
Is there any evidence that supports this claim?
That's a good point, I'll look into tackling this soon
Is there an example of this?
Can't you just tell your AI tool of choice to just port it? One thing I like about AI is that now I can easily roll my own or take an open-source project and customize it really fast with very little commitment on my end. Instead of everyone having to use the exact same tools, now we can customize it to our liking--at least for now
https://github.com/ehrlich-b/wingthing - Here's my version of this idea which is agent agnostic. Not exactly the same idea, "sandbox'ed persistent agent", in my case available over the web with xterm.js (though you can also just run locally).
Opencode already supports continuing old sessions with ctrl-x, l.
I’ve made something very similar that is almost backend-agnostic: https://github.com/ayourtch-llm/tttt - and it does auto inject the MCP in case of Claude, but it is trivial to adapt to other backends.
This is really cool.
I did something similar with gemini cli by just wrapping it in tmux and building some extensions.[0]
Eventually that wasnt enough so I ended up forking it and adding REST endpoints to inject commands and read the screen.[1]
Your solution is much cleaner! I'll probably replace mine with it. Thanks for sharing!
[0] https://github.com/stevenAthompson/self-command
[1] https://github.com/stevenAthompson/gemini-cli-remote-control
If xterm.js is slower than tmux, why don't you just use tmux for the headless sessions as well? How is tmux not headless enough?
Not everyone has tmux. I default to tmux if you have it and fallback to xterm.js
Any idea of how this interacts with Anthropic's ToS for subscription-based use?
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.
Using Claude Channels can make it easy to inject prompts and get just the response back without having to identify it in the terminal output or fight with the TUI.
But they're not well designed, and some things just have to go in through the terminal interface like slash commands (i.e. `/clear`)
License? I see none listed in the repo.
Fixed
Isn't "Claude Code power user" an oxymoron or am I confused?
Are you asking if it is possible to be a power user of Claude Code? Because it very much is - what's the oxymoron?
I thought Claude Code _is_ for power users. How much more powerful do you need to be to use this?
Some people open a claude code session and just talk with it. And some use hooks, custom commands, agent-teams..and so on. You can definitely be a power user. But I’m sure whether that translates to actual “power” is up for debate.
I would simply ask the claude code to use the hooks and custom commands and agent teams for me.
[dead]