Manifest and Environment

The agent follows the Ploinky manifest standard and relies on a minimal set of environment variables for runtime behavior.

Manifest

Main configuration file: soplangAgent/manifest.json.

{
  "lite-sandbox": true,
  "container": "node:24.15.0-bullseye",
  "profiles": {
    "default": {
      "env": ["ACHILLES_DEBUG", "SOUL_GATEWAY_API_KEY", "SOUL_GATEWAY_BASE_URL"]
    }
  }
}

The lite-sandbox flag asks Ploinky to prefer the host sandbox runtime when available. The container field remains the fallback image used when host sandboxing is disabled, and profiles.default.env declares forwarded environment variables used by the agent.

Environment Variables

Variable	Usage
`SOUL_GATEWAY_API_KEY`	Used for LLM calls through SOPLang/LLM plugin paths.
`ACHILLES_DEBUG`	Enables detailed debug logging via `plugins/debugLogger.mjs`.
`PERSISTENCE_FOLDER`, `LOGS_FOLDER`, `AUDIT_FOLDER`	Set by `soplang-tool.sh` for persistence and tool execution logs.

Plugin and Command Registration

At invocation time, the wrapper registers SOPLang plugins and then loads project plugins from soplangAgent/plugins/. During builder initialization, custom commands are registered (load, createJSCode, store), and Achilles skills are also registered as SOPLang commands.

Local Skills Folder

The repository includes soplangAgent/skills/ with local skill packages. These skills are discoverable and can be registered as commands through Achilles bridge, but they are not yet actively used in current Explorer workflows.

This keeps future extension points ready without changing MCP API contracts.

Test Validation

Repository validation is executed with npm test from soplangAgent/. Code changes are considered complete only after this test command passes.