Skip to main content
A project groups your application’s scenarios, Tool definitions, datasets, and runs. An environment selects the execution and reporting scope within that project. Every project created through Firedrill includes a Default environment.

​
Select from the CLI

Init writes your selected project/environment pair to firedrill.config.json. The context read confirms current identity and scope without starting a simulation. To select an existing pair explicitly:
Use the exact pair returned by projects list. If an existing configuration differs, the CLI refuses to overwrite it; review that file or choose another --config path deliberately.

​
Create noninteractively

Authenticate first or provide a scoped machine credential. Keep the same name and key after an uncertain creation response to avoid duplicates.

​
Scope in the web app

The top bar selects project and environment for reports, saved scenarios, and Tools. A resource link still needs current authorization. If your account has no project, the app shows setup instructions instead of another account’s examples.

​
Tool builds

A Tool build pins behavior and schemas. Most users select a catalog release and receive the matching build/dataset identities automatically. You only publish source when authoring a private Tool. You do not need to publish your agent repository to Firedrill to run a simulation.