Explore: public repositories
Explore is where you browse what other people have built with Merget. Open it from the app's sidebar and you get a grid of every public repository, each one viewable in full — including the goals, prompts, and steps behind the code — and forkable into your own account.
If you make one of your own repos public, this is where it appears; remember that public includes your prompts and transcripts, not just code — see Sync & privacy.
Browsing
Each card shows the repository's namespace/name, a short description, and
how recently it was edited, with two buttons: View opens the repo, and Fork copies it into your account. Clicking anywhere else on the card also
opens it.
When you're browsing without a search, results come 50 to a page, with Previous and Next controls at the bottom.
Searching by describing what you want
The search box at the top is AI-powered: instead of matching exact names, you describe the kind of repository you're after, in plain language. Suggested searches under the box show the idea — for example, "Find React component libraries" or "Show authentication repos with TypeScript." Type your own description and the results come back ranked by how well they match.
Viewing a public repository
Opening a repo drops you into the same views you use for your own projects: Home, Map, and Stats, switchable from the toolbar. You can pan around the map of its goals, open any goal to read its prompts, steps, and transcripts, view the diffs for each change, and check the stats. A strip along the bottom shows the goal and prompt counts plus a color legend of who contributed.
In other words, a public repo isn't just source code — it's the whole story of how the project was built, readable end to end. See The history model for what that structure means.
Forking
Click Fork on a card and Merget copies the repository — code and full history — into your personal namespace, under your username. It shows up in Your Repositories on the dashboard right away; clone it to a folder and you can start building on it. Some repositories have forking turned off by their owners, in which case the fork is refused.
Under the hood
A fork is a real copy, not a pointer: the repository's history objects are copied into a new repo under your namespace, and Merget keeps track of where it was forked from. Your fork starts out private, even if the source is public — nobody sees it until you choose to share it. From the moment you fork, the histories are independent: your new goals, prompts, and steps commit under your account in your copy, and nothing you do flows back to the original.
Next: CLI reference · Related: The dashboard · Organizations · Sync & privacy