Skip to content

Eidos CLI

The eidos CLI works directly with local .eidos files. It does not require Eidos Lite or a background service.

Use command-first namespaced syntax:

Terminal window
eidos file inspect tracker.eidos
eidos data query tracker.eidos Tasks --fields Title,Status --limit 50
eidos file validate tracker.eidos --level full

Commands print readable output by default. Add --json when a script or Agent needs the stable machine-readable result:

Terminal window
eidos --json data query tracker.eidos Tasks --fields Title,Status --limit 50

Use eidos --help to list commands, and eidos <command> --help for the options of one command.

Use eidos plugin to inspect and manage locally installed plugins:

Terminal window
eidos plugin list
eidos plugin install ./my-plugin.eidos-plugin
eidos plugin remove com.example.plugin

To create and package new plugins, use @eidos.space/plugin-tools:

Terminal window
npx @eidos.space/plugin-tools create my-plugin
npx @eidos.space/plugin-tools check
npx @eidos.space/plugin-tools pack

Follow the plugin development guide for a complete CSV editor walkthrough.

The CLI bundles the Eidos Skill, so an Agent setup does not need Node.js, npm, or npx:

Terminal window
# Install in the current Space/project.
eidos self skill init
# Install for the current user and all projects.
eidos self skill init --global

Use eidos self skill init --space <DIR> for another Space. The command writes the standard .agents/skills/eidos layout, is safe to repeat, and refuses to replace locally edited files unless --force is explicit. Start a new Agent task after initialization.

The CLI manages Eidos Files, not Eidos Lite Spaces or local history. Use Eidos Lite when you need folder navigation, Space history, or Sync.

For Agent workflows, the safe automation guide also covers intent commands for schema changes, Runtime-backed Formula/Lookup Fields, business-key mutations, and atomic mixed mutation batches, plus safe File-field attachment import and verification.