Skip to main content
If you’re an engineer and a designer sent you a pull request from Onlook, this page is for you. The short version: it’s an ordinary branch and pull request.

​
What Onlook did

  • It made a git worktree. The worktree is in Onlook’s own folder, on a new branch based on your main branch. After the designer’s first request, the branch is named after the project, with a prefix from your GitHub organization or the designer’s git name, like acme/pricing-hero.
  • The agent worked only in that worktree. Onlook refuses to run the agent anywhere else. The designer’s own checkout was never edited.
  • The agent ran your project the normal way. It used your package manager and your dev command.
  • Commits and the pull request are ordinary. They’re authored under the designer’s git identity and pushed with their GitHub account. With Claude, the designer approved each push.

​
What Onlook didn’t do

  • It didn’t commit environment files. Onlook copies the .env files your repo already ignores, so the app can run. Your .gitignore keeps them out of commits, as it does for you.
  • It didn’t change your agent instructions. If your repo has an AGENTS.md or CLAUDE.md, the agent follows it. Onlook adds its own context on top without replacing yours.
  • It didn’t upload your code to Onlook. The agent sends context to the designer’s own Claude or ChatGPT account, the same as if they used those tools directly.

​
Reviewing and giving feedback

Review it like any other pull request. Comment on GitHub as usual. The designer can paste your comment into Onlook and ask the agent to address it, then push the fix to the same pull request. If checks fail, the designer can press Fix Checks, and the agent reads the failures and tries to fix them.