Turn visual changes into structured instructions your coding agent can understand and implement.
Any of them. Claude Code, Cursor, or anything that can make an HTTP request. There is nothing to install on the agent's side.
Press Connect coding agent in the Pixy menu, copy the instructions and paste them into your agent. The invitation inside works once and expires in ten minutes, so no lasting secret goes through a chat window. The card says connected as soon as the agent signs up. See Agents.
You design, then you tell your agent to check Pixy. It pulls with its own key, builds what it finds, answers in the thread and acks each record when it is done. Nothing is copied by hand.
Nothing is lost. A pull does not close a record, only an ack does, so an unfinished batch comes back on the next pull. The lock it was holding can be released from the panel.
Only when you want a titled batch with a conversation on it. Otherwise just edit. The agent names a task itself when it acks, and files the finished work into it.
Yes, one per person if you like. The panel lists each agent, what it is building and when it last pulled. Removing one refuses its next call, and everything it already built stays.
One, at api.pixydesignapp.com. Every call is a POST with JSON and the key in an X-Pixy-Key header, and every documentation page is served as plain .txt so an agent can read the API itself. Calls are unlimited on every plan. See API.
One project's edits, conversation and images. Not your account, not your other projects, not your billing, and never your site directly.