Administrator-only tools
Understand the additional Playground, Admin Runs, and catalog views available to administrators.
The Dev Tools section is shown to accounts with administrator access. Regular users can run their permitted workflows through MCP and monitor them through Queues and My Runs without these pages.
Playground
Open Playground from the administrator navigation.
LLM Chat provides a plain conversation with a configured AI adapter. Create or select a chat, choose the available connection settings, and send a message.
LLM Device Chat binds a chat to device work. Its creation flow collects a title, AI adapter, device, prompt preset, and the required inputs for that preset. Complete the requirements before creating the chat. Device chat can perform real phone actions through its permitted tools.
Where an observation includes a screenshot, open it to inspect that captured moment. Acknowledged tool delivery and a verified on-device effect are separate observations; read the reported result and evidence.
Use only currently enabled Playground entries. A visible deferred or unavailable tool does not provide a usable workflow.
Admin Runs
Admin Runs provides the permitted administrator run views and diagnostics. Inspect the exact run and selected attempt before using available Play, Cancel, or Advance controls.
Use Advance only for a run that is waiting for an administrator decision. It is not the normal retry action for a failed run.
LLM Templates
The guarded LLM Templates area exposes the available catalog views. Use it to inspect the metadata currently offered. Strategy and prompt-content authoring is performed through the permitted MCP operations; retired browser editors are not an alternative authoring path.
Account permissions still matter
Administrator visibility in the web app does not mean an external API key can read or change every user's private source. MCP keys keep their credential-specific ownership and permission rules.
Use the actual owner's records for source changes and your own permitted execution inputs when preparing work. Do not treat another user's visible strategy metadata as access to their accounts, mailbox credentials, or saved resources.
For normal workflows, return to Strategies, Queues, and Run monitoring.