Conversations
Conversations are the main entry point for collaborating with Agents in a workspace. A conversation inherits the capabilities and context available in the current space, and can keep accumulating the process and results around a Task.
Version: 6.1. Intended for: users who collaborate with Agents in a workspace.
Search keywords: Conversation, Session, conversation, new conversation, history, linked Task.
Start a conversation in a workspace
Go to Workspaces > Conversations to start a conversation in the current space. You can also select an Agent you've created to start a chat.
First confirm the current space, then click New chat and select an available Agent. To continue the same piece of work, open an existing conversation from the current space's conversation list. To switch to a separate goal, create a new conversation so that unrelated history isn't mixed in.
In the input box, describe your goal, the materials you already have, and the expected form of the results, confirm the capabilities and context, and then send. Press Enter to send and Shift+Enter for a new line. When you upload attachments, wait until the files are ready before sending.
Regular conversations in a shared space are still isolated per person. Other members can't see your regular conversations just because they've joined the same space, and linking a Task doesn't mean sharing the full conversation. When the team needs to reuse results, you can publish files to space assets. For details, see "Save results and organize conversations" on this page.
To adjust space capabilities or member permissions, see Create a space.
Select the model, capabilities, and execution mode
Common space capabilities and the Agent configuration provide a starting point. Before you send, confirm the model, MCP, Skills, and knowledge bases used this time in the conversation configuration area. The adjustable and required items are subject to the current interface.
- Model: Select an available model for this run. If the model is unavailable and the interface lets you select a replacement, switch to it and try again.
- MCP: Select the tool and service connections the task needs.
- Skill: Select the methods and procedures needed to complete the task. Capabilities required by the Agent may not be removable in the conversation.
- Knowledge base: Select the knowledge bases to search this time. Knowledge base selection isn't the same setting as data scopes such as business projects and DataOps spaces.
Execution mode: If the interface offers a choice of execution modes, choose a currently available mode based on the task. Fast suits lightweight tasks. Whether attachments, business context, and other capabilities are supported depends on the prompt for the current mode. If the prompt says that the current content isn't supported, adjust your input or switch modes as prompted.
Permission boundaries: Selecting a capability doesn't grant you all data or operation permissions. The actual available scope is constrained by the current account, space, resources, and tool authorizations, and switching Agents or models doesn't automatically expand permissions. To add tools, methods, materials, or models, see Capability Center.
In Capability Center > Agent, you can save frequently used model, MCP, Skill, name, description, and prompt configurations so that you can quickly start chats in the same business scenarios.
Add context and link Tasks
Add materials for this task: Based on the question, select the relevant business projects, community spaces, or DataOps spaces, and as needed, select knowledge bases, upload local files, or reference assets in the current space. Before you send, confirm the selected scope and the file status. For materials that can't be accessed or aren't ready yet, handle the on-page prompts first.
Uploading or referencing files provides materials for the current conversation. It doesn't share the entire conversation with space members. To maintain the space's long-term background and reusable experience, see Space Memory. Don't confuse message history with Space Memory that's already in effect.
Hold conversations around Tasks: In the conversation's Task entry, search for and select a Task in the current space. After linking, you can click the Task name to view its details, and you can switch Tasks or unlink the Task while the conversation is idle.
The link target must be an unarchived Task for which you're the owner or a collaborator. Having only space management permissions doesn't make you eligible to link the Task to a conversation. If the Task is archived, restore it first with the required permissions, and then link it.
Switching restrictions: While a conversation is queued, running, or waiting for a user's answer, you can't switch or unlink the current Task. Handle the current run and wait until the conversation is idle again before you do so. Switching or unlinking doesn't clear the existing conversation history, so don't use it as a way to isolate old task content.
To create Tasks, assign owners, maintain progress, or manage result links, see Tasks. This page only explains how to use Task context in conversations.
Follow up on runs and handle confirmations
After you send, judge the progress from the conversation status, the replies, and the tool run records. Seeing a queued or waiting-for-confirmation state doesn't mean that the run failed.
- Queued: Waiting for execution resources. You don't need to submit the same task again.
- Running: View the replies and tool progress. To end the current run, use the Stop operation available in the interface.
- Confirmation needed: Read the question and options, and submit your answer in the confirmation area. After you submit the answer, the task may continue to queue for resources.
- Finished or error: First check the completed results, and then add information to continue. If the interface offers retry or regenerate, confirm the conditions before you use it to avoid repeating work that's already done.
Stopping the current run doesn't undo external operations that were already completed. If sending, creating, or modifying business data is involved, check the actual results before you continue.
Automation run conversations: While an automation task is running, you can view its progress, but you can't type in or stop that conversation for now. To view schedules or run records, or to set up a fixed task to run periodically, go to Automations.
Save results and organize conversations
View results: View the generated content in the reply or file area. Files that support preview can be opened directly. If a file can't be previewed online, download it to view it. If a file is shown as unavailable or changed, reopen it and confirm its current status.
Publish to space assets: To reuse a file in the space, select Publish to Space Assets in the conversation outputs, confirm the target directory, and publish. After publishing, space members can view the file. The original conversation file is kept, and a sequence number is automatically added to files with the same name. Before publishing, check whether the file is appropriate to share in the space.
Conversation outputs don't automatically become space assets just because they're generated. If a Task is linked and you have the required permissions, you can also link the Task through the options in the publish dialog. If you're told that the file was published but linking failed, just retry the link as prompted. Don't mistake this for the file not being published. For managing results in Tasks, see Tasks.
Continue in a new conversation: In the available reply actions, select Continue in new conversation to branch a new conversation from the specified reply, keeping the history up to that reply. The original conversation isn't overwritten, and this operation doesn't copy the entire execution environment or files. If the source conversation is linked to a Task, you still need to meet conditions such as Task participation eligibility and the Task being unarchived.
Organize history: Find conversations in the current space, and rename, pin, or unpin them through the conversation's more actions. You can archive conversations that you don't need for now but want to keep. Archived conversations no longer appear in the regular conversation list. You can view and unarchive them in Archived conversations.
Archiving requires the conversation to be idle. If it's queued, running, or waiting for confirmation, handle the current task first. Team and channel conversations don't follow the regular conversation archiving process described here. Archiving is different from deleting: a deleted conversation can't be recovered, so make sure you've saved the results you need before you delete it. The available management operations also depend on the conversation type and your permissions.
Permission limits and FAQ
Why can't I see my colleagues' regular conversations in a shared space? Regular conversations are isolated per person. Explicitly shared automation run conversations follow shared space member permissions, unlike regular conversations. For details, see Automations.
Why can't I send messages? First check the prompt in the input area to tell apart causes such as a run in progress, waiting for confirmation, attachments not ready, concurrency or quota limits, and unavailable models, capabilities, or execution environments, and then handle the corresponding issue. Don't conclude that the conversation has expired just because you can't type.
Why am I told that the Agent configuration or a capability is unavailable? Models, MCP, Skills, and other resources being deleted, inaccessible, or having connection errors can all affect runs. If the model can be replaced, select an available model. If an MCP or Skill required by the Agent is unavailable, someone with permission needs to check the Agent and the corresponding capability configuration.
Why am I told that the conversation has expired or doesn't match the sandbox? First confirm the space that the conversation belongs to, and whether that space's current execution environment is available and matches the conversation. Shared spaces and personal spaces each use their own execution environment, so a working personal environment doesn't mean that a shared space conversation can continue. Contact your admin as prompted on the page, and if necessary, create a new conversation in the correct space. Don't treat all past conversations as invalid.
Why can't I find the target Task in the Task list? Make sure the current space is correct, the Task isn't archived, and you're its owner or a collaborator. Being able to view a Task or having space management permissions doesn't necessarily mean you can link it to a conversation. For the specific rules, see Tasks.
Parent section: Workspaces. You can continue reading directly from the related pages above.