Use your organization's Agent in a personal App¶
You can use an Agent your organization shares with you in an App you own personally, without moving the Agent or making your App organization-owned. Start in the portal; the CLI and GraphQL doors are included below as alternatives.
The App stays yours, the Agent stays your organization's, and the install references that Agent rather than cloning it.
Not run live
This page is written from the merged server code and tool descriptions, not from a live run. The install and serving paths have not been exercised for this page.
What you can install¶
A personal App can install:
- a
PUBLICAgent; - your own Agent; or
- an
ORGANIZATION-visible Agent whose organization you currently belong to.
The last case is the one this page covers. An unqualified but readable Agent is
refused with ORGANIZATION_MISMATCH. An Agent you cannot read answers as
absent, so the response does not reveal it.
Create a personal App with the Agent¶
In the portal, open Apps and choose New app. Select the Agent your
organization shares with you, fill in the App name, URN and type, then choose
Create app. The list includes your own Agents, PUBLIC Agents and the
ORGANIZATION-visible Agents of organizations you belong to; the server decides
whether the install is allowed.
For an App you already own, open its Agents tab. Under Add an agent, select the Agent and choose Link.
CLI and GraphQL alternatives¶
Create a new personal App with:
For an App you already own, install the Agent with:
The second command installs only the Agent you name. It does not install that
Agent's dependencies. Creating a personal App with required dependencies, or
with optional dependencies you explicitly request, is refused with
BAD_USER_INPUT before the App is created.
Through GraphQL, use createApp without orgRef for a new personal App, or
installAgentIntoApp for an existing one. There is no MCP tool that installs an
App.
What keeps an organization Agent working¶
For an organization Agent that is not PUBLIC, all three of these conditions
must hold:
- The Agent stays
ORGANIZATION-visible. - You stay a current member of its organization.
- Your subscription to it stays active.
They are checked at every read and serve, not only when you install. If any of them stops holding, the install and its install memory are kept, but a bind, chat or run is refused until you qualify again. Serving can resume when all three conditions hold again; nothing is deleted in the meantime.
If you left the organization, ask it to restore your membership. If it narrowed
the Agent's visibility, ask it to restore ORGANIZATION visibility. For a
revoked or expired subscription, ask the organization how it wants to restore
your access.
The serving refusal is
BOOT_PROMPT_INSTALL_LICENSE_INACTIVE.
The same check also applies when you cast or preview a worker.
Who can read through the install¶
Only App participants who are current members of the Agent's organization can read its system memory or this install's install memory, and only while the owner's licence holds. A participant who is not in that organization does not inherit the organization text through your App.
A licence opens no data by itself. In particular, the Agent's
ORGANIZATION-visible knowledge memories remain readable by the organization's
members only. See Memory access.
Related¶
- Agents and Apps: the definition/install split, and what stays with your organization or with you.
- Serving a boot prompt: the licence refusal and its chat-specific concealment.
- Customize an installed Agent for your App: change the Agent for this App only through its install memory.