Agent Dock is in private preview. See what we’re building
LOCAL-FIRST AGENT OPERATING ENVIRONMENT

Your agents, coordinated.
You stay in control.

Agent Dock brings specialist agents, replaceable intelligence, connected tools and explicit authority into one persistent desktop environment.

AGENT DOCK / ACTIVEWORKSPACE · LAUNCH
Create launch visuals from this campaign brief.
campaign-brief.pdf1.8 MB
AD
AGENT DOCKRouting visual production to Studio.

I can handle the brief and messaging here. Studio is the strongest installed match for the final visual system.

96%

Agent Dock Core routes work, validates local actions, resolves specialist capability, and keeps privileged execution behind explicit approval and audit.

01PRODUCTTHREE INTERACTION DEPTHS

A desktop operating environment.
Not another chat window.

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.

01 / COLLAPSED DOCKAMBIENT
ACTIVE Repository Engineer 2 approvals

Presence without interruption.

Status, attention, notifications and the active agent stay visible without turning the notch into a miniature dashboard.

03 / CONTROL CENTERMANAGEMENT
CONTROL CENTERAgentsMarketplaceConnectionsIntelligenceActivity / Audit

Configuration gets its own space.

Installed agents, provider routes, Connections, permission policy, audit and diagnostics belong in a durable management surface.

THE NOTCH IS THE FAST SURFACE — NOT THE WHOLE PRODUCT.

Agent Dock stays persistent without forcing every workflow into the same small window.

02HOW IT WORKSAGENT ≠ MODEL
CAPABILITY SYSTEM

The agent stays itself.
The intelligence can change.

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.

01
Core receives the work

Agent Dock owns the local workspace, task state and routing boundary.

02
A specialist declares capability

Agents advertise skills and requirements instead of being hard-wired to a vendor.

03
Intelligence resolves separately

Required agents can use any compatible connected provider route.

04
Authority is checked last

Connection assignment, permission policy and PAG remain independent gates.

EXECUTION / SPECIALIST PATHDEFAULT DENY
USERPrepare a sourced competitor brief.task intake
↓
COREAgent Dockroute · validate · retain task state
↓
AGENTResearcherresearch.web · source.compare
INTELLIGENCECompatible providerchat.generate · tools.invoke
CONNECTIONBrowser / assignedread
↓
PERMISSION + PAGbrowser.read / per-taskexact privileged payload when required
AGENT IDENTITY UNCHANGEDAUDIT RECORDED
No model required?Direct Actions and deterministic agents can take the shorter path: Core → validated local action → permission/PAG boundary when needed.
03MARKETPLACEPRIVATE PREVIEW

Install capability.
Grant nothing by accident.

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.

CATALOGUE / BUNDLED3 PREVIEW AGENTS
INSTALL REVIEWEXACT PAYLOAD
KALULABS PREVIEW · BUNDLED CATALOGUEResearcher

Review what this agent declares before installation.

INTELLIGENCE
required · tools.invoke
CONNECTION
Browser · required
PERMISSION
browser.read · low risk
INSTALL RESULT
installed disabled
NO PERMISSION GRANTSNO CONNECTION ASSIGNMENTSNO PROVIDER BINDING

Public publisher profiles, publisher verification and hosted submissions are future infrastructure.

04INTELLIGENCEREPLACEABLE REASONING
ROUTING, NOT IDENTITY

Change the intelligence.
Keep the agent.

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.

WORKSPACE CONTEXTSYNCED

Agent Dock Website

37decisions
14files
26tasks
CURRENT TASKRefine the Agent Dock landing experience

Relevant context is reconstructed for whichever provider is active.

ACTIVE INTELLIGENCEChatGPT plan

workspace unchanged · agents unchanged · grants unchanged

05CONNECTIONSCONNECTED ≠ ASSIGNED ≠ AUTHORIZED

Connect the resource.
Delegate it deliberately.

A GitHub account, browser, Figma workspace, filesystem scope or MCP server can exist in Agent Dock without becoming available to every installed agent.

01 / AVAILABLE TO AGENT DOCK
Browserlocal adapter · connectedCONNECTED
GitHubvictorkay97 · connectedCONNECTED
Figmadesign workspace · connectedCONNECTED
≠
02 / ASSIGNED TO RESEARCHER
Browserrequirement: browserASSIGNED
GitHubnot requestedUNASSIGNED
Figmanot requestedUNASSIGNED
≠
03 / AUTHORIZED CAPABILITY
browser.readtask-scoped policyASK
browser.writeno grant existsDENY
credentials.rawnever delegatedDENY
CONNECTION SURFACES
GitHubrepos · PRs · issues
Browserread · local context
Filesystemscoped local access
MCP / APIsextensible services
06PERMISSIONS + PAGHUMAN IN THE LOOP

Permission to request.
Approval to execute.

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.

APPROVAL REQUESTHIGH IMPACT
BIPAIPublish to X?
ACCOUNT
@kalulabs
CAPABILITY
social.x.publish
POLICY
ask every time
EXACT PAYLOAD

“Agent Dock keeps your workspace context separate from the model provider…”

ACTIVITY / LIVE
Studio returned 3 launch assets

files saved to workspace

Agent Dock routed work to Studio

poster.design · 96% match

BIPAI requested social.x.publish

waiting for approval

Intelligence route changed

agent identity and grants preserved

07CONTROL CENTERMANAGE THE SYSTEM

The Dock is for work.
Control Center is for governance.

Long-lived configuration belongs in a dedicated management surface: installed agents, Marketplace state, Connections, Intelligence routes, Activity/Audit and desktop settings.

CONTROL CENTER / HOMESystem overview
RUNTIME HEALTHY
INSTALLED AGENTS032 ready · 1 configure
CONNECTIONS064 connected · 2 local
INTELLIGENCE031 active route
APPROVALS02payload-bound
INSTALLED AGENTSLIFECYCLE
Researcherready
Repository Engineerenabled
Studioconfigure
RECENT AUTHORITYAUDIT

provider.changedResearcher · direct route

connection.assignedBrowser → Researcher

approval.pendinggithub.pull_request.create

01Core

host + routing

02Agents

specialist capability

03Intelligence

replaceable reasoning

04Connections

tools + accounts

05Permissions + PAG

authority + approval

08QUESTIONSDOCUMENTATION-GROUNDED

Read the boundary.
Or ask the product.

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.

AGENT DOCK / PRIVATE PREVIEW

One environment for agents.
One place for you to stay in control.

Install specialist capability, connect the intelligence and resources it needs, and keep delegated authority explicit.

Back to the Dock Explore agents