Two agents on one repo, no collisions 🌿
In AGRO, ask your agent:
"Create a worktree in <owner>/<repo> for issue #123."
Each parallel agent gets its own branch and worktree. Shared Git history, separate files, so no agent overwrites another's work.
github.com/mifunedev/agro
If it works,
if it's performant,
if it has no bugs,
if you understand how it works,
if the agent can modify it a month from now, to your liking,
is it slop?
So many people say security and ai privacy at a corporate/consumer level meanwhile the leave the Gmail, Zoom, etc backdoors no concern lol
Most of security is a psychology/sentiment than facts of a threat model for consumers
Already use devcontainer.json? Where AGRO fits 🧩
Dev Containers is strong for a full dev environment from a devcontainer.json, local or remote.
From the AGRO side: a Docker sandbox for Claude Code, Codex, or Pi. VS Code attaches to it.
github.com/mifunedev/agro
Takes a lot of iterations to figure out what that 20% that is still valuable is without sludging through 80% of slop it took to create opinions about what should remain.
Can your agents keep working after you close the laptop? 🌙
Run the AGRO sandbox on a remote server and start agents in Herdr:
agro tool install herdr
herdr
Detach with Ctrl-b q. Run herdr again to reattach while the container keeps running.
github.com/mifunedev/agro
It turns out that redacting PII from every model request your agent makes isn’t enough to hide it from the model. I ran a simple experiment in @nvidia OpenShell to demonstrate why.
nvidia.github.io/OpenShell-R…
Let an agent run on its own, off your own machine 🛡️
AGRO runs it in a Docker sandbox as a non-root user. The Docker socket is off by default.
Hooks block secret dumps, rm -rf, and git push --force.
agro sandbox install docker
github.com/mifunedev/agro
Thanks for taking AGRO for a spin in Codespaces 🙏
The Codespaces quickstart is in the README, next to the setup for your laptop or a remote VM: github.com/mifunedev/agro
Already on GitHub Codespaces? Where AGRO fits 🧭
Codespaces is strong for a cloud dev environment you open from any branch in a browser or VS Code.
From the AGRO side: a Docker sandbox on your laptop or a VM you choose, with Claude Code, Codex, or Pi.
github.com/mifunedev/agro
Pay for Claude Code and Codex? You don't need a setup for each. 🧰
One AGRO sandbox holds both, with shared agent procedures:
agro harness install claude-code
agro harness install codex
Launch either from a Herdr pane. Switch at any time.
github.com/mifunedev/agro
AGRO v0.16.0: upgrade a workspace to a pinned release and keep its home data 🔁
agro sandbox upgrade <name> --version X.Y.Z
If an upgrade of an unpinned sandbox fails, AGRO restores the running image.
Your harness and your work stay put.
github.com/mifunedev/agro
the average american does not want to get more work done
they want to have less stuff to do
politics and economy are ultimately at the whims of the average american
Move a sandbox to a new AGRO release without losing your work 🔄
agro sandbox upgrade <name> --version X.Y.Z recreates one sandbox on the official release image you pick. It keeps the home mount, named volumes, checkout, and .env.
Run it on the host.
github.com/mifunedev/agro/pu…