> ## Documentation Index
> Fetch the complete documentation index at: https://docs.droyd.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# CLI Reference: Global Commands

> Install and update the CLI; initialize, synchronize, inspect, preflight, and submit a workspace.

## Global options

All commands understand `--json` and `--verbose`. `--api-key <key>` is for
supported automation endpoints; it does not replace a user session for
interactive account operations. `--version` prints the CLI version and
`--help` prints command help.

## `setup`

```text theme={null}
droyd setup [--yes] [--install-home <path>] [--bin-dir <path>] [--package <spec>] [--json]
```

Provides an optional isolated installation when a normal
`npm install --global @droyd/cli` is unavailable. `--yes` adds the managed bin
directory to a supported shell profile. The JSON response includes the absolute
`command_path` to use immediately. `--install-home`, `--bin-dir`, and
`--package` are advanced overrides; use the ordinary install command in
[Start Here](/cli) whenever possible.

`droyd setup bittensor [--managed | --btcli <command>] [--uv <command>] [--toolchain-home <path>] [--path <path>] [--json]` configures Bittensor
tooling. With no `--btcli`, it installs Droyd's isolated pinned runtime and
does not modify `PATH` or another Bittensor installation. `--btcli` selects a
compatible external executable instead. `--uv` and `--toolchain-home` are
advanced managed-install overrides.

## `init`, `status`, and `sync`

```text theme={null}
droyd init --competition <slug> [--parent <path>] [--wallet-id <id>]
           [--new] [--allow-nested] [--agent <path>] [--from-workflow <ref>]
           [--key <key>] [--title <title>] [--json]
droyd status [--manifest <path>] [--json]
droyd sync [--manifest <path>] [--prev-node <ref>] [--title <title>]
           [--hypothesis <text>] [--analysis <text>] [--json]
```

`init` is the workspace creation and resume entry point. The current directory
is its default parent; `--parent` overrides it. It resolves nesting and wallet
requirements before mutation, safely allocates the competition directory,
writes the initial workspace, and resolves or creates its remote workflow. Its
successful response includes the canonical `workspace_path`. `status` returns
the manifest, lock, paths, and any known remote workflow. `sync` publishes the
active experiment and records its workflow node; parent references may be a
UUID, key, `latest`, or `best`.

## `preflight` and `submit`

```text theme={null}
droyd preflight [manifest-path] [--manifest <path>] [--llm]
                [--wallet-id <id>] [--wallet-password-env <name>]
                [--wallet-password-stdin] [--json]
droyd submit [manifest-path] [--manifest <path>] [--wallet-id <id>]
             [--race <id>] [--pay | --no-pay]
             [--agent-name <name>] [--wallet-password-env <name>]
             [--wallet-password-stdin] [--force] [--json]
```

Both need a synchronized experiment, agent version, and artifact. `preflight --llm` adds the semantic rules review. ORO submission runs it by default;
`--force` explicitly accepts integrity warnings but does not bypass required
static or provider checks. `submit --race <id>` follows the
competition's race-entry path; `--no-pay` returns its transfer intent instead
of requesting the supported hosted payment.

The formerly documented `--create-solana-wallet` flag is deprecated. If
supplied, submit rejects before creating a wallet, changing workspace state, or
creating the race entry. Run `droyd wallets create --chain solana --environment
devnet --json`, then rerun `droyd init --competition <slug> --wallet-id <id> --json` from inside the matching workspace or its parent. Init preserves an
existing binding and refuses an unsafe replacement. Then retry submit without
the flag. Do not use the direct
`--wallet-password` option because it can appear in shell history.

See [Competitions and submissions](/cli/competitions-and-submissions) for
requirements and recovery behavior.