Design changes, without the round trip

Your designer
stops filing
tickets

Hand her a link. She points at what's wrong on the real running app, says what she wants in plain words, and it comes back to you as a pull request.

no repo access · no local setup · no “can you just…”

Any stack. Node, Python, Ruby, Go, PHP Your keys. Claude Code or Codex Your git. Branch, commit, PR
preview.mzj.ai/s/9f3c… — pricing page
Ship the design you actually drew
Stop writing bug reports. Point at the thing that is wrong.
Starter$0
Team$29
Business$99
✦ MagicYard

The actual cost

One wrong margin, and six people get involved.

Today

  1. She spots it in staging
  2. Writes a ticket describing it
  3. …waits
  4. You read it, guess what she meant
  5. You brief a front-end developer
  6. …waits
  7. Developer changes it, deploys
  8. She checks. It's not quite right.
  9. …and round again

Elapsed: two days, four people, one spacing value.

With MagicYard

  1. She spots it in the preview
  2. Clicks it and says what she wants
  3. Sees the change land, live
  4. Keeps it, or tries again
  5. You review the pull request

Elapsed: four minutes, one person, and you never left your review queue.


How it works

Three steps for you. One link for her.

01 / SETUP

Connect a repository

MagicYard clones it, works out how to install and start it, and shows you what it found. It proposes — you decide. Wrong guess? Correct it in a text box.

02 / SHARE

Send one link

Your app boots in an isolated sandbox with the editing toolbar attached. The link expires when you say, and revokes the moment you click revoke.

03 / REVIEW

Merge, or don't

Every approved change is committed to a branch of its own and arrives as a pull request — with her own words attached, so you know what she was reaching for.


Two people, one product

Built for the gap between them.

You, who owns the code

Nothing leaves your control. She never gets repository access, never sees a credential, and never touches your default branch.

  • Your own Claude or OpenAI key, with a spend cap per link
  • Isolated sandbox per session — not your laptop
  • Every change on its own branch, arriving as a PR
  • Revoke a link and the session dies with it

Her, who can see what's wrong

No terminal, no clone, no install, no waiting. The app she opens is the real one, running, with her changes appearing as she asks for them.

  • Opens in a browser — nothing to set up
  • Point at an element and describe the change
  • See it live before deciding to keep it
  • Hand it back without knowing what a branch is

Stop reading
bug reports.

Connect a repository and send your first link in about five minutes.

Get started The toolbar is open source