Choose a destination. Code as a pull request, a merge request or files on your Mac. Or a plan in an issue, Linear, Notion or Markdown.
Handoff
Hand a design to engineering.
Send a design to Linear, Notion or GitHub as a plan, or have an agent open a pull request with the code.
How it works
From design to pull request.
The agent reads your repository before it writes. The code uses your components and passes your own checks, so it isn't rebuilt from a ticket.
- 01
Choose a destination.
Pull request, GitLab merge request, GitHub issue, Linear issue, Notion page or Markdown.
- 02
Choose the scope.
Hand off the whole project or selected frames, with an optional note for the agent.
- 03
The agent writes the change.
It follows your repository's conventions and checks its work against your typecheck and lint.
- 04
Review and merge.
It opens a pull request on a new branch. Ask for changes and it updates the same pull request.
Pick the repository. The agent reads it to follow your conventions and checks its work against your own typecheck and lint.
The pull request opens. Your base branch is untouched until you review and merge.
Real code to review. In this example, 7 files and 682 added lines, written to fit the existing code.
Plans
Or send a plan.
File a Linear issue, a Notion page or a GitHub issue with an implementation plan, or copy it as Markdown. Plans name your real files and components, so they're specific enough to build from.
Guardrails
Safe to point at your repository.
The agent works on a branch, in a sandbox, with limits on what it can touch.
Never on your base branch. Nothing changes on main until you review and merge the pull request.
Checked in a sandbox. Typecheck and lint run on a disposable machine with no secrets.
Protected files. The agent can't edit CI configuration or secret files.
Dependencies stay put. package.json and lockfile changes are off unless you allow them.