Twill.ai (YC S25) – Delegate to cloud agents, get back PRs

Hey HN, we're Willy and Dan, co-founders of Twill.ai (https://twill.ai/). Twill runs coding CLIs like Claude Code and Codex in isolated cloud sandboxes. You hand it work through Slack, GitHub, Linear, our web app or CLI, and it comes back with a PR, a review, a diagnosis, or a follow-up question. It loops you in when it needs your input, so you stay in control.Demo: https://www.youtube.com/watch?v=oyfTMXVECbsBefore Twill, building with Claude Code locally, we kept hitting three walls1. Parallelization: two tasks that both touch your Docker config or the same infra files are painful to run locally at once, and manual port rebinding and separate build contexts don't scale past a couple of tasks.2. Persistence: close your laptop and the agent stops. We wanted to kick off a batch of tasks before bed and wake up to PRs.3. Trust: giving an autonomous agent full access to your local filesystem and processes is a leap, and a sandbox per task felt safer to run unattended.All three pointed to the same answer: move the agents to the cloud, give each task its own isolated environment.So we built what we wanted. The first version was pure delegation: describe a task, get back a PR. Then multiplayer, so the whole team can talk to the same agent, each in their own thread. Then memory, so "use the existing logger in lib/log.ts, never console.log" becomes a standing instruction on every future task. Then automation: crons for recurring work, event triggers for things like broken CI.This space is crowded. AI labs ship their own coding products (Claude Code, Codex), local IDEs wrap models in your editor, and a wave of startups build custom cloud agents on bespoke harnesses. We take the following path: reuse the lab-native CLIs in cloud sandboxes. Labs will keep pouring RL into their own harnesses, so they only get better over time. That way, no vendor lock-in, and you can pick a different CLI per task or combine them.When you giv

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

68

out of 100

Verdict

BUILD

high confidence

Competition

12

competitors found, emerging market, funded players

Trend

No signal yet

A cloud platform to delegate coding tasks to lab-native AI agents in sandboxes, aiming to solve parallelization, persistence, and trust issues for developers.

The pain

Developers struggle with running AI coding agents locally due to lack of parallelization, agents stopping when laptops close, and security concerns with local filesystem access. They desire persistent, parallel, and secure execution of AI tasks, receiving PRs back.

The gap

While the market has many AI coding tools and some cloud-based autonomous agents (Devin, Sweep AI), Twill's specific gap is offering a platform that *reuses* existing lab-native CLIs (like Claude Code, Codex) within isolated cloud sandboxes, allowing for multi-agent use and avoiding vendor lock-in, with an emphasis on user control to avoid AI 'looping' or noise.

Build angle

Build a cloud-based sandbox environment that can orchestrate and run various lab-native AI coding CLIs persistently and in parallel. Focus on user control, memory features, and automation for specific recurring tasks.

Strengths

  • Addresses highly specific and severe developer pain points (parallelization, persistence, trust).
  • Large and rapidly growing market for AI coding assistants.
  • Clear willingness to pay evidenced by competitor pricing.
  • Specific technical angle ('reuse lab-native CLIs in cloud sandboxes') that could offer flexibility.
  • Founder-market fit, as the creators built it for their own pain.

Risks

  • Extremely crowded market with well-funded competitors (Devin, Sweep AI) offering similar 'cloud agent' functionality.
  • High technical complexity for a solo builder to create a robust and scalable sandboxing/orchestration platform.
  • Need to prove that developers strongly value Twill's specific 'reuse lab-native CLIs' approach over integrated solutions.
  • Potential for AI labs to integrate similar cloud orchestration directly into their offerings, eroding Twill's niche.

Next steps

  1. Conduct in-depth interviews with developers currently using local AI coding agents or competing cloud agents to understand if Twill's specific 'reuse lab-native CLIs' and 'user control' differentiators are highly valued.
  2. Validate pricing model and whether the proposed value overcomes switching costs from existing solutions (both local setups and cloud competitors).
  3. Focus MVP on the most critical pain point (e.g., persistent execution of a single popular LLM CLI for specific tasks) to accelerate market feedback and minimize initial build complexity.
  4. Explore partnerships or integrations with specific AI labs to ensure compatibility and ease of use for their CLIs.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Twill.ai (YC S25) – Delegate to cloud agents, get back PRs”.

Open FlyBot