> ## Documentation Index > Fetch the complete documentation index at: https://vida.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # Read or wait for a Computer Task result > Reads an existing Computer Task belonging to the account in the path. Never creates, reruns, or cancels work. Uses the same requester and account permissions as Computer Task execution; Tasks belonging to another account and non-computer Tasks return 404. waitSeconds is an integer from 0 to 60, default 0. Zero performs one inspection, bounded to 10 seconds for result reads, without polling. Positive values wait up to that many seconds after the initial Task lookup. Execution completion plus a five-second replication grace period gates selection of the latest replicated assistant text in the execution window. Messages do not have a definitive final-answer marker. Tool, reasoning, system, and user entries are not answers. No direct computer-session reads or new persisted state are used. HTTP 200 means output is ready or the Task errored/was canceled; inspect state, resultStatus, and error. HTTP 202 means execution or replicated output is pending, even if state is finished. Missing/expired replicated output remains pending. Read the linked chat with the existing Tasks API chatRef when investigating. A client disconnect only ends this wait, not the Task. ## OpenAPI ````yaml get /api/v2/computer/accounts/{targetAccountId}/tasks/{taskId}/result openapi: 3.0.0 info: version: 2.0.0 title: Vida API description: Vida API Documentation servers: - url: https://api.vida.dev description: Vida Production variables: baseUrl: default: api.vida.dev description: Production API Root security: [] tags: - name: Agents - name: Apps description: Install Vida apps and use their enabled integration functions. - name: Integrations description: Configure Vader integrations. - name: Inbound Email description: Control which senders may create inbound email work for an Agent. - name: Features description: Inspect capabilities available within an account hierarchy. - name: Conversation Logs description: Query conversation activity and calculate account-level metrics. - name: Computer Agents description: Set up, configure, inspect, and manage Vida Computer Agents. - name: Computer Agent Sessions description: View and reset Computer Agent sessions. - name: Accounts - name: Agent Templates description: Create, manage, and apply reusable Agent configurations. paths: /api/v2/computer/accounts/{targetAccountId}/tasks/{taskId}/result: get: tags: - Computer Agents summary: Read or wait for a Computer Task result description: > Reads an existing Computer Task belonging to the account in the path. Never creates, reruns, or cancels work. Uses the same requester and account permissions as Computer Task execution; Tasks belonging to another account and non-computer Tasks return 404. waitSeconds is an integer from 0 to 60, default 0. Zero performs one inspection, bounded to 10 seconds for result reads, without polling. Positive values wait up to that many seconds after the initial Task lookup. Execution completion plus a five-second replication grace period gates selection of the latest replicated assistant text in the execution window. Messages do not have a definitive final-answer marker. Tool, reasoning, system, and user entries are not answers. No direct computer-session reads or new persisted state are used. HTTP 200 means output is ready or the Task errored/was canceled; inspect state, resultStatus, and error. HTTP 202 means execution or replicated output is pending, even if state is finished. Missing/expired replicated output remains pending. Read the linked chat with the existing Tasks API chatRef when investigating. A client disconnect only ends this wait, not the Task. operationId: tasksGetRecordResult parameters: - name: targetAccountId in: path required: true description: Selected Computer Agent account. schema: type: integer minimum: 1 - name: taskId in: path required: true description: Existing Computer Task ID. schema: type: string maxLength: 100 - name: waitSeconds in: query required: false description: Maximum additional wait after the initial Task lookup. schema: type: integer minimum: 0 maximum: 60 default: 0 responses: '200': description: Reply ready, or Task errored or canceled content: application/json: schema: type: object properties: success: type: boolean example: true allOf: - $ref: '#/components/schemas/ComputerTaskResult' '202': description: Execution or reply replication remains pending content: application/json: schema: type: object properties: success: type: boolean example: true allOf: - $ref: '#/components/schemas/ComputerTaskResult' '400': description: Invalid waitSeconds or route parameters '401': description: Authentication required or target account inaccessible '403': description: Selected account is outside the requester permissions '404': description: Computer Task not found in the selected account security: - apiKeyAuth: [] components: schemas: ComputerTaskResult: type: object required: - success - taskId - state - resultStatus - output - error - resultRef properties: success: type: boolean description: Whether the API request succeeded, not whether the Task succeeded. taskId: type: string description: Existing Task ID. state: type: string enum: - pending - processing - running - finished - errored - canceled resultStatus: type: string enum: - pending - ready - unavailable description: >- Response-only readiness. Finished Tasks remain pending while their reply has not replicated. Unavailable indicates an errored or canceled Task. output: type: object nullable: true required: - text - truncated properties: text: type: string maxLength: 20000 description: >- Latest replicated assistant reply in the completed Task execution window, after a five-second replication grace period. truncated: type: boolean description: True when the returned text exceeded 20,000 characters. error: type: object nullable: true required: - code - message properties: code: type: string enum: - task_failed - task_canceled message: type: string resultRef: type: object required: - href properties: href: type: string description: >- Relative GET result URL. Authenticate with the normal token query parameter. securitySchemes: apiKeyAuth: type: apiKey in: query name: token description: Vida API Token ````