131–136 of 136 posts
this is going in the opposite direction. we need to be sandboxing agents, not giving them a bigger surface area to fuck up your repo.
Hi, have been working on that also ;) as a way to have multiple agents working on the same repo. Started with Docker and then switched, because Docker is to slow to spin up (seconds is to slow) and big.
Earlier quoted context omitted.
git has worktrees for this, I use them all the time
I don't see the correlation. Jujutsu has workspaces as the match to git's worktrees too because their worktrees are a different thing from what I'm talking about. Switching worktrees and making commits is way more work than just making commits.
Earlier quoted context omitted.
Except it likes to put itself as the co-author in every commit message. Even asking it repeatedly and putting not to do so in Claude.md has no effect. So I have to keep deleting that manually :)
Add "includeCoAuthoredBy": "false" to your settings file: https://docs.anthropic.com/en/docs/claude-code/settings
Earlier quoted context omitted.
uhh... .gitignore solves that right?
These agents often generate randomly named files and dump them anywhere. You can end up with dozens of files added if you let it run on any problem it tries to create one-off "test / reproduction" cases. It hasn't always cleaned them up so a "git add all" approach can bring in junk, and the patterns for names aren't consistent. In fact they're often called stuff like *-test.js which looks like it could be a source OR…
This looks well-built, but have you considered using Jujutsu (jj) instead? It elegantly solves the snapshot/checkpoint problem without needing MCP servers or a separate app. With jj, every file change is automatically captured (no manual commits needed), and you can create lightweight "sandbox" revisions for each Claude Code task. When things go wrong, `jj undo` instantly reverts to any previous state. The operation…
Here's what I do to survive macos updates, random restarts, crashes etc. I had Claude Code to configure all of this: Terminal Setup: - Alacritty as your terminal - tmux as your session manager - Auto-start tmux in Alacritty configuration Key Protection: # Alacritty auto-starts tmux sessions tmux new-session -s main # Creates persistent session # tmux shortcuts (prefix: Ctrl+a) # Sessions persist even if terminal clos…
I checked out the demo and it looks great. I am guessing it supports 4 concurrent claude sessions? I cannot find this in docs