iPolloWork Docs
Use iPolloWork

Workspace and agents

Understand the session, local runtime, files, browser, and permission boundaries behind each task.

An iPolloWork session is the durable context for a task. It connects the conversation to files, tool runs, browser state, generated artifacts, and the surface currently open in the workspace.

Session ownershipA session is a work boundary, not just a conversation thread

The session relates intent, tool activity, and one editable artifact surface without turning every task into a global workspace mutation.

01
Intent

What should happen

Task outcome

A clear requested result, owner, repository or workspace, and review expectation.

Conversation

Context and decisions that should stay attached to the task.

02
Execution

How it happens

Local runtime

Routes task work through the local server and supported OpenCode sidecar.

Tools

Files, browser, Skills, plugins, and MCP calls remain attached to the task boundary.

03
Artifact

What can be reviewed and edited

Work surface

Code, Design, Video, browser output, or another session-owned result.

Activity evidence

The result is re-opened and checked in the surface that owns it.

What stays in the session

LayerResponsibility
SessionTask instruction, conversation, activity, and the current work context.
Local serverRoutes agent requests, manages local project state, and exposes the local API.
OpenCodeExecutes the underlying agent runtime and can be upgraded independently.
Work surfacesRender and edit code, design artifacts, video compositions, browser work, and task output.
PermissionsMake requested file, browser, tool, and connector actions visible before they execute.

Keep work scoped

Create a new session when the task has a different repository, owner, outcome, or permission boundary. Keep follow-up revisions in the existing session when they modify the same artifact or decision.

This separation is especially important for Design and Video. Their artifacts are owned by the session so that a new task cannot silently alter a previous project.

Use a new session when any of the following changes: the workspace path, the user or team that owns the work, the main output, the expected permission level, or the artifact type. Keep the same session for a review, correction, extension, or alternate version of the same work. This avoids losing relevant context while preventing a broad, ambiguous session from acquiring authority over unrelated work.

Use tools deliberately

Skills, plugins, MCP servers, and browser automation are extensions of a task. Add only the capability needed for the outcome and keep its authorization narrow. If a task needs a custom model or MCP server, configure it first in Models, tools, and MCP.