Skip to main content
Tolmo has two global flags. They let you override the active organization or switch profiles for a single invocation, without modifying your stored configuration in ~/.tolmo/ or your shell environment.

​
Flag reference

Because these are global, they may appear before or after the subcommand:
--json is not a global flag. Most commands that produce output accept it, but each declares it individually, so it has to come after the subcommand — tolmo findings list --json, never tolmo --json findings list. See JSON output below.

​
—org

Use --org to target a different organization for a single command without switching your active profile. This is useful for one-off queries or operations against an org you don’t work with regularly.
The flag accepts an organization slug, which you can find in your Tolmo dashboard or by running tolmo org list. It overrides the org embedded in the active profile for that invocation only — your default profile is unchanged afterward.

​
—profile

Use --profile to run a command using a specific named profile’s credentials and org context. This is the per-command equivalent of setting TOLMO_PROFILE in your shell.
The command above authenticates with the staging profile and targets whichever organization that profile is associated with. See Named Profiles for details on creating and managing profiles.

​
JSON output

Most commands that produce output accept --json to return raw JSON instead of a formatted table, which makes it straightforward to parse in scripts or pipe to other tools. It is declared per command rather than globally, so it must follow the subcommand. tolmo --json findings list fails with an unknown-flag error; tolmo findings list --json is correct. A command that produces no tabular output does not accept it at all.
Combine --json with jq to filter and transform results directly in the shell:
Always use --json when piping Tolmo output to other tools or scripts. The formatted table output is designed for human readability and may change between releases; the JSON schema is stable and machine-friendly.