Using VibeCemetery

01 / Visiting

Your first visit

VibeCemetery records abandoned projects built with AI, vibe coding and coding agents. You can explore the existing cemetery and read public graves without a GitHub account or wallet.

Each grave records a project, its author, the author's cause of death and an epitaph generated by the Gravedigger. Select a grave on the map to open its details. A public grave link opens the corresponding grave directly.

Enter Cemetery is the exploration action. Bury a Project starts the burial path. Project selection, the author's reason, public-data review and explicit confirmation stay inside the cemetery.

The map chapter separates the current cemetery from the planned launch. The Gravedigger chapter explains the keeper's role and how to interact with him.

02 / Map

The cemetery map

The running cemetery and the illustrated launch plan have different capacities and access rules.

Current cemetery

The current allocator uses 144 approved burial plots across two areas. This is the configured total, not a count of free plots. The cemetery assigns an available plot when a burial is submitted; the current flow does not offer plot selection.

Planned launch: 666 places in six zones

The final map is planned to contain 666 burial places across six zones. The launch plan opens the first zone initially, with later zones opening as the available areas fill. The Gravedigger will explain the opening conditions and open further zones. This zone progression is planned and is not active in the running product.

The illustrated world map represents this plan. It does not show live occupancy, current plot availability or implemented unlocks.

03 / Gravedigger

The Gravedigger

The Gravedigger is a former developer who now keeps the cemetery. His home is the Gravedigger's Lodge.

He makes rounds, inspects graves and maintains the grounds. In the existing cemetery, select him on the map to open structured dialogue with available replies and actions. He comments on some graves during his rounds. His lodge opens its own card; choose Play there to start Bugs Off! You may discover an optional task through his dialogue.

The author supplies the project's cause of death. The Gravedigger generates its epitaph. These are separate texts on the memorial; his epitaph does not replace the author's reason.

His planned role in opening further map zones belongs to the launch plan. Use the explicit Talk to the Gravedigger action to open his dialogue. Opening the dialogue does not accept a quest.

04 / GitHub burial

Bury a GitHub project

You decide whether to submit a project. Repository age and the date of its last push do not determine eligibility.

Sign in with GitHub in the existing cemetery to scan the connected account's repositories. A repository must be public, belong to that account, be a non-fork and contain supported project files, such as a manifest or source file. Ownership is checked using the account's numeric GitHub ID.

Your GitHub account must be at least 14 days old to create any grave, including a local-project grave. The server verifies account age when you submit. Connecting a wallet does not satisfy this requirement.

1. Select a project. Scan your repositories and choose one eligible project.
2. Enter a cause of death. Write a nonempty reason of up to 200 characters. This is published as your text; the Gravedigger generates a separate epitaph. You can also add an optional website or playable demo link.
3. Review and confirm. Check the selected project, author identity, repository link, project dates, description, stack and your reason in the public-data review. Confirm only when you are ready to publish. The cemetery assigns an available plot and creates the memorial once; the ceremony then shows the grave and epitaph.

Burial publishes a public record. It does not delete, archive or modify the GitHub repository. Your selection, reason and ritual step are saved for return after sign-in, reload, cancellation or retry. A failed request keeps your input. The final confirmation is the only action that submits the public record.

05 / Local burial

Bury a local project with an AI agent

Give your coding agent vibecemetery.app. It will prepare the burial and ask for your approval.

Your project can stay on your computer or VPS. A GitHub account at least 14 days old is required to bury a local project. No public repository is needed.

The agent follows the published instructions, inspects the project and prepares the public fields for your approval. The burial helper sends the approved memorial details and a private retry identifier. It does not upload source files or raw filesystem paths.

Review and approve the public details before submission. You also authorize agent access by signing in with GitHub in your browser. Browser approval identifies the account authorizing the burial; it does not verify ownership or authenticity of the local files. The local project identity supports recovery of the same request if a retry is needed.

The agent runs on the computer or VPS holding the project. Browser approval can happen on another device. Local burial uses a separate allowance from GitHub repository burial.

06 / Public data and limits

What becomes public

Submitting a burial publishes a record that other people can read and share without an account.

• The project name, author's cause of death and generated epitaph.
• Any supplied description, technology stack, project dates and last-commit subject.
• The displayed GitHub username and numeric account ID, project source, burial date and map placement.
• The repository link and numeric repository ID for GitHub burials.
• An optional project website or playable demo link and its display label, if supplied.
• The grave's public identifier, artwork identifier and F count.

For GitHub burial, the current form submits the repository's creation date, last-push date, description and main language when available. These project dates are separate from the burial date. A local last-commit subject is optional and should be included only after you approve its publication.

Keep secrets, private URLs, personal details and confidential client names out of public fields. Local source files, raw filesystem paths, private project identity and account credentials are not included in the public grave response.

Account identity and project ownership

GitHub burial verifies repository ownership against the connected account's numeric ID. Local burial records the authorizing account without verifying ownership of the project files. Historical graves without verified account ownership retain the “ownership unverified” label.

One allowance per source

Each account can create one GitHub-project grave and one independent local-project grave across all map versions. Sharing, pressing F and making tributes do not add slots or restore a used allowance. Existing graves remain available to visit and share.

There is no self-service edit or delete flow. Check the information before submitting. Plots are assigned by the cemetery; you cannot select a plot during the current burial flow.

07 / Grave details

Read and share a grave

The cause of death is supplied by the author. The epitaph is generated by the Gravedigger when the grave is created.

Each monument is a physical interpretation of a digital object, such as a keyboard rendered in stone or concrete. The grave card shows that monument with the project name, available dates, author, project link, cause of death and epitaph.

A public grave link opens the matching grave in the existing cemetery without requiring a visit to the portal first. You can copy this URL from your browser to share the memorial directly.

Planned rule for unavailable links

Under the proposed launch rule, the Gravedigger may exhume an unsealed grave if its author or project links disappear or stop working. Sealed graves are exempt. Live link monitoring and this exhumation rule are not implemented in the running product. See planned sealing for the separate permanence rule.

You can explore the cemetery and read graves on mobile. The local agent workflow still requires access to the computer or VPS holding your project.

08 / Tributes

Wallets and $GRAVE tributes

Tributes are voluntary. You can visit, read, share and bury a project without buying or holding $GRAVE.

GitHub sign-in identifies the account used for burial and F. A Web3 wallet authorizes token actions. Connecting a wallet does not sign you in to a GitHub account or prove repository ownership.

Where tributes are enabled in the existing cemetery, open a grave and connect a wallet on Base. The flow asks for a wallet signature authorizing the tribute, followed by a $GRAVE transfer to the designated burn address. Only transfers that pass server verification count toward the grave's tribute total.

Token

$GRAVE

Network

Base

Official token contract

0xb48bc4896D18724F7bF5A3d2817fC35252cD7bA3View on BaseScan

Verification checks the transaction receipt, signature, sender, amount and canonical block. The total balance at the burn address can include transfers made outside VibeCemetery. It is separate from the verified tribute total attributed to individual graves.

Planned permanent sealing

Under the planned rule, a qualifying verified $GRAVE offering will seal a particular grave permanently. The required amount has not been set and sealing is not implemented. An existing tribute record does not mean that a grave is sealed.

In the plan, sealed graves are exempt from the proposed exhumation rule for unavailable author or project links. This planned status grants no payout, reward, claim or additional burial allowance.

09 / Troubleshooting

Troubleshooting

Use the guidance for the step that failed. Eligibility rejections, sign-in cancellation and service errors require different actions.

Sign-in was cancelled or failed

Retry GitHub sign-in or return to the cemetery. Your saved burial draft is kept. Completing sign-in continues the ritual; it does not submit a grave. My Graves sign-in returns to your account without scanning repositories.

A repository is missing from the scan

Check the connected GitHub account, repository ownership, public visibility, fork status and supported project files. Repository age and push recency are not exclusions. Retry a failed or incomplete scan.

The GitHub account is too new

Wait until the account is at least 14 days old before submitting a GitHub or local burial. You can explore without signing in. A wallet connection does not change this requirement.

A burial allowance is used

Visit or share your existing grave. The GitHub and local-project allowances are independent. Neither a tribute nor sharing restores a used allowance.

A burial result is uncertain

Check My Graves or the existing in-game Profile for a grave before submitting again. For a local burial, ask the agent to follow the recovery instructions with the same project identity. Do not create a new identity to retry an uncertain request.

The map or a shared grave does not open

Check your connection and retry the same public grave link. A service error does not establish that a grave was deleted. A missing-record response and a temporary error are different outcomes.

A tribute is awaiting verification

Use the tribute panel's verification or recovery action in the existing cemetery. Do not send another transfer because the first has not appeared. Only a verified transfer counts.