Presence without interruption.
Status, attention, notifications and the active agent stay visible without turning the notch into a miniature dashboard.
Agent Dock brings specialist agents, replaceable intelligence, connected tools and explicit authority into one persistent desktop environment.
I can handle the brief and messaging here. Studio is the strongest installed match for the final visual system.
Agent Dock Core routes work, validates local actions, resolves specialist capability, and keeps privileged execution behind explicit approval and audit.
The Dock stays lightweight when you only need presence, expands when you are actively working, and opens into a full Control Center when configuration, authority or history needs more room.
Status, attention, notifications and the active agent stay visible without turning the notch into a miniature dashboard.
Conversation, active agent, files, voice, Direct Actions, current task state and exact approvals live together.
Installed agents, provider routes, Connections, permission policy, audit and diagnostics belong in a durable management surface.
Agent Dock stays persistent without forcing every workflow into the same small window.
An agent is the specialist capability system: its skills, workflows, tools, Connection requirements and permission requests. A model is only the intelligence source it may use.
Agent Dock owns the local workspace, task state and routing boundary.
Agents advertise skills and requirements instead of being hard-wired to a vendor.
Required agents can use any compatible connected provider route.
Connection assignment, permission policy and PAG remain independent gates.
The current Marketplace is a native private-preview catalogue. The host chooses the exact listing and manifest, validates it, shows the requested boundary, and installs the agent disabled.
Review what this agent declares before installation.
Public publisher profiles, publisher verification and hosted submissions are future infrastructure.
A provider route supplies reasoning. It does not become the agent, inherit its Connections, or rewrite its permission history. Provider-neutral agents keep their identity while Core resolves a compatible route.
Relevant context is reconstructed for whichever provider is active.
workspace unchanged · agents unchanged · grants unchanged
Standing permission policy and privileged execution are separate boundaries. The agent may be allowed to request a capability while PAG still requires approval for the exact consequential payload.
“Agent Dock keeps your workspace context separate from the model provider…”
files saved to workspace
poster.design · 96% match
waiting for approval
agent identity and grants preserved
Long-lived configuration belongs in a dedicated management surface: installed agents, Marketplace state, Connections, Intelligence routes, Activity/Audit and desktop settings.
provider.changedResearcher · direct route
connection.assignedBrowser → Researcher
approval.pendinggithub.pull_request.create
host + routing
specialist capability
replaceable reasoning
tools + accounts
authority + approval
No. Direct Actions and provider-free agents can perform deterministic local work without model reasoning. Agents that declare required intelligence need a compatible provider route before they can be enabled.
No. The model supplies intelligence. The agent is the specialist capability system around that intelligence—skills, workflows, tools, Connection requirements and permission requests.
For provider-neutral agents, the route can change while the installed agent, workspace, task history, Connection assignments, permission grants and audit history remain with Agent Dock.
No. Connecting an account only makes it available to Agent Dock. The agent still needs an explicit compatible assignment, and permission policy remains a separate default-deny boundary.
No. The current Marketplace is a native private-preview catalogue with host-selected exact install and update review. Public publisher profiles, verification and hosted submissions are future infrastructure.
Install specialist capability, connect the intelligence and resources it needs, and keep delegated authority explicit.