A few people asked how I run multiple AI coding agents in parallel. Two things unlock parallel use:
1. Run agents inside a sandbox - so they can safely bypass permission prompts and run unattended for 30+ minutes.
2. Use version control that continuously snapshots file changes - so progress for every agent shows up in one tree.
With these in place, I keep 3-5 going at once. When changes conflict, agents can resolve those too.
~5 min. Tools: Claude Code, macOS sandbox-exec, Jujutsu, VisualJJ.
If you haven't watched @karpathy's recent talk "Software Is Changing (Again)" yet - add it to your queue. He lays out a pragmatic view of where AI (and "agents") are headed.
One point he makes: the feedback loop between AI (generation) and humans (verification) has to get *way* faster. That's exactly the problem I'm tackling. Version control is the key element of that loop - and today's tools are nowhere near quick enough.
Are you using Cursor, Windsurf, or another vibe-coding setup? Does Git feel too slow or overcomplicated? DM me for beta access to @branching_app - version control built for AI-first coding.
https://t.co/IKMuEZkmJ0
#AIEngineering #VibeCoding #VersionControl
Fed up with Git version control headaches, I built Branching App to fix it.
Version control reimagined for vibe coding - continuous backups, real-time AI sync, conflict-free auto-merges. Fully GitHub compatible.
DM me or sign up for early access: https://t.co/0X3GJL1Q2x
Git is powerful, but let’s be honest: it's a headache. Branching, rebasing, conflicts. So I built Branching App to fix that.
Designed for vibe coding, it won't kill your vibe when using AI to code. It offers continuous backups, real-time sync, & conflict-free merges - all GitHub-compatible.
Early access is open! Send me a DM or sign up here: https://t.co/HdnpFC2rBu
Someone needs to build the GitHub of vibe coding.
e.g. Let (normal) people collaborate on a site or app with easy forking, pull requests, rollbacks, and feedback on prompts along the way etc.
vibe coder: how do I save this version?
these guys: ok first git init && git remote add origin, create a feature branch, git add ., git commit -m 'feat: initial commit', push to create a PR, then later when you hit conflicts just git rebase -i HEAD~3, stash pop, resolve the...