Description
Conversations and Chat expose the platform's conversational workflow to terminal users and agents without reducing it to raw HTTP calls. dots conversations manages durable conversation records and turn dispatch, including stop and usage derivation. dots chat start launches the interactive chat flow using the same resolved credential and company context.
The workflow is designed for operators and coding agents. It uses the same authenticated, company-scoped service contracts as the rest of Dots, so terminal or protocol convenience never creates a second source of truth. Inputs are validated before or at the route boundary, and outputs preserve identifiers and structured details needed for a reliable next step.
Selling Points
- Keeps conversational work durable and addressable by stable identifiers.
- Supports non-interactive message dispatch for agents and interactive sessions for humans.
- Provides an explicit stop action for long-running or unwanted responses.
- Derives usage from stored conversations for later analysis and cost visibility.
- Shares authentication, formatting, and company selection with the rest of the CLI.
User Story
A developer creates a conversation for a support investigation, sends a focused message, inspects the stored response, and derives usage after the exchange. For follow-up exploration, they launch an interactive chat in the same company context. The result is a concrete, inspectable outcome that another person or automation can continue from without reconstructing hidden state.
Extension Surface
The surface is automatable: packages/cli/src/commands/conversations.ts and packages/cli/src/commands/chat.ts expose the supported conversation lifecycle. Model providers may be pluggable underneath, but users cannot register new CLI chat verbs. The rating reflects the most-open supported seam that is true for this capability, not a transitive implementation detail. The cited path is the operational proof: consumers can use the documented seam, while unsupported changes still require a core release.
Capabilities & Limits
- Capability: Conversation list, get, create, message, stop, and usage derivation.
- Capability: Interactive chat startup from the configured terminal context.
- Capability: Structured output for durable message and conversation records.
- Limit: Available models, tools, and response behavior remain governed by the platform's configured providers, permissions, and chat contracts.
The limit is intentional product truth rather than missing documentation. Calls also remain subject to authentication, tenant selection, schema validation, and the permissions enforced by the authoritative service.
Implementation Map
packages/cli/src/commands/conversations.tspackages/cli/src/commands/chat.tsdocs/cli/module-and-chat-commands.md