CLI and dashboard together
The dashboard and CLI share the owned app catalog. An app created with your agent key appears under the same platform account. The display name, immutable ID and stored URL describe the same app in both tools.
What you can inspect
Section titled “What you can inspect”- App state, tier, deployment and operation results.
- App users and authentication settings.
- Supported model data and owner controls.
- Event deliveries, attempts and job history.
- File metadata and the account object allowance.
- Scoped metrics, logs and traces when their sources are available.
Access follows current ownership and explicit grants. App-user/admin credentials do not become platform credentials. Internal operator access has a separate grant; ordinary customer or agent roles do not receive it.
Credentials and actions
Section titled “Credentials and actions”The dashboard uses a native platform browser session. The CLI uses an expiring agent key created under Agent credentials. Revoking a key affects that key; it does not automatically delete apps or users.
Browser state-changing requests retain same-origin checks. Protected account responses must not become shared cache entries. Keep agent keys and app tokens out of URLs and screenshots.
Telemetry limits
Section titled “Telemetry limits”The dashboard uses the current scoped telemetry API. Cached metrics are the default; the realtime option has separate behavior. Some sources can be delayed or unavailable. Missing counters mean unavailable, not zero usage.
The platform’s remaining telemetry qualification includes resource overhead, failure behavior and a native trace queue fsync issue. The dashboard is useful for development, but complete telemetry reliability and production HA are not current release claims. Read status and limits.