Fly Labs
Ask FlyBot

Coasts – Containerized Hosts for Agents

Hi HN - We've been working on Coasts (“containerized hosts”) to make it so you can run multiple localhost instances, and multiple docker-compose runtimes, across git worktrees on the same computer. Here’s a demo: https://www.youtube.com/watch?v=yRiySdGQZZA. There are also videos in our docs that give a good conceptual overview: https://coasts.dev/docs/learn-coasts-videos.Agents can make code changes in different worktrees in isolation, but it's hard for them to test their changes without multiple localhost runtimes that are isolated and scoped to those worktrees as well. You can do it up to a point with port hacking tricks, but it becomes impractical when you have a complex docker-compose with many services and multiple volumes.We started playing with Codex and Conductor in the beginning of this year and had to come up with a bunch of hacky workarounds to give the agents access to isolated runtimes. After bastardizing our own docker-compose setup, we came up with Coasts as a way for agents to have their own runtimes without having to change your original docker-compose.A containerized host (from now on we’ll just say “coast” for short) is a representation of your project's runtime, like a devcontainer but without the IDE stuff—it’s just focused on the runtime. You create a Coastfile at your project root and usually point to your project's docker-compose from there. When you run `coast build` next to the Coastfile you will get a build (essentially a docker image) that can be used to spin up multiple Docker-in-Docker runtimes of your project.Once you have a coast running, you can then do things like assign it to a worktree, with `coast assign dev-1 -w worktree-1`. The coast will then point at the worktree-1 root.Under the hood the host project root and any external worktree directories are Docker-bind-mounted into the container at creation time but the /workspace dir, where we run the services of the coast fr

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

69

out of 100

Verdict

VALIDATE

high confidence

Competition

11

competitors found, emerging market, funded players

Trend

No signal yet

A complex local development environment tool for AI agents leveraging git worktrees and isolated Docker runtimes, targeting a specific but crowded niche.

The pain

AI developers using git worktrees struggle with managing multiple, isolated localhost instances and complex docker-compose runtimes, leading to port conflicts, mental context destruction, and inefficient 'hacky workarounds.'

The gap

Current solutions like DevContainers, Docker Sandboxes, and VMs address parts of environment isolation but fail to seamlessly provide truly isolated, reproducible *complex docker-compose runtimes per git worktree* without modifying original project configurations or resorting to manual, painful processes.

Build angle

Coasts aims to provide 'containerized hosts' as a devcontainer-like runtime focused solely on project execution, allowing developers to create a Coastfile to spin up multiple Docker-in-Docker runtimes of their project, assignable to specific git worktrees for isolated testing.

Strengths

  • Addresses a highly specific and painful problem for AI developers.
  • Strong demand reality with clear user frustrations and hacky workarounds.
  • Market for local AI agent development is growing.
  • Unique angle of unifying git worktrees with complex isolated Docker runtimes without config changes.

Risks

  • High technical complexity for a solo builder, potentially leading to slow development or an incomplete MVP.
  • Crowded competitive landscape with funded players (Docker, Microsoft) actively developing similar solutions.
  • Difficulty in monetization given free alternatives and developer expectations for core dev tools.
  • Risk of being 'too niche' or not offering a compelling enough reason to switch from existing (albeit imperfect) workflows.

Next steps

  1. Conduct in-depth interviews with AI developers experiencing this specific pain to validate exact needs, willingness to pay, and critical 'must-have' features.
  2. Focus on a minimal viable product (MVP) that solves the absolute core pain for a specific type of AI agent or workflow, e.g., 'isolated local LLM agent testing for one worktree'.
  3. Explore open-source vs. commercial models more deeply, considering if a paid offering can sustain against free, well-supported incumbents.
  4. Investigate potential integration points with existing developer tools or platforms to reduce distribution friction.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Coasts – Containerized Hosts for Agents”.

Open FlyBot