i made bailout for a pretty specific problem. you boot a fresh vm and want an agent to help get it set up, except you dont have your agent set up yet. no gh, no config, no api key handy. might not even have codex / claude code / opencode curled and loaded. or you already have a setup but opencode / pi / whatever stopped launching, and the thing you'd normally ask to fix it is the thing that's broken.

for me, and this is embarrassing, but at work we switched from per-dev keys to oai / ant to just an internal litellm router, which required configuring opencode. i use opencode2 which can dynamically reload its config. well, while rewriting the config to work with self hosted litellm, it broke, and i was stranded w/ no coding agent. bailout is for that sort of thing, like break glass, agent pls fix.

think of bailout like a spare agent for these sorts of things. install it, ask it to set up the machine or fix your usual tools, then remove it. the idea is “the harness meant to be deleted.” i like having a tool whose last useful action can be uninstalling itself. plus a play on hinge, the whole app meant to be deleted.

you install it with `curl -fsSL https://bailout.dev/install.sh | bash` and run `bailout`. no account or api key needed for bailout. the tools it helps you set up still need your own accounts, obviously. it can hand you the terminal for those logins without sending what you type to the model.

the client is a rust binary, about 639 KB uncompressed on apple silicon. it also runs on linux x64 and arm64. bash is the only tool. it can inspect files, edit configs, install things, curl stuff, etc. commands run automatically with your user's permissions, so it has the same access you do in that shell. i got inspired by vercel's fx.sh in terms of minimalism and size and all that.

the hosted router uses free models and switches between available ones when a request fails. there are shared limits, and it will tell you when it has to wait. this is still a small free service, so i dont want to pretend it has unlimited capacity. odds are, if this post gets enough attention and enough of you try it, it will exhaust capacity. to that end if anyone knows anyone willing to toss a free model in for this consistently, would be very cool.

there's a recording of it fixing an intentionally broken opencode config on the gh page. bailout gets removed at the end and opencode runs again. waits are shortened in the video; the original terminal capture is there too. mit licensed, and built with a lot of help from codex. curious whether this is useful for the way you set up machines, or if there's some obvious case i'm missing. issues / prs welcome.

Comments URL: https://news.ycombinator.com/item?id=49778390

Points: 3

# Comments: 3

i built beehive for myself mostly. it has gotten to the point where my work consists in supervising oc or cc labor at tasks for multiple issues in parallel. my set up used to be zellij with a couple tabs, each tab working in a separate dir and it was a pain to manage all that. i know i could use git worktrees but they're kind of complicated, if you don't know how to use them it is easy to mess up, and i just prefer letting agents run in separate dirs with their own .git and not risk it. while i like zellij and use it inside beehive, i dont like the tabs and i forget where i am half the time.

beehive is a way for me to abstract that away. the heuristic is simple - hives are repos, so you basically have a bunch of hives which correspond to repos you work out of. each hive can have many combs. a comb is a dir with the copy of the repo you're working on. fully isolated, standalone, no shared .git. so for work or for personal stuff, i usually set up the hive, and then have a bunch of combs that i jump between supervising the agents do their thing. if you have a big repo it takes a minute to clone, and you also need gh and git because i like the niceties of like checking if the repo is there at all and stuff like that.

the app is open source, mit license. i went with tauri because i hate electron. also i have friends and coworkers who updated to macos 26 and i dont know if the whole mem leak thing for electron apps has been fixed. the app is like 9 megs which is nice too. most of it is written with cc, but i guided the aesthetics and the approach. works on mac and there is a dmg signed and notarized (i reactivated my apple dev credentials).

sharing this to get a vibe check on the idea, also maybe this is useful for you. there are many arguments, reasonable ones, you can make for worktrees vs dirs. i just know that trees are too big brain for me, and i like simple things. if you like it, pls lmk and also if you want to help (like add linux support, or like add themes, other cool things) please make a pr / open an issue.

Comments URL: https://news.ycombinator.com/item?id=47135425

Points: 47

# Comments: 22