An imported agent should arrive with the instructions and Skills that make it useful, while asking for access to the tools it needs without carrying credentials or machine configuration.
#5015 gives Agent Snapshot import one clear front door. Snapshot v1 carries the prompt, runtime preferences, profile and optional memory. It cannot carry Skills or tool requirements. Persona Packs can describe both, but they do not import into Desktop, and their MCP configuration contains deployment details that should not travel with an agent.
User flow
The import preview should show:
- identity and instructions;
- every included Skill, with its exact plaintext available for review;
- the capabilities the agent needs;
- which requirements can be satisfied by this Project and which still need a connection.
Import should create a fresh identity and preserve those declarations without starting commands, installing credentials or silently granting tool access. The user can then connect each requirement to an approved Project connection on the selected execution target.
Portable boundary
I think this needs Agent Snapshot v2 rather than optional fields on v1. An older client must not accept a portable agent, discard its Skills and tool requirements, then export a reduced file that still looks complete.
The portable values should contain Skill contents and digests plus logical tool requirements. They should not contain commands, URLs, environment-variable names, credential references, local connection IDs or machine paths. Snapshot remains an interchange format, not a runtime registry.
For the first slice, I would keep activation out of scope. It should declare, validate, preview, import and round-trip the new values. Project binding and launch resolution can follow through the shared MCP handoff in #4164.
@tellaho @atishpatel, this builds directly on the Add Agent and snapshot work in #5015 and #5016. I would like to align the v2 boundary with those paths before writing it.
An imported agent should arrive with the instructions and Skills that make it useful, while asking for access to the tools it needs without carrying credentials or machine configuration.
#5015 gives Agent Snapshot import one clear front door. Snapshot v1 carries the prompt, runtime preferences, profile and optional memory. It cannot carry Skills or tool requirements. Persona Packs can describe both, but they do not import into Desktop, and their MCP configuration contains deployment details that should not travel with an agent.
User flow
The import preview should show:
Import should create a fresh identity and preserve those declarations without starting commands, installing credentials or silently granting tool access. The user can then connect each requirement to an approved Project connection on the selected execution target.
Portable boundary
I think this needs Agent Snapshot v2 rather than optional fields on v1. An older client must not accept a portable agent, discard its Skills and tool requirements, then export a reduced file that still looks complete.
The portable values should contain Skill contents and digests plus logical tool requirements. They should not contain commands, URLs, environment-variable names, credential references, local connection IDs or machine paths. Snapshot remains an interchange format, not a runtime registry.
For the first slice, I would keep activation out of scope. It should declare, validate, preview, import and round-trip the new values. Project binding and launch resolution can follow through the shared MCP handoff in #4164.
@tellaho @atishpatel, this builds directly on the Add Agent and snapshot work in #5015 and #5016. I would like to align the v2 boundary with those paths before writing it.