AI employees
An AI employee combines a stable role, capabilities, and work context. Different employees can focus on documents, research, operations, development, or other tasks.
Select an employee
- Choose an existing employee from the sidebar.
- When you need another capability, use the employee or skill entry provided by the application to select reviewed assets.
- Check whether the employee belongs to your Personal space or the current Team.
An employee can use only Skills and MCPs that the current account has installed, purchased, or been granted. Marketplace items are never executed merely because they appear in search.
Set a workspace
Choose a dedicated workspace when an employee must read or generate local files. Use a separate folder for each project so changes remain clear and accidental cross-project edits are less likely.
One employee can have multiple named workspaces. Switching workspaces does not move or delete files in the original folder.
Manage conversations
- Start a new conversation for a new goal so unrelated context does not mix.
- View history by employee, workspace, or conversation.
- Before deleting a conversation, check whether you still need any generated files.
Permission prompts
The client may request permission when an employee needs a tool or controlled capability. Review the target and scope before allowing or denying it. After a denial, you can ask for an approach that does not require that permission.