Use iPolloWork
A practical map of the local-first agent workspace, from a task to an editable result.
iPolloWork is a local-first desktop workspace where an agent can work across a repository, files, the browser, design artifacts, and video compositions. It is not a separate “chat for each tool.” A session keeps the task context while you move between the work surface that matches the output.
The project is source-available and can run as a desktop app, browser UI, or headless server. Cloud connection is optional for local work.
A session retains the task context while the output moves into the surface where it can be inspected and changed.
- 01Intent
Describe an outcome, add files, or open a repository.
- 02Agent run
The local server plans, uses tools, and streams the work.
- 03Work surface
Review code, browser output, design artifacts, or video scenes.
- 04Direct revision
Edit the result and continue from the same session context.
Pick the right surface
| Surface | Use it when | What remains editable |
|---|---|---|
| Code and files | A task changes a repository, document, or local file set. | Files, diffs, tool output, and the session history. |
| Design | The result is a site, interface, slide, report, or visual artifact. | HTML, CSS, assets, tokens, text, layout, and responsive states. |
| Video | The output is a HyperFrames composition or editable video scene. | index.html, scene structure, composition variables, assets, and timeline data. |
| Browser | A task needs a real web page, a connector flow, or web research. | Browser state, tool trace, and the task instructions. |
Start locally
Install the requirements listed in the repository: Git, Node.js 22 or newer, pnpm 11 through Corepack, and Bun 1.3.10 or newer. On macOS and Linux, use the repository launcher:
git clone https://github.com/Devin-AXIS/iPolloWork.git
cd iPolloWork
corepack enable
./ipollowork setup
./ipollowork dev
On Windows PowerShell, use ipollowork.cmd instead:
git clone https://github.com/Devin-AXIS/iPolloWork.git
Set-Location iPolloWork
corepack enable
.\ipollowork.cmd setup
.\ipollowork.cmd dev
setup installs the locked workspace dependencies. dev prepares the OpenCode and Orchestrator sidecars, starts the UI, and opens the Electron client in an isolated development profile.
Follow the normal work loop
- Open or create a session for one outcome.
- Give the agent the goal, constraints, and any local files or URLs it needs.
- Inspect the running work in the appropriate surface rather than waiting for a prose-only answer.
- Make direct edits when the output is visual or structured.
- Ask the agent to continue with the edits as new context.
- Validate the narrow change before moving to a broader task.
The next guides cover System architecture and Runtime lifecycle, the editable Design and Video workflows, then the session, tool, and model boundaries behind them.