Skip to main content
Hyperagent
ConceptsWorkspaces

Workspace agents

Choose the best way to share your agents with your team.

A workspace makes an agent available two ways: the workspace owns it, or a person shares their personal agent to the workspace. Both let every member run it. However, the way the agent is shared determines who may change it.

Availability is easy; maintenance is the real choice

Either model gets the agent in front of your workspace today. Only one of them decides who fixes it next month.

The workspace's Agents page keeps the two apart, so you can always tell which model an agent is on.

Two ownership models

Share Context Builder dialog offering Share with a workspace or Transfer to a workspace.
Workspace-owned agents are maintained by Owners and Editors; shared personal agents stay with their author.

The agent belongs to the workspace. Owners and Editors edit its configuration; every member runs it.

  • Who maintains it: Owners and Editors, together
  • What they can change: instructions, skills, tools, connected integrations, and its execution mode
  • Choose it when the agent's job belongs to the workspace's workflow rather than one person's

Configure multi-agent workflows once

Workspace-owned agents can work as a system. Scout, the triage agent, can triage a case, delegate the documentation to Scribe the documentation agent, and pass the approved result to Press the publisher. Owners and Editors maintain that shared workflow once, and Members can run it without rebuilding the handoffs each time.

Agents can start on a schedule, from Slack, or through another agent. See Invocations for each option.

The agent stays personal and the workspace gets run-only access. Its owner keeps everything else.

  • Who maintains it: the person who shared it, alone
  • What the workspace can do: run it, and nothing more, whatever their role
  • Choose it when teammates should benefit from the agent without becoming its maintainers

Review context and delegation before sharing

A shared agent can still use any personal memories its owner configured it to access, and details from those memories can appear in runs started by teammates. It cannot use workspace context or receive delegated work from another agent. Transfer it to the workspace if it needs either capability.

To share, use Share… on your agent and pick the workspace. Nothing transfers: no copy is made, and the workspace can't edit the source. If Press needs a new publishing connection, only its owner can add it.

Revoking the share is an access decision, not an ownership change: Press stops being runnable through that workspace, nothing is deleted, and the workspace keeps no frozen copy. Share it again later and the same relationship comes back rather than a duplicate.

Move an agent between personal and shared workspace

Sharing grants access; a move changes who owns the agent. Reach for it when maintenance should change hands: a personal agent whose job has become the workspace's, or a workspace agent that should go back to one person.

Start the transfer

Open Share… on the personal agent and choose Transfer to a workspace. Select the destination. You need Owner or Editor access there; Import creates an agent from an export file instead of transferring this one.

Share Context Builder dialog with Transfer to a workspace as the ownership-changing option.
Choose Transfer to a workspace when Owners and Editors should maintain the agent together.

Review what moves

The confirmation lists what changes hands: the agent's configuration, its own memories, and its threads, which move into the shared workspace. It tells you how many threads that is before you commit. Linked documents get a per-document choice: copy into the workspace, or leave behind.

Move into workspace confirmation showing thread visibility and choices for skills, connections, and linked memories.
Review what moves before confirming the transfer. Threads are moved to the workspace along with skills, memories, and integration connections.

Confirm

From then on Owners and Editors maintain the agent and every member can run it. The reverse move, demoting a workspace agent to one person, works the same way, and pauses the agent's automations so a schedule doesn't keep firing under changed ownership.

FAQs

Workspaces

A shared workspace that scopes a set of agents, skills, and memories, with governance that lets many people use what a few maintain.

Workspace skills

Share reusable methods with a Workspace, choose which account runs them, and decide when to use the shared source or fork it.

On this page

Two ownership modelsMove an agent between personal and shared workspaceFAQs