Use the CLI with coding agents
Reach business data from Claude Code and Codex terminals.
Era Desktop adds era to supported engine sessions. It also prepares the native era-cli skill for Claude Code and Codex; business records use the same authorized door.
Prerequisites
Pair Desktop, make the provider engine ready and open an Era chat. Its terminal must carry the session environment. For an independent agent opened outside Era, MCP setup may fit better.
Discover access
Inspect your available schemas with era tools.
Read Demo customers and prepare a summary only; do not change records.Assess the result
era records find customer --q "Demo" --limit 20
era brain search "delivery terms"Compare search results and memory sources. Local repository instructions do not widen business access.
Save the output
Write the summary to local demo-report.csv, then use era file save
to save it to Era Files. Report the returned file ID and actual outcome.Tasks involving writes
Have bulk input prepared in a JSON file and inspect scope before submitting it. For money, messages, publishing and removal, wait for Era’s approval outcome. “Waiting for approval” is not completion; the agent cannot make the person’s decision itself.
Two separate permissions
The local engine governs files/terminal access; your Era role governs business access. Letting an engine read a file does not grant Finance write access. Inspect the turn report after interruption; calls are not automatically retried.