Skip to main content
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 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. The API tour 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:
The CLI does not load .env on its own, so start the Server explicitly:
Open:
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.
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.

​
Next step

Source and Memory

Capture a Source first, then extract Memory. A successful capture does not mean knowledge stayed.

If you are stuck

The page is empty, or the counts do not match. Start there.