CliCLI guides

CLI global flags

JSON input, readable output, field flags and exit codes.

Every command uses the same argument parser. --help is local help; tools provides the session’s live schemas.

Shared flags

FlagBehavior
--help, -hShow help without requiring a session.
--textReadable output, not tool input.
--json @input.jsonRead JSON from a file.
--json -Read JSON from stdin.
--json '…'Literal JSON; shell quoting is required.
--field value or --field=valueSupply a schema field; kebab-case becomes camelCase.

File and stdin input

era records find --json @find.json

find.json:

{"type":"customer","q":"Demo","limit":10}

PowerShell:

Get-Content -Raw ./find.json | era records find --json -

Fields such as items, ids, where, lines, args and rows expect JSON. limit, minutes and depth expect numbers; draft, told and always expect true/false. Never supply a field twice. Arrays become items for create/update/run/approvals and ids for archive; other commands require an object.

Text input versus output

era overview --text
era memory save --text="Check delivery dates for Demo customers" --told

The first selects readable output; the second sends text to the tool and requests a memory write. Review the scope of a remembered instruction. Quote positional values containing spaces to keep them one argument.

Exit codes

CodeMeaning
0Success; still inspect body states such as awaiting approval.
2Invalid command or input.
3Missing/expired session.
4Permission or approval refusal.
5Failed or partial operation.
6Connection/protocol failure.
7Timeout.

Calls are not automatically retried. Separate completed items in partial results. --url, --token, --workspace and --version are not implemented as shared options; passing arbitrary fields does not turn them into sign-in configuration.

Command reference

Read command-specific fields alongside live tools schemas.

© 2026 Era. Era documentation. Something missing or wrong? Write to us: [email protected]