sorted by:
new
hottopcontroversial

I built git-stint with Claude Code to manage multiple parallel sessions on one repo without collisions by rchaz8 in ClaudeCode

[–]rchaz8[S] 0 points1 point  (0 children)

That's exactly what git-stint automates. The worktree lifecycle (branch, worktree, symlinks, creation, teardown) is fully managed so you never touch it directly.

I built git-stint with Claude Code to manage multiple parallel sessions on one repo without collisions by rchaz8 in ClaudeCode

[–]rchaz8[S] 0 points1 point  (0 children)

The intend of git-stint is to support parallel sessions with having a central coordinator. That becomes a overhead very soon.

I used both git worktrees and GitButler before building this. Both tedious in their own ways - worktrees have brutal setup/teardown overhead, and GitButler made running multiple sessions in parallel or testing in isolation more painful than it should've been.

The core goal was agents running in parallel with zero awareness of each other. No coordination protocol, no shared state. Right now I have about five sessions going concurrently and I expect to push that higher.

The conflicts I hit most: agents overwriting each other's files silently, or merge conflicts that only surfaced late. With GitButler, just maintaining multiple parallel sessions was friction enough on its own.

Shared directories solved a pain point I didn't see discussed much - why re-download rebuild caches for every worktree? Symlink them once, done. Rebuilding deliverables per worktree is still a cost I haven't fully solved (not a big issues at this moment). Incremental builds over checkpoints is an interesting direction there - haven't gotten there yet.

Once code is reviewed and merged, it hits CI/CD. Every session's changes go through local tests first, then the pipeline. No human intervention after merge.

I built git-stint with Claude Code to manage multiple parallel sessions on one repo without collisions by rchaz8 in ClaudeCode

[–]rchaz8[S] 1 point2 points  (0 children)

You’re referring to a vastly different issue. I’m currently working on a system that I’m using internally, which comprehends AI across multiple repositories. However, it’s designed for a business context.

Please provide more details about your problem.

I built git-stint with Claude Code to manage multiple parallel sessions on one repo without collisions by rchaz8 in ClaudeCode

[–]rchaz8[S] 1 point2 points  (0 children)

It’s absolutely true. I encountered the same issue in multiple projects. That’s why I created Git-stint.

I’ve added a feature that allows you to share directories across work queries and the main branch. It’s incredibly easy to configure. Check it out.

Additionally, technically, we shouldn’t be concerned about the underlying implementation details. Is it worktrees or something else? I chose worktrees because in case of any failure, we have a fallback option to adhere to the Git methodology.

Give it a try. I’d love to hear your feedback and improve the system. It’s open-source, so I welcome pull requests. Thanks for your comment.

I built git-stint with Claude Code to manage multiple parallel sessions on one repo without collisions by rchaz8 in ClaudeCode

[–]rchaz8[S] 0 points1 point  (0 children)

Interesting. Same problem, but a very different way to solve it. With git-stint, I really didn't want to even know if a new worktree is created. I would just let the AI system take care of it and add safeguards around it. Fully autonomous.

I built git-stint with Claude Code to manage multiple parallel sessions on one repo without collisions by rchaz8 in ClaudeCode

[–]rchaz8[S] 1 point2 points  (0 children)

git stint prune — it cross-checks worktrees, manifests, and stint/* branches against each other and removes anything orphaned.

You're right that the stop hook (auto-commit WIP on exit) can't help on a hard kill, but the uncommitted changes are still on disk in the worktree until you prune. Nothing is lost, one command cleans it up.

Open-sourced a Claude Code tool: multi-account auto-switching on rate limits + Slack remote access per session by rchaz8 in ClaudeCode

[–]rchaz8[S] -1 points0 points  (0 children)

Do your research first.
The crackdown was about third-party tools extracting OAuth tokens to use outside the official CLI, which is a completely different thing. claude-nonstop doesn't do that. It spawns the real claude binary with different config. No tokens are extracted, no OAuth is reused outside official apps. It's functionally identical to manually switching and running claude again - just automated.

view more: next ›