Our take
Activeregular commits and releases- Merges more pull requests than 94% of the projects we track
- Releases more often than 84% of the projects we track
iPolloWork is an actively maintained, multi-engine agent workspace with a broad creative scope, but its source-available license requires careful review before organizational or commercial use.
Good fit if
- You want one project workspace for OpenCode and optional Codex or DeepSeek Harness runtimes.
- Your workflow benefits from coordinating agent tasks and keeping generated creative outputs editable.
- You can work within the license terms, including obtaining written authorization for use by three or more people or for commercial services.
Look elsewhere if
- You need an OSI-approved open-source license or unrestricted commercial, hosted, or customer-facing use.
- You only need a single coding agent and do not need the multi-engine project workspace or creative editing features.
- You cannot use a Node.js-based development setup when building or developing from source.
All health signals
| Last commit | 2026-10-06 (1 day ago) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 37 (latest v0.50.21, 2026-09-24) |
| Contributors | 18 (top contributor: 39% of commits) |
| Issues closed, last 90 days | 0+ |
| Pull requests merged, last 90 days | 89 (typically merged in 0 days) |
| Project age | 14 months |
Checked on 2026-10-07 with the GitHub API.
Overview
iPolloWork is a desktop workbench for people and agent teams who want to manage projects across multiple AI agent runtimes in one place. It gives teams a shared view of tasks, execution, and results instead of requiring a separate project workflow for each engine.
It also extends the workflow beyond code: generated documents, presentations, websites, designs, and video can remain editable. The app runs locally, with an optional connection to iPolloCloud for organization and account features.
Key Features
- Use OpenCode as the default local runtime, with optional Codex and DeepSeek Harness integrations.
- Track project tasks, schedules, execution health, and results in a shared workspace for people and agents.
- Manage portable plugins, Skills, MCP servers, and related capabilities through a unified extension lifecycle.
- Create and continue editing code, documents, websites, presentations, designs, and video.
- Review permissions and execution, and use a model or provider of your choice.
- Operate the desktop UI from external clients through the
ipollowork-ui-mcpcontrol surface. - Work locally without an account; connect to iPolloCloud when organization services are needed.
Use Cases
- A development team coordinating work across OpenCode and Codex can use shared project tasks while retaining each runtime's own execution model.
- A team using DeepSeek Harness can delegate bounded work to its subagents and bring progress back into the project workspace.
- Creators who want agents to produce a presentation, website, design, or video, then edit the result rather than accept a finished export, can use the integrated creative workflow.
- Individual developers who want a local desktop workspace for agents, plugins, and project work can use it without connecting to Cloud.
What you need
Detected in the repository
- Node.js (from package.json)
- A test suite and automated checks on GitHub Actions
Getting Started
For a desktop install, choose the installer for your operating system and CPU from GitHub Releases. To run from source on macOS or Linux:
git clone https://github.com/Devin-AXIS/iPolloWork.git
cd iPolloWork
corepack enable
./ipollowork setup
./ipollowork dev
See the README for Windows instructions, build requirements, and runtime setup.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Alternatives
- Kun: Kun spans coding, writing, design, research, and automation, with a terminal TUI alongside its desktop GUI; iPolloWork centers on a desktop workbench.
- codeg: codeg focuses on coding-agent conversations and code changes across desktop, self-hosted, and Docker setups, while iPolloWork also targets creative outputs.
- agent-orchestrator: Agent Orchestrator centers on Git-backed coding tasks, isolated worktrees, and PR/CI review, unlike iPolloWork's broader multi-engine workbench.
- OpenMausBot: OpenMausBot organizes local agent CLIs as chat contacts and connects them to computers and apps, while iPolloWork emphasizes tasks, extensions, and editable outputs.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| iPolloWork | TypeScript | – | 6.7k | Active |
| Kun | TypeScript | Other | 6.3k | New |
| codeg | Rust | Apache-2.0 | 3.8k | Active |
| agent-orchestrator | Go | Apache-2.0 | 12.7k | Active |
| OpenMausBot | TypeScript | Apache-2.0 | 4k | New |
Considerations
- The project is active, with regular commits and releases, and contributions from multiple people; recent pull requests have merged quickly. Activity does not by itself establish the maturity of every runtime integration.
- Source development requires Node.js 22 or newer, pnpm, and Bun for the Orchestrator sidecar. The README also lists platform-specific build tools.
- The default OpenCode runtime and optional Codex and DeepSeek Harness integrations have separate compatibility boundaries. DeepSeek Harness is described as a developer preview, so its plugin compatibility follows its active release line.
- The license is source-available, not OSI-approved. It restricts use by teams of three or more and requires prior written authorization for sales, paid services, SaaS, hosting, and customer-facing use. Review the license before adoption.
- Cloud is optional, but identity, organization administration, hosted worker lifecycle, and commercial Apps are handled by iPolloCloud rather than the local app.
Found this useful?
Share it with someone who would like iPolloWork.