Public repair pipelineSee what the community
See what the community
wants fixed next.
Every request starts as an idea—not executable code. Track it through privacy checks, live-page inspection, constrained authoring, browser tests, and registry publication.
—open requests
—being built
—published
How review works
A visible path, with safety gates.
A label change reflects a real review stage. Publication requires a constrained patch, tests, selector health, and human approval.
- 1IntakePublic URL and privacy structure checked
- 2AcceptedUseful, public, and safely scopeable
- 3AuthoringCodex inspects DOM and screenshots
- 4Patch reviewDSL, browser tests, and SHA-256 verified
- 5PublishedHealthy repair enters the registry
No requests in this view yet.
Be the first to describe a public website problem. The guided form removes query strings and helps you review exactly what becomes public.
Request a community repair →The public queue could not be loaded.
The repair registry is still available. You can retry or open the source queue directly.
Open GitHub queueImportant boundaryRequests are public ideas.
Requests are public ideas.
They are never auto-installed.
The public view intentionally displays only issue metadata: title, author, labels, timestamps, and link. Patch the Web never copies private page data, form values, cookies, storage, credentials, or URL queries into this dashboard.