Grida Agent from the CLI
The source-built native CLI supports grida agent run for scripts and
grida agent serve --stdio for Agent Client Protocol clients. Select a Gateway
model and, when needed, a funding organization. Use a private state directory
to keep your chats across launches.
Pass --initial-title "Draft comparison" to grida agent run to give the
chat a provisional title when its first message is accepted. ACP clients
can read the saved title with session/list for that workspace.
With grida agent run --questions, an answer-dependent question returns
input_required and exit code 6. The JSON Lines result identifies the turn
and question. An optional question can expire when the agent finishes its
work. Interactive clients using grida agent serve --stdio can answer an open
question and read running and input-needed indicators through the
workspace chat catalog.
For setup, commands, exit codes, and the available client controls, see Connect an agent client.
Run a local ACP peer
On macOS and Linux, grida agent run-external --profile FILE --state-dir DIRECTORY
gives one text prompt to a reviewed ACP v1 stdio peer. Supply an existing
private state directory and a matching native sandbox helper. The private
profile selects a system executable under administrator control, its digest,
the helper's path and digest, and the workspace and runtime paths. Linux
also requires compatible bubblewrap. The peer can read the selected workspace
and runs with networking denied.
Supply --prompt or close stdin after sending the text. Stdout carries JSON
Lines for acceptance and the final outcome, including the local receipt ID.
Each invocation starts a fresh peer process. See the
confined peer profile and recovery reference.