Install an agent from a blueprint, then adjust its instructions and access before using it for recurring work.
Install an agent
Go to Workspace → Agents → Blueprints.
Open a blueprint and review the role, instructions, skills, and suggested connections.
Choose personal or organization use, name the agent, and select a home workspace when requested.
Complete installation and open the agent's control panel.
Write useful standing instructions
Describe the agent's purpose, expected outputs, constraints, and when it should ask for approval. Keep credentials and private keys out of instructions and memory.
Limit workspace access
Open Workspaces and allow only the workspaces the agent needs. A home workspace stores setup material; it does not automatically grant access to every resource.
Choose who can use an organization agent
Organization agents have a visibility setting:
Shared lets every member of the organization use the agent. Organization owners and admins can manage its configuration when their license permits it.
Just me keeps the agent private to its creator inside the organization.
Only the agent's creator can change this setting. Before changing a shared agent to Just me, review its schedules: Dokki immediately removes other members' access and pauses schedules they created.
Add skills and pinned context
Use Skills for repeatable procedures. Use Pinned for a small set of resources the agent should consider often. Update or remove them when the process changes.
Connect external tools
Use the Agent's MCP tab when this Agent needs a dedicated external MCP server. Add the server through its supported sign-in flow or paste a complete Workspace Connector URL when the server should be locked to one Dokki workspace.
Before enabling it:
Confirm who owns the external service or connector.
Grant the smallest external scope required.
Keep tokens and connector URLs out of Agent instructions, memory, and pinned documents.
Review the Agent's Workspaces list separately; an MCP connection does not expand Dokki access.
Run one manual, read-only test and inspect the result.
Review schedules before allowing unattended mutations.
Revoke or remove the connection when the Agent, owner, or workflow changes.
For a user's SaaS account such as GitHub, Gmail, or Slack, prefer Connect → MCP Apps. For an external AI client that needs to access Dokki, use Connect → AI Clients. See Connect for the overall direction and authorization model, and MCP Apps for external-account details.
Pause or uninstall
Pause an agent when it should stop accepting new work. Review schedules separately. Before uninstalling, save any outputs or instructions you need to keep, because uninstalling removes the installed agent.