release
v2.2.0
Sophon 2.2 records every workflow run and lets you build, test and re-run workflows in the Dashboard without the agent, replaces Thinking with Effort, gives the in-chat CLI pickers, themes and image paste, lets a device’s owner manage Sophon Node from the Dashboard, adds six Dashboard themes and agent packages, and removes Discussions.
Workflow runs
Mobile has no run viewer, run list or debug tools yet, and its Run still waits on the synchronous route, giving up after 15 seconds on a long or approval run while the run carries on. Runs in flight at a restart are marked Interrupted and are not resumed.
- Durable runs: every run and every step attempt is stored in the database, listed per workflow and streamed live to the run’s user and the person who started it, so a run that went wrong can be read afterwards.
- Run viewer: the Dashboard draws a run on the canvas, step by step, with each step’s input, output and effect and why a skipped step did not run; Run now starts the run in the background and opens the viewer.
- Start, follow and cancel: POST /api/workflows/{id}/runs answers 202 with a run id, /api/workflow-runs lists and reads runs, and a run can be cancelled; the synchronous /execute stays and now also returns the runId.
- v2.1 history carried over: history files from v2.1 are imported once, a minute after the first start, as finished runs marked Legacy. Legacy runs have no inputs, step timings or definition snapshot, so the viewer draws the current workflow.
- Retention: finished runs are pruned after 30 days, keeping the newest 20 and at most 500 per workflow, adjustable with SOPHON__Workflows__Runs__RetentionDays, MinRunsPerWorkflow and MaxRunsPerWorkflow. Stored records are redacted by setting name and pattern, and outputs and inputs over 64 KiB are cut.
- Run caps: on one Gateway at most 8 runs of one owner and 32 of one tenant execute at once and the rest wait as Pending; past 64 per owner or 256 per tenant a new run is refused with 429 too_many_runs.
- Cost per step: LLM Prompt steps record their model, tokens and cost, and API Call response bodies are capped at 1 MB by default (maxResponseBytes, up to 10 MB).
- Notifications that fire: outbound workflow.completed and workflow.failed webhooks are now published, and Mobile gets a push when an unattended run fails. There is no success push.
Workflow builder
The builder has no field yet for settings.maxConcurrency, a Loop’s continueOnIterationError or maxResponseBytes; set those in the workflow JSON. Browser Back and Forward can still leave unsaved changes without asking.
- Readable step ids: every card shows its id, new steps are named after their kind (prompt, prompt_2, branch), labelling a fresh step renames it to match, and renaming an id rewrites every reference and edge after saying how many.
- Reference autocomplete: typing {{ in an expression field lists the earlier steps, the trigger, the run input, variables and functions, Enter or Tab inserts the entry, and a step can be picked on the canvas.
- Edges and switches you can edit: an edge-condition editor, switch cases added and renamed on the switch itself (a rename rewrites its edges), the trigger drawn on the canvas, and a docked properties panel that no longer covers the canvas.
- Problems before Save: the Gateway’s issues show on the steps, Save is blocked on a reference to the step itself, a later step or a step without .output, and a skill the workflow sandbox preset blocks is marked Blocked.
- Unsaved changes ask: Run with unsaved edits offers Save and run, Run saved version or Cancel, leaving the builder asks before discarding, and Undo also covers setting edits, moves and deletes.
- Templates: email-summary is repaired, the shipped templates label their steps with readable ids, and a new Web Digest template fetches a page every day at 09:00 UTC, summarizes it and sends the digest to WebChat.
Workflow debugging
Re-run uses the workflow’s current definition and re-runs a loop whole. Runs imported from v2.1, step tests, sub-workflow runs and runs of a workflow whose owner changed cannot be re-run.
- Test step: run one step with mock outputs, a recent run’s data or the pinned sample, and see its resolved inputs and any reference that did not resolve. A step that can change something outside Sophon (Send Message, file writes, code, an API Call other than GET, HEAD or OPTIONS) asks for a second click first.
- Re-run and Re-run from here: start a finished run again from its start or from a chosen step, keeping the earlier steps that succeeded and have not changed since; a plan shows which steps are kept and which run again, and repeating a step with an effect asks first.
- Pinned sample input: one sample per workflow, typed or taken from a run, at most 64 KB, for Run with sample and for step tests. Only the owner and Admins see it, and it is stored in plaintext in the workflow file.
- Each step records its effect (read-only, idempotent, effectful or interactive) and the variables it wrote, shown in the run viewer.
Workflow engine and triggers
Loop iterations run one at a time and loops cannot nest. Inbound webhook registrations have no replay protection, and /webhooks is outside the Gateway’s rate limiter, so keep it behind TLS and rate-limit it at the reverse proxy.
- Joins and skips: a step fed by both branches of an if/else now runs once, when every incoming connection is decided and at least one was taken, a step that does not run shows as skipped with the reason, and logic.merge outputs only the inputs that were taken.
- Loops that loop: a Loop step repeats the steps on its body handle once per item or while its condition holds, then continues on done; a list longer than maxIterations fails the loop.
- Opt-in concurrency: a workflow with a Parallel step or settings.maxConcurrency runs up to that many steps at once (1 to 8, 4 by default, capped by the host); every other workflow still runs one step at a time.
- Strict references: in a workflow created in 2.2, an action step whose reference does not resolve fails with “Unresolved reference” instead of sending the literal text; wrap optional values in default(…). Workflows created earlier are unchanged.
- Timeouts by step type: approvals wait 30 minutes, questions 5 minutes and a Wait step its own duration, a run is bounded at 24 hours, and a failed run’s error names the step that failed.
- Event triggers fire: channel_message and email_received start runs as the workflow’s owner on channels that owner owns in the same tenant, and a signed request to an inbound webhook registration (Bearer, HMAC-SHA256 or a custom header) starts a webhook run. Trigger types that cannot fire are refused on save and left out of GET /api/workflows/trigger-types.
- Approvals reach the owner: a workflow’s approval and question cards go only to the owner and same-tenant Admins, name the step that raised them and link to the run.
Workflows from the command line
- sophon workflows validate <file> prints the issues a save would answer, one per line, and exits 1 when one is an error; nothing is saved.
- sophon workflows runs, run and cancel-run list a workflow’s runs, show one run with each step’s inputs and output, and stop a run.
- sophon workflows execute starts the run, follows it to the end and exits by its outcome: 0 succeeded, 1 failed, cancelled or interrupted, and 130 on Ctrl+C, when the run keeps going. --async returns the run id at once.
Effort
Effort sets what Sophon asks each provider for; how much a model reasons at a level is up to the model. Azure OpenAI gets only the sampling change with Sophon’s built-in api-version, plugin providers get no level, and Mobile’s Effort chip applies only to messages sent from that screen.
- Effort replaces Thinking: Auto, Low, Medium, High, Extra high and Max replace Auto, Off, Fast and Full. A level is clamped to what the model accepts, levels a model does not accept are greyed out, and a model with no effort control says so.
- Auto: picks Low, Medium or High for each turn from its kind and content, without an extra model call, and never above Sophon:Models:EffortAutoCeiling (default high). Unattended turns start at Low, interactive chat at Medium, and coding turns in a bound workspace and researcher sub-agents at High; background calls such as titles and summaries get a fixed level, and a workflow’s LLM Prompt step keeps the model’s default.
- Set it like a model: effort is set per chat, agent, user and host in the same layers as model routing, stored with the conversation on the Gateway so every device sees it, and every reply shows the level it ran at and why.
- Where to set it: the Effort select in the Dashboard’s model picker, /effort and -e/--effort on sophon, sophon chat and sophon exec, and an Effort chip on Mobile.
- What each provider receives: Claude gets adaptive thinking with an effort level, also with tools, with its thinking sent back inside a tool loop; OpenAI gets reasoning_effort, or reasoning.effort on the Responses API for GPT-5.6, GPT-6 and the -pro and -codex models; Gemini gets thinking_level or a thinking budget; Bedrock, Copilot, Codex and the Claude Code CLI get their own fields; and OpenAI-compatible providers get the field their model’s catalog row names.
- Custom endpoints opt in: a custom OpenAI-compatible server, LM Studio or a vLLM server sends no effort field until its provider entry in models.json sets "effortWire".
- The reply ceiling follows the level: max_tokens is 16K up to Medium, 32K at High and 64K at Extra high and Max on streaming turns, never above the model’s own limit.
- Anthropic SDK: the Anthropic provider now uses Anthropic’s official .NET SDK on the same API version, 2023-06-01, and its requests carry that SDK’s own User-Agent and X-Stainless headers.
Sophon Code CLI
Allow all tools is off unless the host turns on Sophon:ApprovalPolicy:AllowAllMode. It covers only interactive turns in a trusted, bound workspace, needs the Admin role on Pro and Enterprise, and ends for good in a session once it reads untrusted content.
- Pickers: a bare /agent, /resume, /permissions, /mode, /trust, /export and /effort, and on the classic and pinned chat /model and /save, open a selection dialog instead of printing or needing an argument.
- Fewer commands: ten duplicated or unneeded commands are removed (/provider, /quit, /select, /tokens, /info, /tasks, /approvals, /agents, /sessions and /auto-approve); for this release a removed name prints its replacement.
- Themes: sophon-code is the new default, with sophon-code-light, sophon-code-dimmed, sophon-code-high-contrast, catppuccin-mocha and dracula added for ten in all, and /theme and the saved theme now work on every surface.
- Composer keys: Ctrl or Alt with Left and Right move by word, Ctrl+Backspace and Alt+Backspace delete the previous word, Ctrl+Delete and Alt+D the next, Ctrl+A, Ctrl+E and Ctrl+K work on the current line, and an emoji or accented letter counts as one character.
- Image paste: Ctrl+V or Alt+V pastes a clipboard image into the composer (Alt+V in Windows Terminal), dragging an image file in attaches it, and attached images now reach vision models as pixels, up to Sophon:Documents:InlineImageMaxBytes (5 MiB by default).
- Full-screen layout: an input band, a context line with the folder, branch, uncommitted changes, pull request, context and cost, and a footer with the permission mode and approval policy; ? on an empty composer opens the key help, and a new session opens on a Getting started welcome.
- Allow all tools: a host opt-in permission mode, entered from /permissions, in which tool calls that would ask run without a card for up to 120 minutes by default (Sophon:ApprovalPolicy:AllowAllTtlMinutes). Plan cards, workflow approvals, agent deletion and plugin installs still ask, and the Dashboard shows the mode as a red chip whose only action is Leave allow all.
- Workspace git status: the context line marks uncommitted changes and, when gh is installed and signed in as the Gateway’s OS user, shows the branch’s pull request; turn the lookup off with Sophon:Workspace:PullRequestLookup=false.
Sophon Node settings and confirmations
Managing folders and confirmations from the Dashboard needs both the Gateway and Sophon Node 2.2.0 or later; renaming works with any node. Mobile cannot edit node settings, and a headless Linux machine or a Windows session-0 service cannot show the confirmation dialog.
- Settings tab: a device’s owner renames it, manages the folders the agent may use and the actions the device asks before, from the Dashboard, and changes apply live on the node without a restart, or at its next connect if it is offline.
- Confirmations off, for a while: the owner can turn confirmations off for 1 hour, 8 hours, 24 hours, 7 days or until turned back on; the device list shows a Confirmations off chip, both sides audit it, and the computer shows a notification.
- Owner loosens, admins tighten: only the owner can loosen a setting, admins can tighten one or turn confirmations back on, and Sophon:Nodes:AllowConfirmationsOff=false turns the feature off for the whole Gateway.
- A lock at the computer: sophon-node lock stops Sophon from turning confirmations off or widening folder access there, sophon-node unlock removes it, sophon-node status shows the confirmations, the lock and the settings managed from Sophon, and sophon-node settings reset returns the node to its config.json.
- A hardened dialog: on Windows the dialog receives its text on standard input, so quotes, $(…) and backticks are shown as typed and never run as PowerShell; Enter now refuses, a Stop closes an open dialog, and mouse and keyboard commands are refused while a dialog is open.
- Folder checks: folders managed from Sophon are checked on the node, which refuses whole drives, the home folder, hidden home folders, AppData, Library, system folders and network, device and short-name paths, with the reason shown in the Dashboard.
- Timeouts cancel: when the agent stops waiting for a node command, the Gateway cancels it on the device and an open confirmation dialog closes, so a late approval no longer runs it.
Themes
- Six more Dashboard themes: Sophon Code, Sophon Code Light, Sophon Code Dimmed, Sophon Code High Contrast, Catppuccin Mocha and Dracula, for eleven in all, grouped in Settings → Appearance as Sophon Core, Sophon Code, Community and Automatic (System).
- Sophon Core names: Daylight is now Core Light, Indigo Core is Core Dark and Deep Void is Core Extra Dark on every client, with no colour change; Graphite keeps its name.
- The CLI ids follow: core-light, core-dark and core-extra-dark, with daylight, indigo-core and deep-void accepted permanently.
- Nothing saved changes meaning: the Dashboard keeps its stored theme values and its default stays Core Dark. The names are shared, but each client keeps its own colours.
Agent packages
A package agent stays third-party for its whole life: no standing auto-approval covers its turns, its heartbeat auto-approves up to Low, and the router never picks it on its own. Publishing agents needs the marketplace’s agent release in production.
- A third package type: agents, made of persona files and a manifest with no code, join skills and plugins in the Marketplace, installed from the marketplace or from a .sophon-agent file.
- One preview everywhere: the Dashboard install dialog, sophon agents install and the chat card show the same preview (persona files, the injection scan, required skills and tools, the settings the agent will get), and an install creates the agent with its heartbeat, auto-approve, planning and any model pin off.
- Your edits survive updates: an edited agent pauses its updates until you review a three-way diff, and agents update one at a time, never through Update all.
- Found when needed: the model can search the marketplace for an agent when it needs a specialist and asks before installing one, on a High-risk card that can be approved only in the Dashboard, after opening its full preview.
- Withdrawn versions stop: when the installed version is revoked or the package removed, the agent stops until you keep using it or take another version, and Sophon sends one security notification.
- Export and publish: any agent can be exported as a .sophon-agent file and published through the linked marketplace account; sophon agents search, install, updates, update, export and publish, and sophon dev new, validate, build, install and publish, understand agent projects.
Removed and deprecated
- Discussions removed: the multi-agent debate feature is gone, with no replacement: its Dashboard and Mobile screens, the discussion.run tool, the action.discussion workflow node, sophon discuss, its push category and its webhook events. Past discussion sessions stay as ordinary chats, and <dataDir>/discussions stays on disk, unread.
- /api/discussions/* answers 410 feature_removed, except four list routes that answer [] until v2.3.0, and the CancelDiscussion hub method and Discussion* events are gone.
- Thinking removed: /thinking, --thinking and the cli.json defaultThinking are replaced by /effort, -e/--effort and defaultEffort.
- CLI slash commands removed: /provider, /quit, /select, /tokens, /info, /tasks, /approvals, /agents, /sessions and /auto-approve, replaced by /model, /exit, F2, /context, the /agent and /resume pickers, /permissions and the sophon tasks and sophon approvals commands.
- Deprecated: the WorkflowProgress hub event, removed in v2.3.0 (listen to WorkflowRunUpdated), and legacy agent.json dev projects, which sophon dev build and sophon dev publish refuse.
Security
- Workflows scoped to tenant and owner: workflow routes, the agent’s workflow tools and live run events are tenant-scoped, non-Admins can edit, run and delete only their own workflows, and every run executes as the workflow’s owner with the owner’s credentials, whoever started it.
- Workflow writes need a role: on Pro and Enterprise, Viewers lose workflow create, edit and run, and new users get Viewer by default.
- Confined effects: the file node stays inside <dataDir>/workflow-files/<tenant>/<user>/ and its create no longer overwrites, Send message uses only the owner’s or a same-tenant Admin’s channels, and a sub-workflow must have the run’s owner.
- Substitutions encoded: values put into URLs, headers, JSON bodies and skill parameters are encoded for where they land, and code steps refuse {{ }} references on webhook and channel runs.
- Untrusted text marked: fetched and trigger text is wrapped in <external_content> markers inside prompts and flagged on approval cards, and under Block a step whose fetched output trips the prompt-injection detector fails.
- Agents in their tenant: every /api/agents/{id} route checks the caller’s tenant, delegation and agent tools no longer reach another tenant’s agent, and file tools refuse reads and writes under <dataDir>/agents, marketplace, vault and security. Shell tools that a person approves are not covered.
- Node files protected: filesystem commands can no longer reach ~/.sophon-node, network, device, short-name and NTFS stream paths are refused, and config.json is readable by its owner only after each write on macOS and Linux.
- Rotate token and Revoke now take the device’s current connection out of command delivery before they answer.
Fixes
- E-mail channel: each unread message is delivered once instead of on every poll, and once more after a restart; mail sent from the channel’s own address never starts a workflow.
- The email-summary template now passes its summary to the send step, tests the branch for matches and searches for “action required” in the subject.
- Workflow builder: an edge whose condition is the empty string is kept instead of becoming unconditional on the next save, and Save keeps a switched-off workflow switched off instead of switching it on.
- Sophon Node: on macOS and Linux a stopped or timed-out command now ends its helper process and everything it started, where a stopped shell command used to keep running; "consentRequiredCommands": null loads the defaults instead of stopping the node; and sophon-node pair exits 1 when it fails.
- sophon agents soul <id> --edit and --from-file work again.
- CLI: on the pinned and classic chat a multi-line paste arrives as one edit instead of being sent line by line.
Upgrade notes
- Back up the database and the data directory before upgrading: the first start of the v2.2.0 Gateway applies two migrations, AddWorkflowRuns and AddNodeSettings. They only add tables and indexes, but there is no down-migration, so the way back to 2.1.x is restoring that backup. The backup also keeps <dataDir>/discussions, which 2.2.0 no longer reads.
- Upgrade every client: the Gateway with its Dashboard image first, then the CLI, Sophon Node and Mobile. Until a v2.1.x client is upgraded, its explicit Thinking pick, including a CLI defaultThinking of off, fast or full, overrides every stored effort, and a Dashboard or Mobile app that does not see effort.v1 shows no effort control.
- Discussions: let running discussions finish or cancel them with sophon discuss cancel before upgrading the Dashboard and the CLI, since no client can cancel one afterwards. Replace every action.discussion workflow step (the builder’s Replace with LLM Prompt), rewrite prompts and personas that call discussion.run, and expect webhook registrations for discussion.completed or discussion.failed never to fire again.
- Workflow runs in flight at the upgrade show as Interrupted and are not resumed: re-run them by hand, and run one Gateway per database. v2.1 history is imported once, a minute after the first start; on Pro, first delete <dataDir>/workflows/history/<id>/ for any id another tenant or owner re-created, or create history/.imported-v1.json to skip the import. Insights workflow counts change.
- Every workflow run is now stored, about 1,440 a day for a one-minute schedule, and pruned after 30 days, keeping the newest 20 and at most 500 per workflow. To keep more, set SOPHON__Workflows__Runs__RetentionDays, MinRunsPerWorkflow or MaxRunsPerWorkflow before upgrading, and raise MaxRunningRunsPerUser on Personal if you run more than 8 at once.
- Pro and Enterprise: Viewers lose workflow create, edit and run, and new users get Viewer by default (grant Operator, or set SOPHON__Tenant__DefaultRole=Operator). Workflows are owner-only for non-Admins, so transfer ownerless and departed users’ workflows with POST /api/workflows/{id}/owner. Every run executes as the owner, run visibility narrows to the run’s user, its requester and same-tenant Admins, and a workflow webhook hears only runs its creator may read.
- Saves are validated: workflow ids outside the allowed characters, unknown node types, and new steps with invalid ids or references to steps that do not exist are refused. Trigger types that cannot fire (file_change, calendar_event, agent_request) never fire and are refused on new saves, so change them.
- Edge conditions are normalized on any save, the enable switch included: True becomes true and Approved becomes approved, so an if/else or approval branch that never ran starts running. Check what such a branch does before you save. A step fed by both if/else branches now runs once, logic.merge outputs only its taken inputs, and graph exports with a re-approval gate need re-exporting.
- Loops and branches: re-connect every Loop step (the steps to repeat on body, the next step on done), since existing Loop steps fail until re-connected; a workflow with a Parallel step now runs branches concurrently, so connect order-sensitive steps or set settings.maxConcurrency to 1; and new workflows fail an unresolved reference instead of sending literal text.
- Workflow steps: move file-node outputs into <dataDir>/workflow-files/<tenant>/<user>/, recreate channels Send message uses under the owner or an Admin, have code steps on webhook and channel runs read SOPHON_TRIGGER_DATA, SOPHON_INPUT_DATA or SOPHON_NODE_DATA, raise maxResponseBytes for API Call bodies over 1 MB and timeoutMs on skill steps whose tool asks for approval, and check workflows you had switched off, since Save no longer switches them on.
- Triggers and notifications: keep one enabled channel config per type across all tenants, set routing.debounceEnabled to false on an e-mail channel that starts workflows, and keep /webhooks/in behind TLS with an allowlist and a rate limit. Outbound workflow.completed and workflow.failed webhooks and failure pushes start firing: check the registrations and pause schedules that fail often.
- Custom clients: register a handler for WorkflowRunUpdated; WorkflowProgress reaches only the run’s user and requester and is removed in v2.3.0. Accept new members such as runId and issues, handle 400 workflow_invalid, 403 not_workflow_owner, 409 effect_confirmation_required and 429 too_many_runs, read step results by nodeId, and expect sophon workflows execute to exit by the run’s outcome. /api/discussions/* answers 410 feature_removed.
- Effort shifts cost: unattended turns and background calls now run at Low, interactive chat at Medium and coding turns at High, so models that did not reason unless asked now do on some turns, and models with a higher default reason less. Set an explicit level on the agent or host, or lower Sophon:Models:EffortAutoCeiling, to hold it down. OpenAI reasoning models no longer receive temperature or top_p, and Claude models drop temperature while they think.
- Egress rules: OpenAI’s newest models (GPT-5.6, GPT-6, the -pro and -codex models) now call /v1/responses on api.openai.com, and Anthropic API-key requests carry the official SDK’s User-Agent and X-Stainless-* headers. A custom OpenAI-compatible endpoint sends no effort field until its models.json provider entry sets "effortWire".
- Effort in scripts and clients: /thinking is /effort, sophon exec --thinking exits 1 (use -e/--effort), and cli.json defaultThinking is read as defaultEffort (off → Low, fast → Medium, full → High) until sophon config set defaultEffort rewrites it. Headless NDJSON and every reply’s routing gain effort and effortSource, an unknown level in SendMessage is refused with EFFORT_INVALID, and LlmRequest.Thinking is gone for in-process hooks.
- CLI commands: /provider, /quit, /select, /tokens, /info, /tasks, /approvals, /agents, /sessions and /auto-approve are removed, so update scripts that pipe them into sophon (/provider <id> <model> becomes /model <id>:<model>). Bare /permissions, /export, /mode and /trust open dialogs; pass an argument where you expect printed output. The default theme is now sophon-code: run sophon config set theme core-dark to keep the old look.
- CLI terminal: Ctrl+H now deletes the previous word, so set a terminal that sends ^H for Backspace to send DEL; image paste on Linux needs wl-clipboard or xclip on PATH; and the full-screen chat tints the terminal background (opt out with SOPHON_CLI_TERMINAL_BACKGROUND=0). Images attached in chat are stored base64 in session events up to 5 MiB each, so set Sophon:Documents:InlineImageMaxBytes to 0 to keep the text-only behaviour.
- Allow all tools and git status: before turning on Sophon:ApprovalPolicy:AllowAllMode, update the CLI and the Dashboard with the Gateway, and on Pro keep the Admin role narrow. When gh is signed in as the Gateway’s OS user, the Gateway looks up pull requests with that one GitHub identity for every trusted workspace; set Sophon:Workspace:PullRequestLookup=false to stop it.
- Sophon Node devices: the confirmation dialog’s default is now No (Reject on Linux), mouse and keyboard commands are refused while a dialog is open, and on macOS and Linux a stopped command ends everything it started. Rename a filesystemRoots key in config.json to fileSystemRoots, run chmod 600 ~/.sophon-node/config.json, and replace network, short-name (PROGRA~1) and NTFS stream paths, which are refused. A node running as a LocalSystem service reads the system profile, so lock that one.
- Node settings from the Dashboard: an admin who does not own a device can no longer loosen its settings, app.launch with arguments is admin-only on the manual Send command route, and Sophon:Nodes:AllowConfirmationsOff=false forbids turning confirmations off. When the agent stops waiting the command is cancelled on the device, so raise timeoutSeconds for longer work; after Rotate token, put the new token in config.json and restart the node; after downgrading the Gateway, run sophon-node settings reset on a managed device.
- Themes: the CLI saves new choices as core-light, core-dark and core-extra-dark and prints those ids. A v2.1.x CLI does not know them, so to share cli.json with one, save the old id (daylight, indigo-core or deep-void), which 2.2.0 still accepts and never rewrites.
- Agent packages: update DevStudio to 1.1.0 or later with the CLI, migrate legacy agent.json dev projects with sophon dev new agent (build and publish refuse them), start the Gateway before sophon dev install of an agent project, and approve agent installs in the Dashboard, since chat channels, Mobile and the CLI can only reject them. Re-link the marketplace account to publish from Sophon.
- Agents and tenants: every chat’s prompt cache misses once after the upgrade on a Gateway with the marketplace on; a workflow that named another tenant’s agent stops working, so recreate the agent in that tenant; turning on heartbeat autoApprove or allowPlanning needs ManageSkills; and an agent or workflow that edited SOUL.md through fs.write must use agent.update or the persona routes, since file tools refuse Sophon’s data folders.