Inspect and operate infrastructure with approvals.
The ServerChirp assistant can inspect team resources, explain state, and run authorized operations from the dashboard. It uses the same tool catalog, public schemas, entity resolution, and scope-to-permission mapping as the REST API and MCP.
The assistant receives a stable system prompt and a small resource index containing names and IDs. Live state is fetched through tools when needed rather than interpolated into the prompt.
Tool context is derived from the signed-in principal, including the member's role and resource grants. A resource that is missing and one outside the member's access both appear as not found.
Read operations can run without a mutation approval. A tool backed by a :write scope is a mutation and produces an approval card before execution.
Approvals are HMAC-signed so a browser client cannot forge permission to run an operation such as rebooting a server. Review the exact tool, resource, and arguments before approving.
Ask for a goal and include the operational boundary:
Check why checkout-api is unhealthy. Read-only investigation only.Show the failed deployment for docs-web and propose a recovery plan.
Do not deploy or restart anything until I approve it.The assistant is an operational interface, not a separate authorization system. It cannot bypass team permissions, plan features, API scopes, or entity access checks. You remain responsible for reviewing proposed mutations and their production impact.