Are you still using outdated GitHub Oauth apps for this, or have you swapped to GitHub Apps? GitHub Apps are newer and have Oauth flows, but have a fine-grained permissions model instead of the Oauth permission model.
More-over, can you document the GitHub permissions needed and which GitHub App(s) this tool uses? Are you using device-flow, online oauth-flow, etc? And where are the Oauth tokens stored if so? Is there any server-side component where you might be storing tokens?
Who does your design? I absolutely love this aesthetic, both this product, and your site (chorus.sh). What is this even called? I went for a similar vibe with tinylogger.com, but def didn't have your skills to pull it off.
I have been imagining something like this would be perfect for working with Claude Code. I tried a couple other apps but they seemed to change too much without providing enough value for that change. This feels like just a nice clean simple extension of how Claude code already works that solves my most common pain points in the workflow.
Cool idea, and I'm definitely not in the target market (I'm a Linux user and also very hesitant to adopt proprietary tools to my important workflows), but something like this could be useful. Right now though it's pretty easy to run each in a different tmux window and check on it, but once I have about 3 or more running at a time it's very easy to forget about one and have it paused waiting for confirmation. A tool like this to add a dashboard of sorts would be nice. Definitely interesting to think about!
I noticed that I found Claude great for squashing bugs/issues, and started using worktrees but saw similar problems as you described, so I enlisted Claude and wrote https://github.com/Someblueman/hydra to solve for this very issue, keeping (or rather trying) it in pure shell for personal portability and gives me a playground for AI driven development
I was really excited to try this but this does NOT work the way I expected. I wanted a simple git worktree manager for my existing, already-checked-out repository. Instead, it requests Github permissions and clones the repo from Github. This is bad, because you need to run all the dependency installs, etc. for every workspace before being able to test anything. In other words it's like Codex or Cursor Background Agents, except worse, because it's on your machine. The reason I don't use Codex or Background Agents is because my project has way too many dependencies and would take way too long (and too complicated) to install everything required to have an isolated running instance, plus there would be DNS conflicts, external API conflicts, among other issues.
What I do want is simple git worktree management for an already-checked-out repo on my machine, no Github permissions or dependency re-installation (copying node_modules, etc.).
I'm the only user at the moment, and I really enjoy the workflow. I run about four claude-codes at once this way. It's a little underbaked but I think this is the way a lot of people are going to go. Seems like the 'par' tool in a sibling comment is a similar approach.
Containers do make things easier, especially since agents can see the log output of any service super easily. To do the same thing outside a container you need to send logs somewhere the agent can see.
Also the working on PRs workflow seems broken - the local branch doesn't have the changes that are on the PR so I can't pick it up and continue working on it.
Full read-write access required to all your Github account's repos. Not just code. Settings, deploy keys. The works. Full access to your organisation settings. Not a privacy policy in sight. Zero disclosure of data practices.
You are INSANE to authorize this app on anything other than throwaway code.
- I switch in between planning and execution in the middle of the conversation using Terminal a lot, it would be nice to have it here as well rather than defining how I want Claude to think in advance.
- Entering messages when the agents can result in task lists to save time.
I’m also experimenting different UX with CC, here is Claude Code running in Slack if anybody is interested. https://peerbot.ai
So this is why Claude Code is so slow now. I am all for these but not at the cost of other more casual users. I never had to worry about Sonnet use but even that is not guaranteed. Forget Opus.
This is very useful! I think the interfaces around models being used in an async manner will look very different than the synchronous chat UIs we are today. Claude Code is the first real “agent” that is providing true economic value, and there’s so much low hanging fruit in making the interfaces far better.
I'm in the midst of modernizing a 1994 K&R C 32-bit codebase to 64-bit C23, as a museum piece: the computer algebra system Macaulay that I coauthored, since replaced by Macaulay 2.
The horror!
On macOS my environment is Sublime Text as editor, iTerm as terminal. I open two full screen iTerm windows of four panes each, start Claude Code Opus 4 and type "just task" in each pane. CLAUDE.md tells the session to run this justfile command and follow the directions, which generally include instructions to continue by doing "just task" again. Each session may edit its <file>.c and <file>.h but not shared headers; if it has a problem with this I touch STOP in the task directory, the other sessions eventually are told to wait, and then the trouble child session can edit what it wants.
I'm sure in a few years AI will read and fix my 57 C file code base all at once, but for now this workflow has proved invaluable.
The irony? This is the dumbest parallel task manager imaginable yet it works. And our code base has a similar feel: The storage management is a set of fixed sized stacks that outperformed malloc() by 4x back in the day. Etc. Etc.
I learned this gift from my Dad. He devised the Bayer filter for digital photography back in 1974, it looks like ten minutes work (it wasn't) but we're still using it.
50 comments
[ 8.9 ms ] story [ 122 ms ] thread- It'd be great to change the default branch used for creating new workspaces.
- I'd like the ability to add custom tools to the "Open in..." menu.
But no way to find out if there’s any data sent to your servers etc, unless I’m missing some links?
Or, skip the integration and use your local GitHub CLI auth.
More info: https://docs.github.com/en/apps/oauth-apps/building-oauth-ap...
More-over, can you document the GitHub permissions needed and which GitHub App(s) this tool uses? Are you using device-flow, online oauth-flow, etc? And where are the Oauth tokens stored if so? Is there any server-side component where you might be storing tokens?
Thanks!
Anyways, excellent work!
What I do want is simple git worktree management for an already-checked-out repo on my machine, no Github permissions or dependency re-installation (copying node_modules, etc.).
I'm the only user at the moment, and I really enjoy the workflow. I run about four claude-codes at once this way. It's a little underbaked but I think this is the way a lot of people are going to go. Seems like the 'par' tool in a sibling comment is a similar approach.
Containers do make things easier, especially since agents can see the log output of any service super easily. To do the same thing outside a container you need to send logs somewhere the agent can see.
Agreed that worktrees seem clearly better.
You are INSANE to authorize this app on anything other than throwaway code.
@charlieholtz care to comment?
- I switch in between planning and execution in the middle of the conversation using Terminal a lot, it would be nice to have it here as well rather than defining how I want Claude to think in advance.
- Entering messages when the agents can result in task lists to save time.
I’m also experimenting different UX with CC, here is Claude Code running in Slack if anybody is interested. https://peerbot.ai
https://github.com/stravu/crystal
Sadly, this is lost with conductor.
I just don’t feel as joyful using it.
The horror!
On macOS my environment is Sublime Text as editor, iTerm as terminal. I open two full screen iTerm windows of four panes each, start Claude Code Opus 4 and type "just task" in each pane. CLAUDE.md tells the session to run this justfile command and follow the directions, which generally include instructions to continue by doing "just task" again. Each session may edit its <file>.c and <file>.h but not shared headers; if it has a problem with this I touch STOP in the task directory, the other sessions eventually are told to wait, and then the trouble child session can edit what it wants.
I'm sure in a few years AI will read and fix my 57 C file code base all at once, but for now this workflow has proved invaluable.
The irony? This is the dumbest parallel task manager imaginable yet it works. And our code base has a similar feel: The storage management is a set of fixed sized stacks that outperformed malloc() by 4x back in the day. Etc. Etc.
I learned this gift from my Dad. He devised the Bayer filter for digital photography back in 1974, it looks like ten minutes work (it wasn't) but we're still using it.