Repository Detail

The repository detail page is the main interface for working with a single repository. It combines a header with key metadata, a tab bar for navigating different views of the data, and permission-aware controls for editing.

Header

The top of the page displays:

• Repository name in large text.
• Visibility badge — a globe icon for public repositories or a lock icon for private ones.
• MCP badge — a clickable badge displaying the repository’s Model Context Protocol (MCP) endpoint path. Click it to copy the full MCP URL to your clipboard.
• Actions dropdown — a pencil icon button (visible only to users with repo:settings permission, i.e. admins and above) that opens a menu with options to rename the repository or edit its description.
• Description — the repository’s description is displayed directly below the header line.

Tab Navigation

Below the header, tabs organize the repository’s content:

1. About (default) — README, data dictionary, and sidebar info.
2. Things — Thing browsing and search. See Things and Wrefs for the data model behind this tab.
3. Assertions — Assertion browsing for the repository, with source reputation, filters, and BDU meters. See Assertions for the underlying data model.
4. Actions — Subscription management (webhooks and crons). Only visible to users with repo:settings permission.
5. Components — Installed components and their configuration.

Non-default tabs are reflected in the URL as a query parameter (for example, ?tab=actions), so you can bookmark or share a direct link to any tab. The default About tab omits the parameter.

Permissions

Repository actions are gated by role-based permissions. For background on how authentication works, see Authentication. The table below maps each permission string to the minimum role required:

Permission	Minimum role	Grants
repo:settings	Admin	Manage subscriptions, credentials, rename repo, edit description
things:write	Editor	Create and revise things (including the README)

• Read access — All tabs except Actions are visible to anyone who can view the repository. Browsing data does not require write access; use wh thing history for per-thing version trails.
• Actions tab — requires repo:settings (admins and above). Users without this permission do not see the tab.
• Write access — Different actions require different permission levels:
  • Edit README — requires things:write (editors and above), because the README is stored as a thing and goes through the write path.
  • Rename repo / edit description — requires repo:settings (admins and above).
  • Actions dropdown — only visible to users with repo:settings permission.

CLI Equivalent

To view repository metadata from the terminal, use wh repo view. For a full list of CLI commands, see the CLI reference.