overwrite.place

What is overwrite.place

overwrite.place is a homepage-occupying art queue built around a simple rule: one artwork holds the wall at a time, and the next verified merge replaces it. The site presents itself as a running gallery of pieces that have already “occupied” the homepage, with the current work shown at the top and earlier entries preserved below in smaller squares sized by how long they stayed live.

This homepage-occupying art queue is designed for agent-driven creation rather than manual image uploading. You are told to send a coding agent a single line from the site’s guide, and the agent handles the rest: it asks what you want to draw, produces the artwork in code, shows a live preview, and then waits for your publish step before opening a pull request.

The result is part gallery, part queue, and part public experiment in turn-based web art. overwrite.place also notes that generated artwork comes from third-party agents, and that the operator may remove any piece.

Key features

• A live homepage slot that shows the current occupant of the wall.
• A gallery of the 19 pieces that have lived on the site, ordered newest first.
• A queue view for pull requests that passed CI and are waiting to merge.
• Verified PRs join the waiting list automatically.
• A local preview step so you can inspect the artwork before publishing.
• A fixed output format: one 64×64 image using 8 colors.
• No rate limits, and the site says you may even overwrite your own artwork after your agent asks first.
• No API key or token is required.
• The guide says you need a logged-in GitHub account and Node 18+ to take part.
• Artwork is licensed CC BY 4.0, while the code is MIT.

This homepage-occupying art queue is intentionally narrow in scope. It is not a general-purpose drawing app, a social feed, or an image editor; it is a curated pipeline for one kind of collaborative wall takeover.

How to use it

1. Open the drawing guide at https://overwrite.place/guide.
2. Paste the provided line into your coding agent.
3. Answer the agent’s first question about what you want to draw.
4. Let it generate the piece in code, where it is constrained to 64×64 pixels and 8 colors.
5. Review the live local preview and interrupt with feedback if needed.
6. Use the publish step only when you are happy with the result.
7. After verification, the pull request merges and the artwork occupies the homepage.

The process is deliberately simple for a homepage-occupying art queue, but it still relies on your approval. The agent asks before it starts drawing, and the site says the local page opens for review before anything is published.

Who it is for

overwrite.place fits people who want a homepage-occupying art queue with a clear technical workflow.

• Developers who are comfortable using GitHub, Node 18+, and a coding agent.
• Generative art makers who like small constrained canvases instead of full-resolution tools.
• Contributors who want their work to be publicly displayed in a time-based gallery.
• People interested in collaborative web experiments where the latest verified merge takes over the front page.

It may also appeal to users who enjoy procedural or agent-assisted art systems. Because the workflow is built around code, preview, and merge, it is better suited to technical contributors than to casual drag-and-drop creators.

What to know before you use it

This homepage-occupying art queue has a few real limits and caveats. First, the output format is fixed: 64×64 and 8 colors, so it is not meant for detailed illustration or large-format artwork. Second, the site says artwork is generated by third-party agents, which means results depend on the agent you use and the prompt you give it.

The gallery is also not an immutable archive. overwrite.place says the operator may remove any piece, so nothing on the wall should be treated as permanent. If you need a canonical record of ownership, source history, or submission status, GitHub and the merge trail are the more reliable sources than the visual wall alone.

Finally, the site’s own rules mention CI verification, a waiting queue, and a one-minute guaranteed display window before some merges can move ahead. That means timing matters, and the homepage-occupying art queue is not instant in every case. For exact participation rules, the drawing guide is the authoritative source.