
Why teams use Twill
- PRs come with proof. Twill doesn’t just produce a diff. It runs your build, tests, and lint, starts your app, clicks through UI changes in a browser, and attaches the evidence — test output, screenshots, recordings — to the pull request.
- It runs your whole stack. Every task runs in a dev environment with your repos cloned, dependencies installed, databases seeded, and dev servers already running. Multi-repo and monorepo setups work out of the box.
- It works where your team works. Trigger tasks from GitHub issues, Slack mentions, Linear labels, Notion comments, or Asana — and iterate in the same thread. No context re-explaining.
- You stay in control. Nothing merges automatically. Every change arrives as a pull request for human review, built in an isolated sandbox — agents can’t push to your default branch or touch your infrastructure.
How it works
- You describe the change. From any connected tool, the CLI, the API, or the web app.
- Twill asks or plans when needed. Ambiguous tasks get clarifying questions; you can also require a reviewable plan before any code is written.
- An agent implements it in a fork of your workspace’s dev environment, using the coding agent and model you choose (Claude Code, Codex, or OpenCode).
- Twill verifies the change — build, tests, lint, plus runtime checks against the running app.
- You review a PR with a summary and proof-of-work artifacts.
Start here
Quickstart
Connect GitHub and get your first verified PR in minutes.
What to delegate
The tasks Twill handles best, with example prompts.
Work from your tools
Trigger tasks from GitHub, Slack, Linear, Notion, and more.
Use with your local agent
Delegate to Twill from Claude Code or Cursor.