Keep only the changes you understand.
Compare files and row values before and after each edit.
Eidos File · SQLite
Help me complete a structured-data task in a .eidos file. Set up Eidos first if needed.
Start by asking what I want to accomplish, which .eidos file to use—or whether to create one—and where any source data is located. Do not install software or modify files yet.
After I answer:
1. Run `eidos --version`.
2. If the command is unavailable, detect the operating system, explain that the official installer downloads and verifies the standalone Eidos CLI, and ask for confirmation before running one of these commands:
macOS or Linux:
curl -fsSL https://download.eidos.space/cli/install.sh | sh
Windows PowerShell:
irm https://download.eidos.space/cli/install.ps1 | iex
If the current shell has not refreshed its PATH, locate the installed binary and continue using its absolute path.
3. Initialize the matching Eidos Skill in the directory containing the file:
eidos skills init --space "<directory>"
Use `--global` only if I ask to enable it for all projects. If an existing Skill differs, do not overwrite it with `--force`; explain the conflict and ask me what to do.
Then read the generated `.agents/skills/eidos/SKILL.md` and the references it requires for this task before continuing in the current session.
4. Use structured `eidos --json` operations to inspect the exact file context and current revision. Do not mutate yet.
5. Propose the smallest useful change, limited to the relevant tables, fields, relations, views, or rows, and wait for my confirmation.
6. After confirmation, use typed Eidos operations with the expected revision. Never write raw SQLite or Eidos internal tables directly.
7. Validate the result and summarize the file changed, previous and current revisions, exact changes, and validation result.
If you cannot run shell commands or access the installer, show me the exact next command and stop. Tables, relations, formulas, and views live in one standard SQLite file. Use the same file from the desktop, browser, CLI, or an agent.
Open format · Single file · Standard SQLite
Eidos File · Views. Grid, Gallery, Kanban, and more use the same records. Change the view, not the data source.
Eidos File · Views
Grid, Gallery, Kanban, and more use the same records. Change the view, not the data source.
Drag or choose a view.
Eidos Lite · Desktop Spaces
Eidos Lite is the desktop client. Open any local folder as a Space and keep .eidos files beside your documents, images, code, and assets—nothing needs to move.
2 Eidos Files · ordinary files and folders · one local Space
Eidos Lite · Local version history
Eidos Lite keeps files, tables, and rows in one local history. Review changes from you or an agent, then keep or restore them.
Compare files and row values before and after each edit.
Inspect files, tables, and rows, or restore the whole Space without rewriting history.
Optional hosted services
Sync and Publish are optional. Your files stay usable locally without either service.
Compare pricing →01 · Eidos Sync · Invite-only Beta
Each computer edits its local file; Sync carries changes and history between them.
02 · Eidos Publish · Preview
Set the address and access; Forms can also collect responses into your file.
Eidos File · SQLite
Every .eidos file is SQLite. Standard SQLite tools can read its real tables today or years from now.
01 · Create a file and table
eidos create library.eidos \
--table library --label-field title \
--fields '[{"name":"title","type":"text"},{"name":"author","type":"text"}]' 02 · Add a row
eidos library.eidos rows add library \
--expected-revision 1 \
--values '{"title":"Chaos: Making a New Science","author":"James Gleick"}' 03 · Read it with SQLite
sqlite3 -header -column library.eidos \
'SELECT title, author FROM library;' SQLite output
title author
--------------------------- ------------
Chaos: Making a New Science James Gleick Start working local-first.
Download Eidos LiteFree locally · No account required