era terminal command: usage and complete list

era accesses business records, files and memory from the terminal. Era Desktop writes it into the chat workspace's .era/bin and adds it to the engine PATH. Do not assume it is a permanent login command in every system terminal.

Before you start

The era command is prepared for the chat session. There is no persistent era login or global system installation flow.

CLI overview

Steps and focused answers.

MCP and CLI

Steps and focused answers.

Start

era --help
era tools
era overview --text
era records find customer --q "Demo" --limit 20

era tools lists currently permitted tools and schemas. The server enforces roles, enabled modules, sources and approvals. Web users can perform the same work through Era chat.

Complete command list

Command	Job
`overview`	Current business state.
`records find/create/update/archive`	Find/count, create, change, remove.
`message send`	Message or private draft.
`document create/issue`	Draft or issue/send invoices/quotes.
`meeting schedule`	Calendar meeting.
`numbers`	Business metrics and periods.
`free-times`	Available booking times.
`site edit/publish`	Draft changes and approved publication.
`file save/get/import`	Save to Era Files, download, import rows.
`open`	Open record/list/file/page beside chat.
`memory save/forget`	Remember or forget.
`brain search/graph`	Sourced knowledge and relationships.
`skill save`	Propose a procedure.
`approvals decide`	Apply the person's approval/decline decision.
`work status`	Background-job result.
`turn report`	Actual writes in this turn.
`run`	Any permitted action by exact name.
`places search`	Google Maps businesses.
`visuals make`	Generate/edit images on supported engines.
`pc act`	Remote computer work; may be absent locally.
`tools`	Live permitted catalogue.

Prefix every row with era. The generated CLI reference and MCP schemas detail inputs.

Input rules

Use flat --field value flags; kebab-case names become camelCase. JSON supports --json @input.json, --json '{"type":"customer"}' or stdin with --json -. Files/stdin reduce shell quoting mistakes. Structured fields such as items, ids, where, lines and args expect JSON. Numeric fields accept numbers; draft, told and always accept true/false.

era records create customer --json @customers.json
era brain search "delivery terms"
era brain graph "Demo Company"
era file save "./report.xlsx"
era file get --file-id "FILE_ID"
era file import "./demo.csv" --target table --title "Demo"
era run --action crm.update_lead --json @update.json
era turn report --text

JSON arrays map to items for create/update/run/approvals and ids for archive. Some commands accept one positional value: record type, path, query, surface or job ID. Bare --text selects readable output; supply a tool's text field through JSON or --text="message". Default output is compact JSON.

Move local files into Era Files

file save resolves and uploads paths; large files can return a one-time upload command. Complete it and use the returned ID. file get returns a short-lived download URL/command; execute it to download. file import saves first and imports to crm / table / dashboard; complete any upload command first. Files appear in Files → Era on web.

Exit codes and retries

Code	Meaning
0	Success
2	Invalid arguments/input
3	Missing/expired session
4	Permission/approval refusal
5	Failed/partial operation
6	Connection/protocol failure
7	Timeout

Calls are never retried automatically: a disconnected write may have succeeded. Inspect records or turn report before repeating. Standalone source execution supports Node 22.19+ or Bun and requires an existing chat's ERA_CLI_URL/ERA_CLI_TOKEN; it does not read saved device tokens. These are secrets: never copy their values into documentation/history.

era terminal command: usage and complete listshots/desktop-terminal

era terminal command: usage and complete list