Work with AI in Chat

Prepare workspace permissions

Open Chat using your current workspace identity. Built-in Chat does not require a separate MCP key.

A workspace owner or administrator enables Chat and chooses device groups and operations in Chat permissions. Effective access is limited by membership, Chat configuration and device capabilities together. Enabling an option does not override access the member lacks.

Describe a clear task

Select an available model and specify the device, action and completion criteria. Start with a small task whose result you can check, such as:

Check whether my office computer is online and list its system information. Do not change any settings yet.

Or, with desktop capability and permission available:

Open the application on the specified device, inspect the current page, and describe its state. Wait for further instructions.

Avoid vague requests that require the model to guess the device, directory or whether changes should be saved.

Follow progress and confirmations

Read tool results and task status in Chat. If the task waits for confirmation, review the proposed action and scope before accepting or rejecting. Not every tool call requires an individual confirmation; the permissions configured in advance still apply.

For computer tasks with task controls, use Pause, Resume or Stop. Wait until the interface confirms it has paused or stopped before opening the target desktop yourself. Stopping does not undo changes already completed.

Verify outcomes and usage

Ask the model which steps completed, failed or remain unfinished. Inspect actual file contents after edits and the final screen after desktop work. A success message alone is not verification.

Model calls use workspace balance under the current billing configuration. Check available balance and plans in Balance and Subscription. If Chat cannot start, check model availability, balance, Chat permissions and target connectivity.

Use an external AI client

External clients have separate keys and approval settings. They do not automatically inherit your browser Chat session. Follow MCP setup for dedicated access, and close any remote sessions they open when the task ends.