Bug Reproduction

"It works on my machine." Clone the repo at the exact commit, reproduce the bug on a fresh server, iterate on a fix with zero environmental noise.

Workflow

# Forge a clean server with the repo
gibil create --name repro --repo github.com/you/project --ttl 60

# Checkout the exact commit from the bug report
gibil run repro "cd /root/project && git checkout abc123def" --json

# Reproduce
gibil run repro "cd /root/project && pnpm install && pnpm test:failing" --json
# → {"exit_code": 1, "stdout": "TypeError: Cannot read properties of undefined..."}

# Fix and verify
gibil run repro "cd /root/project && pnpm test:failing" --json
# → {"exit_code": 0}

gibil destroy repro

Or SSH in for interactive debugging:

gibil ssh repro
# root@repro:~# cd /root/project && node --inspect src/broken.js

Why gibil

• Guaranteed clean state — no leftover node_modules from a previous branch, no stale configs
• Exact reproduction — clone at the exact commit, install fresh deps, run the failing test
• Two modes — gibil run for scripted reproduction, gibil ssh for interactive debugging
• Auto-cleanup — TTL burns the server even if you forget

Agent workflow

An agent receives a bug report, forges a server, reproduces the issue, iterates on a fix using the code-test loop, then pushes the fix. The entire cycle happens on an isolated server — the agent never touches the developer's local environment.

gibil create --name bug-123 --repo github.com/you/project --ttl 60
# Agent: checkout commit → reproduce → fix → test → push
gibil destroy bug-123

Next steps

• Agent Code-Test Loop — the iteration pattern for fixing bugs
• Debugging Guide — SSH debugging techniques
• CLI: gibil ssh — interactive shell access