Skip to main content

ask-ava-streaming 

dci ask-ava-streaming [body]

Send a question to Ava and receive a streaming response via Server-Sent Events (SSE). The response streams back events containing the answer text, conversation ID, and message metadata.

Pass the request body as name: value arguments or pipe JSON on stdin — see Command structure.

Scripts and agents should use ask-ava-sync

This command returns the raw Server-Sent Events stream — answer text mixed with conversation and message metadata. For a clean JSON answer (plus conversationId and answerId when the conversation is persisted), use dci ask-ava-sync.

Examples​

# Ask Ava a question and watch the answer stream in.
dci ask-ava-streaming question: "Why did my GCP costs spike last week?"
# Continue an existing conversation.
dci ask-ava-streaming question: "Break that down by project", conversationId: <conversation-id>

Request​

Content-Type: application/json

FieldTypeRequiredDescription
questionstringyesThe question to ask Ava.
conversationIdstringOptional ID of an existing conversation to continue.
Raw JSON schema
{
  "type": "object",
  "properties": {
    "question": {
      "type": "string",
      "description": "The question to ask Ava."
    },
    "conversationId": {
      "type": "string",
      "description": "Optional ID of an existing conversation to continue."
    }
  },
  "required": [
    "question"
  ]
}

Output​

OK - SSE stream of Ava response events.

By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.

Returns: string

Raw JSON schema
{
  "type": "string"
}

Errors​

On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.

HTTP status to exit code mapping
HTTP statusExit codeError codeMeaning
40030VALIDATION_ERRORThe arguments or request body were rejected. Review the command's flags and payload.
40110AUTHENTICATION_FAILEDNot signed in, or the API token is invalid. Run dci login or check DCI_API_KEY.
40311PERMISSION_DENIEDThe DoiT user or the active customer context does not have access.
50040API_SERVER_ERRORThe API failed to process the request. Retryable; contact DoiT support if it persists.

Aliases: askavastreaming