MCP servers and extensions work in open sessions from the next message
5 features · 53 fixes · 3 performance changes
Features
MCP servers and extensions work in open sessions from the next message
Adding, enabling or signing in to an MCP server, or installing or enabling an extension, now makes its tools callable in the sessions you already have open, from your next message. You no longer stop, resume or fork a session to pick up a server, and forks, continued sessions and child sessions follow the current server set too. Removing, disabling or signing out withdraws the tools on the next call. When a runtime can't refresh its tool list by itself, CompozyOS reloads it once before your message, keeps the conversation, and records one quiet "MCP servers updated" line in the transcript. If the runtime can't start, the message is not sent and goes back to the composer; send it again to retry.
Each session shows which servers it can use. The new MCP control in the composer, compozy session mcp <id> and the compozy__session_mcp_list native tool list every configured server with
its state (Ready, Applies on your next message, Needs sign-in, Waiting for approval, Couldn't connect,
Not available in this session) and the action that fixes it.
Runtime MCP servers. Settings → MCP servers and Marketplace → MCPs now also list, read-only, the MCP
servers each coding agent CLI loads from its own files (Claude Code, Codex, Gemini CLI, OpenCode, Kimi
CLI, Qwen Code, GitHub Copilot CLI, Cursor Agent, Antigravity and Pi), grouped by runtime. CompozyOS
only reads those files: it never edits them, runs the runtime, connects to the servers or reads a
keychain. Copy to CompozyOS (compozy mcp import <runtime>/<server>) turns a runtime server into a
CompozyOS server, storing its values as Vault secrets. The new [providers.<id>] runtime_mcp = "off"
setting, also a switch in Settings, stops Claude Code, GitHub Copilot CLI or Qwen Code from loading
their own servers in CompozyOS sessions, from each session's next message.
New CLI verbs compozy mcp list, compozy mcp allow, compozy mcp import and compozy session mcp,
native tools compozy__mcp_list, compozy__mcp_allow, compozy__mcp_import and
compozy__session_mcp_list, and the matching HTTP/UDS routes are additive.
Migration
- Project MCP servers need approval. A server declared in a project's files
(
.compozy/mcp.json, the project'sconfig.toml,.compozy/profiles/<name>/…, or an agent or skill folder inside the project) now waits for your approval, bound to its exact definition, before any session can call it. Allow it with Allow in Settings or the session's MCP control, orcompozy mcp allow <server> --workspace <project>. Editing the definition asks again. Servers you add through CompozyOS, servers in your own~/.compozyfiles and servers of enabled extensions need no approval. - Unapproved project servers no longer start. Before this release, CompozyOS could start an unapproved project stdio server during tool discovery or a Settings status probe. A server waiting for approval is now never started, connected to or signed in to.
external_default = "ask"is stricter for project servers.tools.policy.external_defaultkeeps its values and default, but now applies only to servers without your consent. Withask, an unapproved project server used to be callable after a per-call prompt; it now waits for approval and is never started. Servers with consent still prompt on each call underask.enabledstill admits project servers without approval.external_default = "disabled"no longer blocks servers you set up yourself. Withdisabled(the default), only project servers waiting for approval stay blocked. Servers you add through CompozyOS, servers in your own~/.compozyfiles, servers of enabled extensions and project servers you allowed are now callable. If you relied ondisabledto block every external MCP server, disable or remove the servers you don't want sessions to use.- Spawned sessions inherit the parent's MCP servers and tools by default. A child session or subagent spawned without an explicit MCP server or tool list now follows its parent's current servers and tools instead of starting with none. It never gets more than its parent. To keep a child narrower, name its MCP servers and tools when you spawn it.
- Session MCP limits are stored as intent. Stored sessions and always-on instance ceilings are upgraded in place by an automatic database migration that records whether each one follows the current server set or keeps an explicit list. Nothing is lost, and archived sessions and stopped instances are covered. Rows written by an older binary during a downgrade window are still read correctly by a compatibility decoder in this release and the next one; that decoder is removed in the release after next. Upgrade through this release (or the next) before skipping further ahead with a database an older binary wrote to after this upgrade.
- Existing v0.7.0 sessions keep their access. The corrective migration also covers databases that
already applied the initial intent backfill in a development build. Empty provenance policies and
older root budgets without materialization flags follow the current native, extension and MCP
catalog. Forks, continued sessions and recovery sessions refresh their native tools too. Spawned
and coordinator limits, explicit
allowed_toolsprofiles, ancestor ceilings and lists authored after the intent upgrade remain enforced. After upgrade, legacy descendants without a spawn marker may gain access to additional tools and servers within their always-on instance's ceiling. Delegated sessions never exceed their instance ceiling. - The public lineage
permission_policy.mcp_serversnow reports the session's effective server list.
Fixes
Automation backoff retries unaccepted provider startup failures
retry.strategy = "backoff" again retries ACP startup, process-exit, handshake, and protocol
failures before session acceptance, including a crash at spawn, package preparation failure, or
session/new error. The existing retry count and delay apply, including to repeated typed startup
configuration failures. A provider that already accepted the session is never started again by a
startup retry. Cancellation, authentication failures, errors without an ACP startup classification
(such as agent-definition validation), and cleanup that retains ownership stay terminal. Exhausted
retries preserve the final failed session and diagnostics.
Delete archived history whose session files are missing
Archived sessions retained after their files disappear can now be deleted explicitly or through archived history cleanup. Cleanup reports a deletion only when the catalog entry was removed or confirmed already gone.
Extension replacement respects profile ownership before publication
An agent can replace a local extension only when every installation belongs to its workspace and its own profile or all profiles. An attachment in another profile requires operator authority. Replacement also resolves the selected installation before staging, so a denied or missing target never temporarily publishes candidate code to another installation.
Keep layout changes when the page reloads
Tab pins and other accepted layout changes now finish saving when the page reloads immediately after the change.
Project configuration cannot grant MCP consent to itself
Security change: workspace and workspace-profile configuration can only restrict inherited external
tool policy. tools.policy.external_default keeps the stricter value (disabled before ask before
enabled), and trusted_sources retains only entries already trusted by the preceding layer.
Omitting the trust list inherits it; an empty list removes all trust. Attempted project grants are
ignored with one warning per daemon process. Put intentional grants in user or personal profile
config. Project files and existing explicit server approvals are preserved.
Narrow inherited child tools to the parent agent's permissions
Spawning a less restricted child agent with default inheritance now narrows any broader effective tool set to the parent's permissions. Explicit requests for tools outside the parent's permissions are still refused.
Preserve subagent CLI error compatibility
compozy session subagents list, show and cancel keep the v0.7.0 exit code 1 for daemon errors and print each error once, including when a workspace is selected explicitly.
Keep subagent completion wakes flowing after deletion
Deleting the only result in a queued subagent completion now cancels the empty wake completely, so later subagents can still wake their parent.