Skip to main content
Use the eigenpal CLI to author workflows, push datasets and evaluators, start runs, inspect traces, manage Git-backed agents, and configure organization email servers. Most resources are files, so the same commands work for local development, CI, and agent-assisted editing.
Source is open at github.com/eigenpal/cli.

Authenticate to your organization

This opens a browser to create an API key and stores it locally. One key maps to one tenant, so the key decides which organization you are working in. Work across several organizations by keeping a named profile per org and switching between them:

Optional: install the skill

Install the EigenPal skill into a supported coding agent if you want it to work with EigenPal commands and file formats directly:
The command opens an interactive picker for Claude Code, Cursor, Codex, and other tools. See Install the EigenPal skill for the full list and non-interactive options.

Read documentation from an agent or terminal

Every CLI release bundles the complete public documentation, the OpenAPI contract, and detailed agent references generated from the platform schemas. No browser, authentication, or network connection is required:
docs read writes the full source document to stdout, while docs list and docs search support --json for agent tooling. The bundle is release-matched, so its syntax and command reference describe the installed CLI version.

Output and polling flags

  • Pipeable data goes to stdout. Status, progress, hints, and errors go to stderr.
  • --json emits the command’s primary payload as JSON. --select <path> emits one nested value as JSON and is preferable to a separate jq process for stable paths.
  • --wait belongs on commands that start work; it blocks until terminal state. --watch follows work that already exists. Use --interval <seconds> and --max-wait <seconds> where exposed; a timeout exits with code 2.
  • --format chooses an export or generated-code encoding. It is not a synonym for --json.
  • runs get --expand requests server-side detail sections. --include is command-specific, so read that command’s help rather than assuming shared values.
  • When --out is omitted, export commands stream to stdout. Help identifies whether a particular --out expects a file or directory.

Common ways to work

Build and score a dataset. Create examples with expected output, push evaluators, and run an experiment from the CLI.
See Build a dataset and Evaluate a workflow. Author and iterate on a workflow. Scaffold a project, push it, run it on a file, and read the trace to see what each step did. Edit workflow.yaml, push a new version, and compare experiments before deploying.
See Your first workflow. Work with a Git-backed agent. Clone the organization’s agent source, edit it, then commit, push, and release.
See Agents.

Command reference

Every command group has its own page with all subcommands, flags, and arguments.