CLI commands

The adsk-experiment tool is how you sign in, create experiments, and manage what gets published. You can either run the commands directly in your terminal, or use them in Claude Code with the ! prefix.

To check if you’ve installed the CLI, run adsk-experiment version — if it prints a version, you’re ready to sign in. If not, see Install the CLI.

CLI commands are constructed by combining the tool name (adsk-experiment), a command, optional flags, and arguments.

For example:

adsk-experiment env create --name myexp --industry con

This creates a new experiment called myexp in the con industry.

Command reference

Command	What it does
`login`	Sign in with your Autodesk account (usually opens your browser once)
`logout`	Sign out and remove the saved token from this machine
`whoami`	Show who you are signed in as and how many experiment slots you are using needs sign-in

Experiments

Command	What it does
`env create`	Create a new experiment and its GitHub repository needs sign-in
`env list`	List your experiments, soonest-to-archive first needs sign-in
`env get`	Show full detail on one experiment needs sign-in
`env select`	Choose which experiment later commands act on (saved locally)
`env renew`	Extend an experiment before it archives needs sign-in
`env archive`	Retire an experiment and turn off its link needs sign-in

For check status, extend, and archive with examples and Claude prompts, see Managing experiments.

Access and notifications

Command	What it does
`env sharing show`	See who can open an experiment’s link needs sign-in
`env sharing set`	Restrict a link to specific people needs sign-in
`env sharing open`	Make a link visible to anyone at Autodesk again needs sign-in
`env collaborators set`	Choose who gets email warnings before an experiment archives needs sign-in

Sharing controls who can view the published link. By default anyone at Autodesk with the link can open it after signing in.

Collaborators controls expiry email warnings only — not repository access or viewing access. The owner is always warned and does not need to be listed.

Settings and troubleshooting

adsk-experiment config get
adsk-experiment config set defaultIndustry con
adsk-experiment doctor
adsk-experiment update              # upgrade an existing install
adsk-experiment update --check      # see if a newer release exists

Settings live in ~/.adsk-experiment-ee/ on your machine. Run adsk-experiment config path to print the exact location.

Run doctor first when something is not working. It checks whether you are signed in, whether the CLI can reach the service, and which experiment is selected.

Useful options on any command

Option	Purpose
`--environment`, `-e`	Act on a specific experiment instead of the selected one
`--output json`, `-o json`	Machine-readable output (useful for scripts and agents)
`--verbose`, `-v`	More detail about what the CLI is doing

Resources and support

For additional help, join #experimental-environments on Slack.