iPolloWork Docs
Use iPolloWork

System architecture

Ownership of the work surface, local runtime, editable files and external tools.

iPolloWork organizes goals, context, tool activity and artifacts in a session. Project files stay in the workspace; designs and videos retain editable project structure. Configure the model provider, execution engine and external tools separately.

Local task pathFrom input to an inspectable result
  1. 01Work surface

    Desktop and browser views present chat, files, Design, Video and review.

  2. 02Local server

    Workspace APIs own configuration, approvals, extensions and artifact access.

  3. 03Execution engine

    Supported interfaces connect the runtime, tools, Skills and MCP.

  4. 04Editable files

    Keep source, assets and project structure for review and revision.

Check three boundaries separately

BoundaryVerify
Model providerEndpoint, account or key, model ID, quota and transmitted context.
Execution engineOpenCode, DSH or Codex Harness version, accounts, tools and runtime requirements.
Collaboration and outputSession context, file access, real delegation records and editable results.

Integration principles

  1. Use the owning server for workspace operations.
  2. Access OpenCode through supported CLI, API, plugin and configuration interfaces.
  3. Verify a remote Worker and a model API separately: one executes tasks, the other provides inference.
  4. Keep credentials in their owning configuration, outside templates, logs and artifacts.
  5. Inspect actual exports and editable projects after checking the preview.

Continue with runtime lifecycle, Local Server reference and the ecosystem guide.