Ploinky and Explorer Integration
`dpuAgent` is not a standalone product surface in practice. It exists because Explorer and related plugins need a confidential backend with a stable Model Context Protocol (MCP) contract.
Integration With Ploinky
Ploinky hosts the agent through its manifest and exposes the tool surface defined in mcp-config.json. When Explorer or another caller invokes a DPU tool, the runtime executes tools/dpu_tool.sh and returns the serialized result of the corresponding DPU operation.
Integration With Explorer
Explorer uses DPU for the virtual confidential surface rather than for normal filesystem browsing. In code, the agent exposes the roots returned by getWorkspaceRoots(), including `/Confidential/My Space`, `/Confidential/Shared`, and `/Confidential/Secrets`. DPU comments and permissions are also surfaced through Explorer-side plugins instead of filesystem metadata.
Explorer Plugins
| Plugin | Role |
|---|---|
dpu-runtime-support |
Explorer runtime support and permissions modal integration. |
dpu-comments-popover |
Confidential comments user interface backed by dpu_confidential_comment_add, dpu_confidential_comment_delete, and dpu_confidential_get. |