Skip to main content
Version: 0.8.5

Agents and Workspaces

An Agent is a reusable digital coworker with a name, role instructions, model, skills, tools and memory. The same Agent can work in different Workspaces without being copied.

A Workspace is the explicit context for files, Chats, Works, Mini Apps and Git repositories. Its file root may be managed by Clawuno or linked to an existing computer folder; Agents only reason about the Workspace root and relative paths.

Access and roles​

A Workspace's user access and its Agent arrangement are separate. Arranging an Agent does not give a person permission to enter that Workspace. Owners and administrators manage access; a child Workspace can inherit its parent's Agent arrangement until independently configured.

A User works with authorized Workspace chat, files and existing Mini Apps. Work, Git, Agent configuration and Mini App authoring are not available to that role. Advanced Users can create Workspaces but manage only those they own; administrators can manage all Workspaces. A missing control may be a role restriction, not a failed installation. See three user roles and access permissions for the complete comparison and grant procedure.

Create and configure a Workspace​

  1. As an administrator or Advanced User, create a Workspace from the sidebar. Use the intended parent's entry when creating a child.
  2. Enter a name. New names are checked across the instance, not only among siblings.
  3. If local-folder selection is available, link an existing folder on the Engine host; otherwise use Clawuno-managed storage. A remote connection cannot make a folder on the client computer the remote Engine's file root.
  4. Select collaborators in Agents and, in Team edition, choose user rules in Access permissions. New children inherit their parent by default and can be given independent arrangements.
  5. Save, check the available Agents on the home page and upload a test file to confirm its location.

Open the same settings dialog from the Workspace header or sidebar menu. Existing Workspaces allow name, assignment and access changes; location, owner and file source are read-only here. Renaming does not move the directory or replace its binding. Review concurrent-save conflicts instead of overwriting someone else's changes.

Configure an Agent​

  1. An administrator or Advanced User opens Agents and creates or edits an Agent.
  2. Use its name and description for a lasting responsibility and select an administrator-configured model.
  3. Write task boundaries and quality criteria in its instructions. Select only needed tools, MCP services and Skills rather than enabling everything.
  4. Check Workspace assignments. Global availability affects current and future Workspaces; changing specific assignments still requires management rights there.
  5. Save and start a small Chat from the target Workspace to check file location, output quality and external calls.

Archived Agents are not available for new work. Enable the archived filter in the Agent list when needed. Renaming does not affect existing conversations or move them to another Workspace.

Practical rules​

  • Give an Agent one stable professional role rather than one temporary task.
  • Make the active Workspace clear before asking an Agent to create or modify files.
  • Use separate Workspaces when projects require different files, members or operational boundaries.
  • Review an Agent's model, skills and tools before using it with sensitive data.
  • You can rename an Agent without interrupting its existing conversations or collaboration with other Agents.

Ask Uno:

Create a financial reporting Agent for this Workspace and show me the settings before saving it.