Shared Agents & Context
Share agents and methods with your team, keep the right context available, and choose who can use and maintain it.
Let your team use the same agents without sharing all your work
A workspace gives teammates agents and useful knowledge to work with. Ownership and access settings determine who can maintain an agent, what the agent can use, and who can see the work.
Who owns the agent, and where do you use it?
Everyone has a personal workspace for their own work. A team workspace gives teammates a place to share agents and knowledge. The agent’s owner keeps its instructions current. Where you use it and whose accounts it uses are separate choices.
An agent your team can maintain
The workspace owns its setup, and teammates bring it work in workspace threads and rooms.
- Who maintains it
Workspace Owners and Editors can change its setup. - Where work happens
Teammates run it in workspace threads and rooms. - Whose accounts it uses
That depends on the agent’s connections and each skill’s credential settings.
Use the team’s agent with your accounts
Its instructions stay current with the workspace while your threads and connections stay in Personal.
- Who maintains it
The team maintains its instructions, and updates reach the agent you use in Personal. Fork it if you want independent instructions. - Where work happens
Your threads stay in Personal, and the usage is charged to you. - Whose accounts it uses
You connect your own accounts and skill keys. The team’s saved credentials do not copy over.
The workspace’s Agents view shows workspace agents and personal agents shared with the team. Open a workspace agent to find Add to Personal.
What changes when you transfer or share an agent
Joining a workspace leaves your personal agents and threads where they are. Choose what should happen to the agent, its setup, and the work around it.
Give the team ownership
Transfer your personal agent when the team should maintain it. The workspace becomes its owner, and its threads move there too. Review the new audience and the resources that come along:
| Resource | What to check |
|---|---|
| Configuration and agent-owned memories | Move with the agent. |
| Threads | Move into the workspace. Review the count and the new audience. |
| Linked documents | Choose whether to copy each into the workspace or leave it behind. |
| Linked skills | Review ownership and the options offered. Another workspace’s skill does not change ownership. |
| Connections and other resources | Review the choices in the confirmation before relying on them. |

Use the team’s agent for your own work
With Add to Personal, you can use a workspace agent with your own accounts. Its instructions stay current with the team’s agent, while your threads and usage stay in Personal. The team agent’s past threads, memories, attached files, accounts, and keys do not come along.
Open the agent from the workspace’s Agents view and choose Add to Personal. Review its connections and schedules before confirming, since selected schedules turn on when setup succeeds. Then connect your accounts, supply any skill keys, and try a task with your own sources. If you already added it, choose Open your copy.
Instructions stay linked
The team maintains settings marked Set by [workspace name]. Updates to those instructions reach the agent you use in Personal.Your settings are yours
Change its name and appearance, choose your model and budget, or restrict its access further. Your changes do not edit the workspace agent.Fork for independent instructions
Choose Fork from the agent’s ⋯ menu if you want to edit the team-controlled instructions yourself. The fork stops receiving workspace updates.
If the team deletes the agent
The agent you added to Personal stops running. Fork it first if you need one that continues independently.
For the steps to transfer or share an agent, see Share agents with your team.
What your team can share with agents
Your team can share skills, memories, and source material. Sharing makes a resource available; each agent’s access and knowledge settings determine whether it can use that resource.
Maintain one method together
Share a skill when several agents should follow the same method, such as preparing a customer brief or checking a report. Workspace Owners and Editors maintain workspace-owned skills. If someone shares a personal skill, that person remains responsible for it.
Skill discoverability and the agent’s knowledge settings are separate controls. A shared skill does not become part of every agent’s work automatically.

- Update the shared skill when the improvement should reach future runs that use it. Work already in progress does not reload the change.
- Fork the skill when you need a separate method. The fork will not receive later updates from the shared source.
A shared personal skill is used by reference. If its owner deletes it or removes access, the workspace does not retain an independent copy. See Edit and import skills.
Share facts that help future work
Keep a lesson with one agent when it applies only to that agent’s work. Use workspace memories for facts and preferences other agents may need. Each agent’s knowledge settings still control what it can use.
The save destination determines whether a new memory belongs to This agent’s memories or the workspace. Learning settings determine whether a proposed lesson needs review or can be saved automatically where permitted.
An Owner or Editor can Promote to Workspace memories when a lesson should be available beyond one agent. The memory moves into the shared library, and the original agent keeps access. Move to an agent narrows it to one agent and clears earlier agent links.

You can also add an established policy with + New workspace memory. See Memories for how to maintain and retrieve it. Check a memory’s current location to understand its audience; version history tracks content edits, not ownership moves.
Keep useful references available
Keep material the team should read and maintain in the workspace library, such as a service description or approved reference guide. Members can read it; Owners and Editors can contribute and curate it.
Use the agent’s knowledge settings to make relevant sources available to it. Give customer-specific files with the job when they do not belong in shared context.
A file or output appearing in Library is not automatically shared with the workspace. Thread files and outputs can have their own access rules. Check the item’s sharing controls before sending a teammate its link.
These are separate settings: the knowledge profile controls memories; Context files provide reference material.
Who can see the work?
Joining a workspace does not move your personal work into it. Visibility depends on where a thread or resource lives and whether you share it.
| Where it lives | Who can see it |
|---|---|
| Personal workspace | Your agents, threads, and library stay personal unless you share or transfer them. Workspace Owners cannot browse or move your personal library. |
| Individual workspace thread | The person who starts it keeps access while required permissions remain valid. Workspace Owners can review it read-only, even without an agent. Editors and Members cannot see teammates’ threads just because of their role. |
| Workspace room | Every workspace member can see and join it. |
| Workspace-library memories and documents | Members can read them. Agent use also depends on knowledge settings. |
| Thread outputs | Access follows the thread and any explicit sharing. Appearing in a workspace list does not make an output available to everyone. |
A workspace agent does not inherit your personal memories
A workspace-owned agent uses workspace context and its own resources according to its configuration. A personal agent shared with the workspace keeps its existing knowledge access. Neither setup grants access to another person’s private context just because they start a run.
Owner oversight lets a person review workspace work. It does not give an agent access to every thread that person can inspect. Explicit thread sharing and oversight of a shared personal agent are separate access settings.
Whose account runs a shared skill?
Sharing a skill does not decide whose connected account it uses. That depends on the skill’s credential mode:
| Mode | What teammates should expect |
|---|---|
| Use my credentials | The skill uses the sharer’s connected account and permissions. A teammate can choose their own credentials where offered. |
| Each member adds their own | Each teammate connects their own account before using the skill for that work. |
If a skill shows Needs your credentials to run, add them in the skill and check for Using your credentials before retrying. See Call APIs from a skill for the setup. Do not paste secrets into a thread.
Who can use and edit shared work?
Workspace roles control what teammates can do with workspace-owned agents and resources. Members use them, Editors maintain them, and Owners also manage the workspace and review its threads.
| Responsibility | Owner | Editor | Member |
|---|---|---|---|
| Run workspace agents and use available skills | Yes | Yes | Yes |
| Read workspace-library memories and documents | Yes | Yes | Yes |
| Edit workspace-owned agents, skills, memories, and documents | Yes | Yes | No |
| Review other members’ workspace threads read-only | Yes | No | No |
| Manage members, invitations, roles, and workspace settings | Yes | No | No |
| Permanently delete workspace-library memories and documents | Yes | No | No |
Sharing does not transfer edit access
Workspace roles do not let an Owner or Editor change someone else’s shared personal agent or skill. Its personal owner maintains it. An edit to a workspace memory that your role does not allow is not saved into your Personal library instead.
The last Owner cannot be removed or demoted. To choose roles and invite teammates, follow Share agents with your team.