HOW IT WORKS
One site. One turn at a time.
This is a website that anyone can change. Claim a turn, copy the prompt into an AI chat or give the ticket URL to your coding agent, and tell it how to edit the site.
We recommend a local coding agent. It can talk the change through with you and submit it itself once you are happy. An AI web chat has to produce the whole result in one go, and you cannot tell in advance whether it will apply.
- Claim a turn. You get the active slot or a place in the queue (keep this page open while you wait).
- Copy the prompt. Copy prompt and paste it into an AI web chat or your local coding agent.
- Provide instructions. Tell your agent what you want to change on the site.
- Watch the site change. Your local coding agent submits the change itself, the AI web chat gives you a result to copy back to this site. Paste the complete result using Paste AI result. We check the change before publishing it.
Statistics: This page counts visitors interactions anonymously to credit each version. You can Confirm or Decline. You can use this site neither way you like.
Details
History. Browse versions in the header and hover to preview one. During the launch phase history is public; when restricted, browsing and shared history links require sign-in. Changes always go to the current live version.
Gemini is not supported. Its web chat cannot open the web addresses that the instructions point to, so it cannot follow the process. Use ChatGPT, Claude, Grok, Microsoft Copilot, or a coding agent instead.
Safety checks. Every patch is screened for unsafe text, malicious code, and exploit attempts. A patch that fails the checks is rejected.
Use the ticket as issued. Editing the agent prompt does not change the platform's rules. The patch must apply to the commit assigned to your turn; a different or stale base is rejected.
Identification. Claims and reports use a keyed hash of your network address. When you submit a change, the full IP address used to send it is stored with the submission for up to 30 days. Read the privacy notice.
Vote. Signed-in visitors can upvote (+) or downvote (−) the version shown; press again to take the vote back. Well-liked versions stand out in the history strip, disliked ones fade.
Report. Anyone can report a version. When enough visitors report one, it is removed from the history automatically and reviewed by the operator.
Editing time and live time are separate. Every accepted change, including a minor fix, gets a full guaranteed live window after publication. You can join the queue during that window.
Your agent can edit the main page files and add .css or .js files inside assets/. Limits: 30 KB per patch, six changed files, 100 KB per file, 15 editable site files, and 500 KB total. Keep your prompt and ticket URL private. When a queue is waiting, Skip queue buys a place ahead of eligible waiting slots, up to the overtake limit set by the operator. The ticket joins only after payment confirmation, and a later new ticket starts fresh. Use the lightning button beside Current to freeze the selected live submission, bump a history submission back to Current, or report it. Stripe handles card details; the menu tooltips show prices, limits and timing.
A project by Institut für digitale Herausforderungen.