The official CLI for the Dedalus REST API.
It is generated with Stainless.
brew install dedalus-labs/tap/dedalusTo test or install the CLI locally, you need Go version 1.22 or later installed.
go install 'github.com/dedalus-labs/dedalus-cli/cmd/dedalus@latest'Once you have run go install, the binary is placed in your Go bin directory:
- Default location:
$HOME/go/bin(or$GOPATH/binif GOPATH is set) - Check your path: Run
go env GOPATHto see the base directory
If commands aren't found after installation, add the Go bin directory to your PATH:
# Add to your shell profile (.zshrc, .bashrc, etc.)
export PATH="$PATH:$(go env GOPATH)/bin"dedalus updateTo check the latest available release without installing it:
dedalus update --checkThe updater respects how the CLI was installed. Homebrew installs delegate to
brew upgrade, macOS/Linux curl installs rerun the install script for the
current executable directory, and Windows installs print the PowerShell installer
command because Windows cannot replace the running dedalus.exe process.
After cloning the git repository for this project, you can use the
scripts/run script to run the tool locally:
./scripts/run args...The CLI follows a resource-based command structure:
dedalus [resource] <command> [flags...]dedalus machines create \
--api-key 'My API Key' \
--memory-mib 2048 \
--storage-gib 10 \
--vcpu 1For details about specific commands, use the --help flag.
| Environment variable | Description | Required | Default value |
|---|---|---|---|
DEDALUS_API_KEY |
Dedalus API key sent as Authorization Bearer. | no | null |
DEDALUS_X_API_KEY |
Dedalus API key sent as x-api-key header. | no | null |
DEDALUS_ORG_ID |
Organization ID header for all DCS requests. | no | null |
--api-key- Dedalus API key sent as Authorization Bearer. (can also be set withDEDALUS_API_KEYenv var)--x-api-key- Dedalus API key sent as x-api-key header. (can also be set withDEDALUS_X_API_KEYenv var)--dedalus-org-id- Organization ID header for all DCS requests. (can also be set withDEDALUS_ORG_IDenv var)--help- Show command line usage--debug- Enable debug logging (includes HTTP request/response details)--version,-v- Show the CLI version--base-url- Use a custom API backend URL--format- Change the output format (auto,explore,json,jsonl,pretty,raw,yaml)--format-error- Change the output format for errors (auto,explore,json,jsonl,pretty,raw,yaml)--transform- Transform the data output using GJSON syntax--transform-error- Transform the error output using GJSON syntax
To pass files to your API, you can use the @myfile.ext syntax:
dedalus <command> --arg @abe.jpgFiles can also be passed inside JSON or YAML blobs:
dedalus <command> --arg '{image: "@abe.jpg"}'
# Equivalent:
dedalus <command> <<YAML
arg:
image: "@abe.jpg"
YAMLIf you need to pass a string literal that begins with an @ sign, you can
escape the @ sign to avoid accidentally passing a file.
dedalus <command> --username '\@abe'For JSON endpoints, the CLI tool does filetype sniffing to determine whether the
file contents should be sent as a string literal (for plain text files) or as a
base64-encoded string literal (for binary files). If you need to explicitly send
the file as either plain text or base64-encoded data, you can use
@file://myfile.txt (for string encoding) or @data://myfile.dat (for
base64-encoding). Note that absolute paths will begin with @file:// or
@data://, followed by a third / (for example, @file:///tmp/file.txt).
dedalus <command> --arg @data://file.txtYou can link the CLI against a different version of the Dedalus Go SDK
for development purposes using the ./scripts/link script.
To link to a specific version from a repository (version can be a branch, git tag, or commit hash):
./scripts/link github.com/org/repo@versionTo link to a local copy of the SDK:
./scripts/link ../path/to/dedalus-goIf you run the link script without any arguments, it will default to ../dedalus-go.