Skip to main content
Firedrill Cloud is in private preview.
A session is one isolated running world pinned to a project, environment, build, seed, and starting setup. Creating a session never starts your agent.

Choose the starting setup

Create a session with exactly one of these choices: Every session requires a decimal unsigned 64-bit seed. You may also pin an exact build hash and explicitly select approved callback receivers.

Connect your agent

When the session is ready, request access for one actor declared by its build. The returned binding contains short-lived world URLs, one world credential, expiry, and the exact operations that actor may call. Pass only that binding to your agent’s test configuration. Never give the agent a Cloud control credential. A world credential cannot manage projects, create other sessions, or access another actor’s capabilities.

Session controls

Reset changes world state, pending work, clock, and evidence generation together. It does not change repository source or silently select another build. Existing connection endpoints stay scoped to the same session, but SDK helpers may rotate the short-lived binding after a mutation. Unsafe controls require a stable idempotency key. If a request times out, do not assume it was undone. Recover the accepted asynchronous operation or repeat the exact request with the same key.
Starting a session, opening a Tool app, or manually calling a Tool does not mean an agent passed. Use a drill run when you need a verdict.