Manifest and Environment

The DPU runtime is intentionally small. Most of its operational behavior comes from a short manifest and a few storage-related environment variables.

Why Configuration Matters

The agent only works correctly if it can find the workspace boundary, the DPU storage root, and the master key used to encrypt secrets and confidential content. In Ploinky, the DPU master key is derived from PLOINKY_DERIVED_MASTER_KEY through the manifest runtime-resource contract, so it remains stable without manual secret configuration.

Manifest

manifest.json declares a single default profile on top of node:24.15.0-alpine. Runtime resources provide persistent storage and derive the DPU key:

{
  "container": "node:24.15.0-alpine",
  "lite-sandbox": true,
  "runtime": {
    "resources": {
      "persistentStorage": { "key": "dpu-data", "containerPath": "/dpu-data" },
      "env": {
        "DPU_DATA_ROOT": "{{STORAGE_CONTAINER_PATH}}",
        "DPU_WORKSPACE_ROOT": "{{WORKSPACE_ROOT}}",
        "DPU_MASTER_KEY": "{{derivedMasterSecret:DPU_MASTER_KEY}}"
      }
    }
  },
  "profiles": {
    "default": {
      "env": [
        "ASSISTOS_FS_ROOT",
        "WORKSPACE_ROOT"
      ]
    }
  }
}

Environment Variables

Variable	Role
`DPU_MASTER_KEY`	Encryption root for secret values and confidential file content, derived from `PLOINKY_DERIVED_MASTER_KEY` through `{{derivedMasterSecret:DPU_MASTER_KEY}}`.
`DPU_DATA_ROOT`	Optional explicit storage root. If missing, storage falls back next to the resolved workspace root.
`DPU_WORKSPACE_ROOT`	Preferred workspace root for DPU resolution.
`ASSISTOS_FS_ROOT`, `WORKSPACE_ROOT`	Fallback workspace-root inputs used when `DPU_WORKSPACE_ROOT` is not set.

Standalone Mode

The standalone entry point is server/standalone-mcp-server.mjs. It serves POST /mcp and GET /health, while reusing the same mcp-config.json and tool dispatcher as the embedded runtime.