Find your work in USER.

Use the wallet that owns the project.

Connect and sign with the owning wallet in the site header. Signing in establishes an owner session; it is not a token launch or a payment. See the wallet guide for setup and prompt checks.

My overview groups My projects and My account. It does not automatically open every project or billing record. If a list is empty, first check the connected wallet and whether loading succeeded. Unavailable data is not an empty account; do not create or pay again to compensate for missing records.

Each category has one purpose.

• My agents: select one owned agent to open its workspace, proofs, settings or operational controls.
• My token launches: saved launch attempts and confirmed tokens. A pending attempt needs reconciliation, not a duplicate transaction.
• My custom requests: follow scope agreement, approval, delivery and publication.
• My code audits: follow repository requests and open the complete authorized report.

Creation starts from START; public discovery stays in EXPLORE. USER lists manage work that belongs to your signed wallet. Archived agents retain evidence and recovery links without reopening ordinary runtime configuration.

Native agents and approved custom RUNCHECK deliveries receive scoped certification automatically when their required checks pass. Inspect that evidence in My agents; do not register the same project for manual external verification. GitHub code audits for external or custom RUNCHECK source remain separate requests in My code audits.

Purchased credits are not the available balance.

My credits & services shows confirmed credit purchases and top-ups saved by RUNCHECK, with their receipts, 50 at a time. Use Load older purchases to continue through the history and Export shown purchases (CSV) to save the records currently displayed. Historical purchased credits do not account for later usage and are not pooled across agents.

Use Check available credits for the specific agent to request its reported billing balance and usage. This is a separate read from refreshing saved purchases. BYOK provider spending and pending purchases are not included in the purchase history.

The AI credits guide explains setup, pricing presentation and service limits.

Connect during a request; manage access here.

Public repositories do not need a GitHub connection. When a requested repository needs private access, authorize the GitHub App in the request flow and select only the repository being reviewed. Never paste a GitHub token, wallet key or source secret into a request.

My GitHub connection lets you inspect saved authorization and revoke wallet access. It does not start a code scan or offer a separate connection shortcut. Revoking access stops future authorized reads; an already completed outcome may remain as historical evidence with monitoring stopped.

Read the complete privacy policy for data handling and access choices.

Refresh the data, not the operation.

My activity records saved owner controls. It is not an exchange fill history or a new health check of every agent.

Refresh controls sit beside the relevant status or at the end of its section. A saved-status refresh does not launch a token, begin an audit or grant provider consent. A separately labelled on-chain or provider check reads that named source; read its label before using it.

Public showcases and private records stay distinct.

Tokens, Agents and Reviews under EXPLORE are public showcases. They do not expose all the projects and private requests in USER. Public visibility is separate from ownership, evidence status and operational permissions.

Completed private-repository audits have limited public summaries; full private reports remain owner/admin restricted. For how to interpret those outcomes, read Checks & evidence.