Copilot is more than a chat box. It can call tools that read and change Dokki resources, search knowledge, publish content, generate media, schedule work, and use external apps.
Tool groups
Group | Examples |
|---|---|
Navigation and resources | List workspaces/resources; create, rename, move, delete, tag, and untag resources. |
Search and retrieval | Semantic search, exact grep, related entities, document/table/artifact reads, and web search when Exa is configured. |
Document editing | Read, insert, replace, rewrite, or delete document nodes. |
Table editing | Add/delete rows and columns, update columns, and update cells. |
Artifact editing | Read, replace, or patch artifact source. |
Image tools | Generate images and edit images when the image provider is configured. |
Publishing | Create/update publish sites, publish/unpublish resources, list published resources, manage custom domains, and check domain status. |
Tasks and schedules | Sync/read/clear chat todos and create/list/update/delete scheduled agent tasks. |
Agent-only tools | Pinned resources, IM messaging, and attention flags when running as an agent identity. |
External apps | Composio Tool Router tools for the acting user's connected apps. |
Tool availability
Copilot can see the tool schemas it may need for the turn, but each tool still performs its own permission, resource, and provider-configuration checks before doing work.
A visible tool does not mean the model can bypass permissions. It means Copilot knows the operation exists and can request it when the current user, resource, plan, and workspace context allow it.
Search and retrieval
Copilot can search semantically, grep exact strings, read documents, read tables, read artifacts, and use Knowledge Graph related entities when enabled. It can also use Exa-backed web search and URL crawling when EXA_API_KEY is configured.
Editing and creation
Copilot can create documents, tables, artifacts, and folders. It can edit documents, tables, and artifacts with resource-specific tools. For focused resources, the relevant tool family has the strongest local context, but Copilot can still operate on other accessible resources when given IDs or search results.
Code Sandbox secrets
Workspace admins can add environment variables under Workspace settings → Code Sandbox. Choose a short, descriptive name and enter the value. After a secret is saved, Dokki shows its name and update time but does not reveal the saved value. When a configured value appears in sandbox output, Dokki masks it.
Treat sandbox secrets as workspace-wide runtime credentials. Add only values needed by code running for that workspace, rotate them when access changes, and delete values that are no longer required.
MCP clients and connected apps
External MCP clients use Dokki's /mcp/v2 facade through OAuth, a dk_ tenant API key, or a Workspace Connector. The facade covers discovery, reads, creation, editing, sharing, Channel messaging, publishing, external apps, and rendered previews when the credential and acting identity permit them. Workspace Documents Connectors intentionally omit publishing, personal external apps, and global workspace actions.
MCP Apps are the opposite direction: Dokki calls an external service through the acting user's connected account. Selecting or @-mentioning an app narrows the external tools for that turn. Other workspace members do not inherit a personal connection. See Connectors, Clients, Workspace Connectors, and Connected Apps for the complete setup and authorization flow.
Connected app tools are account-scoped. Other workspace members do not inherit your personal connection.
Agent tools
Installed agents can run with extra tool families: agent schedules, pinned resources, IM tools, attention flags, and per-agent MCP servers. Agent MCP connection failures are non-fatal; Dokki records the failed server and continues with the tools that connected.
Permission boundaries
Tools do not bypass Dokki permissions. Private resources, inaccessible organization workspaces, archived workspaces, organization model controls, and public/private visibility rules are enforced before content is shown to the assistant or changed by a tool.