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

# The console

> The dashboard at frostwolf.app/dashboard: overview, telemetry, Cloak, captures, keys, and team.

Sign in at [frostwolf.app/dashboard](https://frostwolf.app/dashboard). Everything in the console is scoped to your workspace.

## Overview

What the engine decided in the selected window, and what was done about it: events, detections, blocks, sanitised requests, and allowed traffic. It breaks detections down by source (prompt or tool call), severity, and the rules that fired most, and shows traffic over time, your plan usage, and tool-validation totals.

Pick a window of 1 hour, 24 hours, 7 days, or 30 days.

## Telemetry

Every decision the engine made, newest first. Prompt content is never part of this list. You can filter by severity or by rule.

## Cloak

What Cloak did in the window. **Counts only.** No value, token, or offset is ever shown, because none is ever sent.

| Panel | What it tells you |
| - | - |
| Protected | Requests that used Cloak. |
| Values replaced | How much personal data was kept out of the model. |
| **Unchecked** | Requests the detector never answered for. The SDK refuses these by default. A non-zero number means Cloak was unreachable. |
| Restored | Tokens put back into responses, and how many were unknown. |
| **Refused restores** | A token that turned up in a response for another identity. The one Cloak event that means something went wrong. |
| By category, type, strategy | What was replaced, and how. |

Unchecked and refused restores are highlighted when they are not zero.

## Validator

Paste a prompt and see the verdict the SDK would get. It runs the same engine as the API, authenticates with your session, and records nothing.

## Captures

Request and response bodies, when capture is on for a key. Bodies are fetched one at a time.

## API keys

Create, name, and revoke keys, and turn capture on or off per key. A key is shown once, when you create it.

## Team

Invite people and set their role. A role decides who can create keys and change settings.

## Settings

Workspace settings.


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