CLI command
fleetdeck action
Submit any of the 18 action payloads and wait for its outcome.
Usage
bash
fleetdeck action SESSION JSON [REQUEST_ID]Example
fleetdeck action session_123 '{"type":"tap","x":0.5,"y":0.6}' tap-001Arguments
| Argument | Required | Description |
|---|---|---|
SESSION | required | Session to execute within, owned by this key. |
JSON | required | One command object, quoted as a single shell argument. The type field selects the action payload. |
REQUEST_ID | optional | Stable ID for this intended action. If omitted, the CLI generates one. Preserve it for recovery. |
Supply FLEETDECK_API_KEY through the environment. See environment configuration.
Choose one action type. Each payload has its own required fields.
Behavior
- JSON must be one strict command object. Unknown fields fail validation.
- Provide a stable request ID when recovery matters. If omitted, the client generates one.
- The client renews the session before and during longer calls, then stops its keepalive before returning.
Output and exit
Writes the action record. Exit 0 for completed, 1 for failed/unknown/cancelled, and 2 for queued/running. Exit 0 records driver completion, not proof of the intended app effect.
Example stdout
{
"id": "action_123",
"requestId": "tap-001",
"status": "completed",
"kind": "tap",
"createdAt": "2030-01-01T10:00:00.000Z",
"finishedAt": "2030-01-01T10:00:00.000Z",
"result": {
"status": "submitted",
"verified": false,
"instruction": "Take a fresh screenshot to verify the intended effect before the next decision"
}
}Response fields and API errors: Submit one command.
See all exit codes and error recovery.
