---
title: "Work with files from the terminal | Eidos Docs"
description: "Inspect a file, query records, and choose the command for your task."
source: "https://docs.eidos.space/cli/"
lang: "en"
---

# Work with files from the terminal

The `eidos` CLI reads and writes local `.eidos` files. It does not need Eidos Lite or a background service. Start with the [installation guide](https://docs.eidos.space/getting-started/cli/) if the command is not installed.

## Inspect, query, check

For an existing `tracker.eidos` file with a Tasks table:

Terminal window

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

The first command describes the file. The second returns up to 50 records. The third checks the file at the full validation level. Use your own file path and table name.

## Choose a command group

| Task                                       | Command group |
| ------------------------------------------ | ------------- |
| Create, inspect, check, or repair a file   | eidos file    |
| Manage tables, fields, and views           | eidos schema  |
| Query or change records and attachments    | eidos data    |
| Open a local web editor                    | eidos serve   |
| Sign in, publish, or collect submissions   | eidos cloud   |
| Manage local plugin packages               | eidos plugin  |
| Upgrade the CLI or install its agent skill | eidos self    |

Run `eidos --help` to list commands. Add `--help` to a command group to inspect its options.

## Return data to a script

Use `--json` for machine-readable output:

Terminal window

```bash
eidos --json data query tracker.eidos Tasks --fields Title,Status --limit 50
```

Check the exit status before using the result. For writes, [read context, apply with a revision check, then check the file](https://docs.eidos.space/cli/automation-workflow/). Do not build a script around the human-readable output.

## Set up an agent

Install the bundled Eidos Skill in the current project:

Terminal window

```bash
eidos self skill init
```

Use `--global` for the current user, or `--space <DIR>` for another project. The initializer refuses to replace edited skill files unless you explicitly use `--force`. Start a new agent task after installation.

## Add a local plugin

Terminal window

```bash
eidos plugin list
eidos plugin install ./my-plugin.eidos-plugin
```

Use `eidos plugin remove <PLUGIN_ID>` to remove an installed package. To build one, follow the [text-reader tutorial](https://docs.eidos.space/plugins/guide/).

## Continue with a task

- [Automate a safe write](https://docs.eidos.space/cli/automation-workflow/).
- [Open the local editor](https://docs.eidos.space/cli/serve/).
- [Publish a hosted copy](https://docs.eidos.space/cli/publish/).

The CLI manages files. Use Eidos Lite for Space navigation, local history, and Sync.
