I built okiro because AI coding tools mostly felt like one-shots. They write directly to your files, and you either have to rollback or push forward. You don't really get to explore multiple ideas in parallel like you would if you were generating an image with AI.
okiro creates instant, zero-cost clones of your codebase so you can try several AI-driven approaches at once.
It uses filesystem copy-on-write (APFS on macOS, btrfs on Linux), so you can spin up dozens of variants of a large repo without actually duplicating it on disk. The copies only diverge when files change.
Example:
okiro 3 --prompt "add authentication"
# var-1: use Better Auth
# var-2: use Clerk
# var-3: roll your own with JWT
Each variant gets its own directory and an AGENTS.md with specific guidance. Open them side-by-side, let your AI tool work, then diff and keep the best result.
Would appreciate your feedback!
0 comments
—
Show HN: Okiro – spin up ephemeral codebases for parallel AI coding · HackerTrans
okiro creates instant, zero-cost clones of your codebase so you can try several AI-driven approaches at once.
It uses filesystem copy-on-write (APFS on macOS, btrfs on Linux), so you can spin up dozens of variants of a large repo without actually duplicating it on disk. The copies only diverge when files change.
Example:
okiro 3 --prompt "add authentication" # var-1: use Better Auth # var-2: use Clerk # var-3: roll your own with JWT
Each variant gets its own directory and an AGENTS.md with specific guidance. Open them side-by-side, let your AI tool work, then diff and keep the best result.
Would appreciate your feedback!