bailout.
72 SECONDS · GET YOUR AGENT BACK

Get your agent back.
Then delete the harness.

OpenCode won’t start after a config edit. The agent you’d normally ask for help is the thing that needs fixing.

A deliberately broken example config, repaired by the real public Bailout service in an Ubuntu ARM64 container. Original session: 4 min 48 sec. Waits shortened; terminal output unchanged. Silent video. No account or API key is added. Original terminal capture with full timing ↗
Try it on your machine Download video

What happens in the recording

  1. Your usual agent is broken. OpenCode exits with a configuration error before it can answer.
  2. Get a working agent. Run curl -fsSL https://bailout.dev/install.sh | bash, then bailout. No account or local model key.
  3. Ask for a repair. Give Bailout the startup error and ask it to back up and repair the config while keeping the other settings. Bailout diagnoses and repairs the invalid permission setting.
  4. Get back to your agent. Run bailout uninstall. OpenCode now answers through its free Big Pickle model.

One successful session, not a reliability benchmark. Model responses, speed, and free capacity vary. Independent checks also verified the config backup, preservation of the other settings and project file, and OpenCode’s response after uninstall.

Reproduce the example from source ↗ · Previous fresh-machine setup demo ↗

Read the setup & recovery guide ↗