Import & Export Agents

Agents are portable. Export them as JSON files, share them with teammates, and import them into any QARK installation.

Export Agents

Export a Single Agent

1. Open the agent gallery.
2. Select the agent you want to export.
3. Choose Export from the agent’s menu.
4. QARK saves a .json file to your chosen location.

Export Multiple Agents

1. Open the agent gallery.
2. Select Export All or use multi-select to choose specific agents.
3. QARK produces a single .json file containing all selected agent definitions.

What Transfers

The exported JSON captures the full agent definition:

Field	Included
Name, description, icon, color	Yes
System prompt (with mode: append/replace)	Yes
Tool selection (built-in tool IDs, MCP tool references)	Yes
Temperature, max tokens, additional LLM parameters	Yes
Context strategy	Yes
Agent type (standard or tool)	Yes
Input schema (for agent-tools)	Yes
Output schema (for agent-tools)	Yes
Category, sort order, favorites flag	Yes
Availability mode (agents_only / everywhere)	Yes

What Needs Manual Adjustment

Model and provider IDs — the exported file includes the model identifier (e.g., claude-sonnet-4-20250514) and provider name. If the destination installation does not have that provider configured or uses a different model catalog, you need to update the model assignment after import.

MCP tool references — if the agent uses tools from an MCP server, the destination installation must have that same MCP server connected. The tool IDs are preserved, but they resolve only when the matching server is available.

Agent-tool references — if the agent’s tool set includes other agent-tools, those agents must also exist on the destination installation. Export and import them together, or ensure dependencies are already present before importing.

Import Agents

Import via Dialog

1. Open the agent gallery.
2. Select Import.
3. Choose a .json file from your filesystem.
4. QARK validates the file and shows a preview of the agent(s) to be imported.
5. Confirm the import. Agents appear in the gallery.

Import via Drag and Drop

Drag a .json agent file directly onto the QARK window. The import preview appears automatically.

Handling Conflicts

If an imported agent has the same name as an existing agent:

• QARK prompts you to rename, replace, or skip the conflicting agent.
• Replacing overwrites the existing agent’s definition entirely.
• Renaming appends a suffix and imports as a new agent.

JSON Format Reference

The agent JSON structure follows this shape:

{
  "version": 1,
  "agents": [
    {
      "name": "Research Agent",
      "description": "Investigates topics using web search and produces cited summaries",
      "icon": "🔍",
      "color": "#4A90D9",
      "agent_type": "tool",
      "system_prompt": "You are a research specialist...",
      "system_prompt_mode": "replace",
      "model": "claude-sonnet-4-20250514",
      "provider": "anthropic",
      "temperature": 0.3,
      "max_tokens": 4096,
      "context_strategy": "auto_compact",
      "tools": ["web_search", "url_reader", "file_write"],
      "input_schema": [
        {
          "name": "topic",
          "type": "string",
          "description": "Subject to research",
          "required": true
        }
      ],
      "output_schema": [
        {
          "name": "summary",
          "type": "string",
          "description": "Research findings"
        }
      ],
      "availability": "agents_only",
      "category": "Research",
      "sort_order": 1,
      "is_favorite": false
    }
  ]
}

The version field ensures forward compatibility. QARK reads the version number during import and applies any necessary migrations for older formats.

Share Agents with Teams

For team-wide agent distribution:

1. Export the agent set your team should use.
2. Share the .json file through your existing channels — version control, shared drives, internal tools.
3. Each team member imports the file into their QARK installation.
4. Team members can duplicate and customize imported agents without affecting the shared baseline.

There is no central agent server. Agents are files. Version them, review them, distribute them however your team handles shared configuration.