Manage Edge Delta from the Terminal with the edx CLI
Install and authenticate edx, the Edge Delta CLI, to search logs, query metrics, manage pipelines, and work with AI teammates from your terminal.
4 minute read
Overview
edx is the Edge Delta command line interface. It provides terminal access to the full platform: Telemetry Pipelines (pipeline configurations, fleet management, live capture), observability data (logs, patterns, metrics, traces, events, monitors, dashboards), and AI Team (issues, threads, channels, teammates, connectors). A raw API escape hatch covers any endpoint that does not have a dedicated command.
edx is a single binary designed for humans, CI automation, and AI coding agents alike. Output is JSON by default, so results pipe directly into jq or into an AI agent’s context, and every command supports table, CSV, YAML, and raw output for human-friendly summaries.
The following diagram shows how edx fits between your terminal, automation, or AI agent and the Edge Delta platform:
graph LR A[Terminal] --> D[edx CLI] B[CI and automation] --> D C[AI coding agents] --> D D --> E[Edge Delta API] E --> F[Logs, metrics, traces, events] E --> G[Pipelines and fleets] E --> H[AI Team]
Install
Install edx with Homebrew on macOS or Linux:
brew install edgedelta/tap/edx
Alternatively, install with the Go toolchain:
go install github.com/edgedelta/edx@latest
Verify the installation:
edx version
The source is available at github.com/edgedelta/edx.
Authenticate
edx supports two authentication methods. Pick the one that matches how you run it:
- OAuth (interactive use):
edx auth loginopens a browser login. The access token refreshes automatically and your organization ID is derived from the token. - API token (CI and automation): Create a token in the Edge Delta web app under Admin > My Organization > API Tokens (see Create an API Token). The Read & Write permission preset is recommended for
edx. After you create the token, the Use this token section’s edx CLI tab shows a ready-made login command with the token and organization ID filled in:
edx auth login --token YOUR_API_TOKEN --org-id YOUR_ORG_ID
Credentials are saved to a profile in ~/.config/edx/config.yaml. Confirm they work with:
edx auth status
Profiles
Profiles let you switch between organizations or environments. Create a named profile with edx auth login --profile staging-org ..., list profiles with edx auth list (the default is marked with *), set the default with edx auth use <profile>, and target a profile for a single command with --profile <name>.
Environment variables
Environment variables override values from the config file, which makes them useful in CI:
| Variable | Purpose |
|---|---|
ED_API_TOKEN | API token used to authenticate requests |
ED_ORG_ID | Organization ID |
ED_ENV | Environment: prod (default) or staging; selects the API and AI service hosts together |
EDX_PROFILE | Profile to use when --profile is not given |
EDX_CONFIG | Path override for the config file |
EDX_NO_UPDATE_CHECK | Set to 1 to disable the passive update notice |
Output formats
Every command accepts the same output flags:
| Flag | Purpose |
|---|---|
-o, --output | json (default), yaml, table, csv, or raw |
--columns | Dot-path column selection for table and csv output, for example --columns id,tag,status |
For example, list pipelines as a compact table:
edx pipelines list --output table --columns id,tag,fleet_type,status
Conventions
These conventions apply across commands:
- Time ranges: Use
--lookbackwith Go durations (15m,1h,24h), or--fromand--towith ISO 8601 timestamps (2006-01-02T15:04:05.000Z). - Pagination: Search responses include cursors; pass
--cursorto continue. The default search limit is 20; raise it with--limit(maximum 1000). - Confirmations: Destructive commands such as
deployanddeleteprompt before running; add--yesin non-interactive contexts. - Queries: Search commands filter with Common Query Language (CQL) using dot-path fields, for example
service.name:"api". Discover valid fields and values withedx facets keysandedx facets optionsbefore writing a query.
Install AI agent skills
edx skills installs Edge Delta skills into AI coding assistants (Claude Code, Cursor, Codex, and OpenCode) so agents know how to drive edx for log search, pipeline management, incident investigation, and more. The skills are embedded in the binary, so installed skills always match your edx version:
edx skills install # auto-detects your assistant
edx skills install claude # or target a platform explicitly
Add --project to install into the current repository instead of your home directory.
Update
Update to the latest release with:
edx update
Homebrew installations are upgraded through brew automatically. On interactive terminals, edx prints a one-line notice when a newer version is available (at most one check per day); set EDX_NO_UPDATE_CHECK=1 to disable it.
Troubleshooting
| Problem | Fix |
|---|---|
401 Invalid authentication token | Re-run edx auth login with a valid token and matching organization ID |
404 on a path | Check the organization ID; try edx api with the full /v1 path |
| Empty search results | Widen --lookback; verify field names and values with edx facets options |
| Timeout on large queries | Narrow the time range or add --timeout 120s |
See Also
- edx Command Reference - Every command, grouped by domain, with key flags.
- Common Query Language (CQL) - The query syntax used by search commands.
- API Reference - The REST API that
edxwraps, for direct HTTP access. - Edge Delta MCP Server - Give MCP-capable AI clients direct tool access to Edge Delta.