[HN Gopher] Show HN: Claudraband - Claude Code for the Power User
       ___________________________________________________________________
        
       Show HN: Claudraband - Claude Code for the Power User
        
       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.
        
       Author : halfwhey
       Score  : 77 points
       Date   : 2026-04-12 16:55 UTC (6 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | colobas wrote:
       | Any idea of how this interacts with Anthropic's ToS for
       | subscription-based use?
        
         | cortesoft wrote:
         | 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.
        
           | halfwhey wrote:
           | 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.
        
           | j45 wrote:
           | Nor is it flooding servers with open claw type use.
        
       | lifis wrote:
       | 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.
        
         | halfwhey wrote:
         | 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.
        
           | lifis wrote:
           | 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.
        
             | halfwhey wrote:
             | That's a good point, I'll look into tackling this soon
        
             | BoorishBears wrote:
             | Is there an example of this?
        
         | obmelvin wrote:
         | It isn't ones duty to develop for everybody. If someone makes
         | something for their own use case and shares it, that's fine.
        
           | godelski wrote:
           | 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 -\\_(tsu)_/-
           | 
           | 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
        
             | halfwhey wrote:
             | MIT License added
        
         | ay wrote:
         | 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.
        
       | mikeroySoft wrote:
       | License? I see none listed in the repo.
        
         | halfwhey wrote:
         | Fixed
        
       | beepbooptheory wrote:
       | Isn't "Claude Code power user" an oxymoron or am I confused?
        
         | sudb wrote:
         | Are you asking if it is possible to be a power user of Claude
         | Code? Because it very much is - what's the oxymoron?
        
           | ghiculescu wrote:
           | I thought Claude Code _is_ for power users. How much more
           | powerful do you need to be to use this?
        
       | dragonfax wrote:
       | 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`)
        
       ___________________________________________________________________
       (page generated 2026-04-12 23:00 UTC)