ExtendRoom 11 of 13

Install a specialist. Make it yours.

An agent is a persona, a set of instructions and a choice of tools. Since 2.2, you can share that setup as a package: find one in the Marketplace, inspect it, install it, and adapt it to your own work.
Agents / MarketplaceExample package

Research helper · v1.0.0

A specialist you can inspect.

Find agents alongside skills and plugins in the Marketplace, or import a .sophon-agent file.

Publisher
Example publisher
Package type
Agent
Purpose
Research a topic and separate evidence from inference.
Contents
Persona files and a manifest
1 / 4

Simplified recreation of the Dashboard review and update flow. Example package; no installation takes place.

ABefore it acts

The whole persona, before the first turn.

Skills, plugins, and now agents
Browse the Marketplace's agent packages or import a .sophon-agent file. A package contains a manifest and persona files, with requirements for skills and tools. It does not contain executable code.
Read before confirming
The install preview shows the publisher, every persona file, injection-scan findings, required skills, expected tools, initial settings and the proposed agent id. Installing needs ManageSkills permission.
Chat can ask; you decide
Sophon can search for a specialist and request its installation. That High-risk approval is never automatic. Open the full preview and approve in the Dashboard; the CLI, Mobile and external chat channels can reject that chat request, but cannot approve it.
Autonomy is your choice
Install creates the agent with heartbeat, auto-approval, planning and model pins off. Installing a persona does not switch on its background work.

BAfter you make it yours

Your edits have a place in the update.

Review a three-way diff
An edited agent is customized, and automatic updates pause. Compare the published copy, your changes and the proposed version; choose what to apply or skip the version.
A visible origin
The agent's Marketplace panel keeps its source, installed version and update status. You can reset files to the published copy or detach from updates; detaching does not make the agent a trusted local persona.
Withdrawn versions stop
If a check finds the installed version revoked or the package removed, delegation and its heartbeat stop. You receive a security notification and choose whether to keep using that version or take another one.

CFor authors

Share the setup that works for you.

Export an existing agent, or scaffold a package project with the CLI. Review persona files for private information before exporting or publishing. A linked Marketplace account needs publishing permission; an API key is also supported by the developer CLI.

sophon agents search research --limit 10
sophon agents export researcher --output ./dist
sophon dev new agent acme-helper --author "Acme"
sophon dev validate
sophon dev build

Run validate and build from the new project directory. Legacy agent.json projects still validate and install with a warning, but must migrate to manifest.json before building or publishing. Follow the package and migration guide.

Limits

What an agent package doesn't promise.

  1. A scan finding nothing is not a guarantee. Read the persona and install only from sources you trust; packages are not cryptographically signed.

    Where it says so
  2. Package agents stay third-party, even after you edit or detach them. Their turns do not qualify for standing auto-approval, and the router does not pick them automatically.

    Where it says so
  3. Update all skips agents. Customized agents wait for your review, and automatic updates require both your settings and a clean update gate.

    Where it says so
  4. Publishing through Sophon requires a Marketplace with agent publishing support and a fresh account link with publishing allowed. DevStudio agent projects need version 1.1.0 or later; its distribution remains separate.

    Where it says so

Start with a persona you can read.

Review an agent in the Dashboard, or package your own with the CLI.