Import Agents
The platform can restore portable-export ZIPs into another workspace. Imports always create new agents with new IDs; they never update or replace existing agents.
Before you import
- Keep the original ZIP intact and treat it as sensitive; it may contain messages, files, contacts, and durable SQLite data.
- Make sure the current workspace has enough agent slots and that you can normally create agents there.
Your deployment may roll this feature out separately.
Import into the current workspace
- Switch to the destination personal, Organization-private, or Team workspace.
- In Agents, choose Import agents beside New agent and select the original ZIP. In the classic interface, open the arrow beside New agent and choose Import agent.
- Wait for format, path, size, and checksum validation.
- Select agents, edit their destination names, confirm capacity, and choose Import.
- Keep the dialog open or return to Import agent later for progress and results.
Bulk imports are independent per agent. If one agent fails, successfully restored agents remain available and the result explains what needs attention.
The destination is shown in the import dialog and stays fixed throughout the import. Team imports create agents in that Team, including when you switch workspaces in another tab. Permissions are checked again during upload and restoration; a deleted or inaccessible Team never falls back to My workspace.
Large ZIPs upload in 8 MiB pieces so each request stays below common proxy limits. You can pause and close the dialog, then reopen Import agents and select the same ZIP to resume. Saved pieces are verified against the selected file before continuing. Incomplete uploads expire after 24 hours by default; Discard upload removes the saved pieces. No agents are created until you select them and choose Import.
What the platform restores
- Name, charter, descriptions, tags, avatar, and the nearest supported intelligence tier.
- Memory snapshots, completed planning information, tasks, and deliverables.
- Visible conversation history, attachments, and non-billable historical tool steps.
- Files and compatible sharing, saved skills and capabilities, disabled custom-tool source, durable SQLite tables, and peer relationships between agents imported together.
Older agent-platform.portable-export/v1 archives remain supported, as do legacy-format v1 and v2 ZIPs from earlier platform versions. Because v1 did not record every filespace and skill detail, the platform uses safe best-effort fallbacks and shows those choices as warnings. New v2 exports include machine-readable restoration metadata.
What stays off
An imported agent becomes active for web chat only after restoration succeeds. Imported work and messages are not replayed. Schedules, proactive work, external channels, webhooks, MCP and OAuth connections, managed integrations, custom Python tools, and recreated peer links remain disabled.
Credential values are never included in a portable export. Reconnect required services in the destination and review their scopes before enabling writes.
Owner-level instructions and communication policies from the source are preserved in the migration report for reference. They do not change the destination workspace and are not appended to the agent charter. Imported contacts are disabled reference entries.
Review an imported agent
Open each result link and review its charter, memory, plan, tasks, files, private-copy warnings, disabled tools and schedules, contacts, permissions, and reconnection requirements. Test web chat before enabling automation or external delivery.
Troubleshooting
An upload stops: Reopen the import and select the same ZIP to resume. If all bytes are saved, choose Continue to validation. A stalled validation can be queued again with Retry validation if it has stalled. Timeouts and proxy errors are shown in the dialog rather than leaving progress stuck.
The ZIP is rejected: Upload the unmodified original. Changed files fail checksum validation; newer formats require upgrading the destination.
An agent cannot be selected: The source export may have failed for that agent, or required v2 restoration metadata may be missing.
The import cannot start: Workspace access, account state, capacity, and names are rechecked at start time.
A v1 import has warnings: Older archives may lack exact filespace or skill metadata; review the reported fallback.