Ploinky and Explorer Integration
The agent is wired for Ploinky runtime and consumed by Explorer-oriented user interface (UI) flows. It acts as communication path between UI actions and SOPLang execution.
Ploinky Integration Model
Ploinky starts AgentServer for soplangAgent, applies lifecycle settings from soplangAgent/manifest.json, and exposes the tool surface declared in soplangAgent/mcp-config.json. From the UI side, browser clients call the MCP endpoint at /mcps/soplangAgent/mcp, which keeps transport concerns outside the SOPLang layer.
AssistOSExplorer Bridge
The practical target UI is the file explorer repository (.ploinky/repos/AssistOSExplorer). soplangBuilder exposes tool APIs that Explorer can call without embedding SOPLang runtime concerns in the frontend.
In this setup, soplangBuilder is backend orchestration and Explorer is interaction surface.
IDE-plugins Channel
The special folder soplangAgent/IDE-plugins/ contains UI plugin bundles injected into Explorer. This is the agent-to-UI extension mechanism.
| Artifact | Purpose |
|---|---|
IDE-plugins/open-builder-button/config.json |
Registers plugin at file-exp:toolbar location. |
IDE-plugins/edit-variables/config.json |
Registers variable editing surfaces as agent-owned document plugins. |
IDE-plugins/run-script/config.json |
Registers SOPLang script execution modal as an agent-owned plugin. |
IDE-plugins/open-builder-button/open-builder-button.js |
Opens build UI page at /soplangAgent/web/build-status.html. |
web/build-status.js |
Calls tools over MCP and streams build/task updates. |