Skip to main content
Some Tools have a synthetic browser application. Open it to inspect the same data your agent reads or changes through the Tool’s API or MCP interface. A catalog page describes a Tool. An instance page describes the particular running copy in your selected project and environment.

​
Open an instance

  1. Open Tools in Firedrill.
  2. Select the intended project and environment.
  3. Open an instance created through the CLI, SDK, or manual web setup.
  4. Use its browser preview or Open Tool action when available.
The instance view shows current status, expiry, starting dataset, activity/history, and connection details. A Tool without a browser app can expose a supported record view instead. Opening a browser app does not connect or launch your agent. Run the agent from your CLI or SDK workflow.

​
Starting data is shared

The browser app uses the instance’s actual selected dataset. If your CLI or SDK created the instance with a saved dataset, those are the records it displays. Browser writes and agent Tool calls affect the same synthetic state. Starter data is explicitly authored synthetic input. Firedrill does not read your production service account to populate it.

​
Access is scoped and temporary

The portal obtains a short-lived instance-specific browser grant. Opening the Tool in another tab uses a fresh grant, not your account’s operator credential. If an embedded preview is blocked by browser cookie policy, use Open Tool to open it separately. An expired connection, reset, ended instance, or revoked account access cannot be made active by refreshing an old URL.

​
After the instance ends

Its retained metadata, activity, and associated results remain inspectable according to retention. The live preview and active connection are unavailable. You can deliberately start another instance from the chosen build and dataset; ending an instance does not erase its recorded outcomes.