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 syntax for new workflows:

Terminal window
eidos inspect tracker.eidos
eidos context tracker.eidos Tasks --fields Title,Status --limit 50
eidos 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 context 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 create, check, dev, and pack to build an offline file editor for Eidos Lite. Install Eidos CLI and Node.js, then create a project and install its dependencies. 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 skills init
# Install for the current user and all projects.
eidos skills init --global

Use eidos skills 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 rows upsert, and atomic mixed rows mutate batches, plus safe File-field attachment import and verification.