Skip to main content
This reference defines product terminology. API identifiers, error codes, and code fields remain untranslated. Interpret states by object: Session, Run, Runtime, and cloud resources have distinct state models.

Avoid ambiguous claims

  • “Task completed” requires the actual Run terminal state and deliverable checks, not just model text. “Cleanup completed” additionally requires remote confirmation.
  • “Connection works” must specify structural validation, account validation, enablement, or actual invocation. Ready does not prove permission for every operation.
  • “Recovery supported” must identify preserved files, conversation, processes, or memory and the exact provider/Harness evidence.
Prefer explicit actions: submit a new Run to the same Session, resume observing the original Run, or close and confirm cleanup. Do not use “restart” interchangeably for recovery, replay, recreation, and deletion.

Name the operation and the identity you retain

“Replay” needs an object: replaying durable events is observation; replaying an external write can repeat a side effect. “Retry” likewise needs the original request identity and a stated policy. See recovery.

Writing and translation convention

Keep Session, Run, Harness, Runtime and API field/state values unchanged in both languages. Chinese prose may introduce the explanatory term in this table, then use the API-facing name for precision. Use “Agent template” when discussing reusable configuration and “Agent revision” for its selected version; a bare “Agent” can otherwise mean the running model-driven engine. Do not translate waiting_authorization or waiting_approval into new wire values. UI labels may explain them, but actions come from the related connection, approval and Tool-call records. Likewise, unknown is a recorded uncertainty, not a translated synonym for failed. The state reference owns the exact state definitions; this glossary is the terminology entry point. This page summarizes the linked contracts and implementation explanations; it introduces no API or state values. Next: object relationships, capabilities and evidence.