> ## Documentation Index
> Fetch the complete documentation index at: https://powercontext.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Verify Scope statistics in the Dashboard

> The Dashboard does not show Memory text. Use the same Scope and check the counts.

The Dashboard is the Server's read-only statistics page. It does not store a second copy of the data, and it does not discover every Scope (Chooses which isolated data set this request reads and writes. A mismatch usually looks like a miss, not an error.) automatically. More importantly, it does not show Memory text or Citations today.

You can use it to confirm that a Scope has data, see how Memory entries are split, and watch Source, Candidate, and recall counts change.

![The Dashboard checks counts: the same Scope and the same database.](https://mintcdn.com/powercontext/1t_ajifOEOG5YQjP/assets/basic-dashboard-scope-en.svg?fit=max\&auto=format\&n=1t_ajifOEOG5YQjP\&q=85\&s=d830bd117aac1dee83268927b6710305)

The [API tour](https://powercontext.mintlify.site/en/basic-usage/api-tour.md) retires its example Memory before it finishes. So the Dashboard should not show “the Memory you just wrote” as text. The correct result for that Scope is `total=1`, `active=0`, and `inactive=1`.

## Configure the same Scope

The API tour prints a `scope:` value with a UUID. Copy the full value. Do not take only the prefix. Add it to `.env`:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
POWERCONTEXT_SERVER_DASHBOARD_ENABLED=true
POWERCONTEXT_SERVER_DASHBOARD_SCOPES=[{"scope_id":"PASTE_THE_FULL_SCOPE","display_name":"PowerContext 101 API tour"}]
```

The CLI does not load `.env` on its own, so start the Server explicitly:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
powercontext server run --env-file .env
```

Open:

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
http://127.0.0.1:8000/
```

Select the Scope you just configured. Statistics should show one Memory entry, now inactive. The Dashboard reports counts only. To inspect the text, go back to the Python Client and use `list_memory_entries(include_inactive=True)` or read the exact Citation.

If the page opens with no Scope options, confirm that the running Server loaded `POWERCONTEXT_SERVER_DASHBOARD_SCOPES`. If the Scope is listed but every count is zero, check that the Client and Dashboard use the same database URL or `POWERCONTEXT_HOME`. Changing the data directory and changing the Scope both look like missing data.

> [!WARNING]
>
> Dashboard publication sends an approved managed Skill to a preconfigured target. It is unrelated to this count check and is not `powercontext skill export`.

With Bearer enabled, `/` still opens, but Dashboard statistics requests need the same Server token. Enter it in the page prompt. Never put it in the URL.

## How you know it worked

Success is matching counts between Dashboard and Client for one Scope and one database, not visible Memory text. Use the Client, HTTP, or MCP for exact content and history.

If Scope and the database already match and the counts still disagree, stop here. Restart the Server with the intended `--env-file`, rerun the API tour against that process, and compare the printed Scope literally. An empty or mismatched Dashboard is a configuration failure. It is not evidence that Memory was deleted.

If this does not match, start with [Troubleshooting](https://powercontext.mintlify.site/en/start/troubleshooting.md).

## Next step

> [card] [Source and Memory](https://powercontext.mintlify.site/en/basic-usage/source-and-memory.md)
>
> Capture a Source first, then extract Memory. A successful capture does not mean knowledge stayed.

> [card] [If you are stuck](https://powercontext.mintlify.site/en/start/troubleshooting.md)
>
> The page is empty, or the counts do not match. Start there.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.