21–30 of 48 posts
Isn't "Claude Code power user" an oxymoron or am I confused?
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.
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.
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
Earlier quoted context omitted.
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 gu…
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.
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.
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.
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.
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?
Isn't "Claude Code power user" an oxymoron or am I confused?
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.