I built supapool.io, an ephemeral full copy of supabase's services that you can spin up in ~400 ms (Auth, postgres, storage, realtime).

so if you run multiple coding agents in parallel in different worktrees, they can now have their own copy of supabase without making changes that conflict with eachother.

> why not use supabase docker locally?

when I run 3-4 instances locally, my macbook gets hot and sometimes freezes.

> why not use supabase branches?

branches take minutes to setup, and are designed for persistence. this is expensive, and for a dev environment, it is too slow.

> why not use mocks?

mocks are bad for agents. i expect agents to test their migrations, SQL against real prod service behavior. agents hallucinate working mocks often. However, upside of mocks is that its faster and runs locally, but with supapool, the upside is less convincing.

> how does it work/how is this economically viable?

starting supabase in 400ms requires a few things: 1. a pool of ready supabase instances running warm, and colocated with region failover (us-east, us-west, europe-west, asia-southeast) 2. fast autoscaling when pool starts to shrink with microVM/firecracker 3. gutting strong persistence guarantees. dev agents don't need WAL, fsync, PITR, replication. anything for HA on a ephemeral supabase instance is bloat

its in beta right now, and i'm using our gcp credits to bankroll this, so its free. the eventual pricing will be something like $/instance second and more cost effective than branching or self hosting/maintaining a supabase cluster.

would love to get your feedback if you use supabase, and if you think there's something better that would fit your local coding agent setup. Thanks!

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

Points: 27

# Comments: 4

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

Points: 1

# Comments: 0

maybe what we're asking for is that terminal commands keep in mind that agents are now the primary users of them, and have a feeling that new packages or commands could get wider adoption if they are better understood by a coding agent

- similar to SEO for LLMs growing in adoption - documentation sites offering .md file raw for LLMs to ingest easily

These things will make it so that your packages or libs adopted faster

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

Points: 3

# Comments: 3

Howdy - I’m Kevin, co-founder of Firebender, and we built the first background coding agent in android studio / Jetbrains!

Why not just use Cursor background agents or OpenAI Codex?

Both of these require setting up a cloud container and cloning your existing developer environment, and maintaining it. Then when you want to iterate on changes as AI inevitably makes a mistake, you either throw away the work, or have to pull down the branch and clean it up. This feels really clunky. With Firebender, background agents run locally in a lightweight git worktree/IDE tab. This means when the agent is done, you can easily clean up the changes and run code with a few clicks.

Under the hood, the agent behaves similarly to claude code (didn’t want to reinvent the wheel), but also leverages all of the hooks into IntelliJ sdk like go-to-definition, find usages, auto-imports for accuracy, and it gives a cleaner visual UI for reviewing changes and merging them. You can use any frontier model like gpt-5/sonnet-4 as the base.

We’ve had to do quite a bit of reverse engineering of the IntelliJ codebase to cleanly set up and manage the isolated environment, and I think you’ll appreciate the simple UX of hitting cmd+enter to run a background agent anywhere.

get started docs: https://docs.firebender.com/get-started/background-agents

download the plugin: https://firebender.com

Would love to get your feedback to help us improve the tool for you! Thanks!

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

Points: 9

# Comments: 2

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

Points: 3

# Comments: 1

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

Points: 1

# Comments: 0

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

Points: 1

# Comments: 0

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

Points: 2

# Comments: 0

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

Points: 1

# Comments: 0

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

Points: 3

# Comments: 0

Also, if you ever want to revisit a video, just use chromes history, but you'll find also this rarely happens if ever.