iPolloWork vs Kun
Local-first AI agent workspaces compared
iPolloWork and Kun are local-first workspaces for directing AI agents across practical tasks. iPolloWork centers on coordinating multiple agent runtimes and keeping creative outputs editable, while Kun connects coding, writing, design, and collaboration through a shared desktop and terminal runtime.
iPolloWork: Coordinate AI Agents and Edit Their Work
iPolloWork is a local-first desktop workbench for coordinating projects across Codex, DeepSeek Harness, and OpenCode. It brings agent tasks, extensions, and editable outputs for code and creative work into one workspace.
Kun: Local-First AI Agent Workspace
Kun is a local-first workspace for using AI agents across coding, writing, design, research, and automation. Its desktop GUI and terminal TUI share one runtime, keeping tasks and approvals connected.
| iPolloWork | Kun | |
|---|---|---|
| Language | TypeScript | TypeScript |
| License | — | NOASSERTION |
| Stars | 6.7k | 6.3k |
| Forks | 1.1k | 595 |
| Last analyzed | Oct 7, 2026 | Oct 4, 2026 |
Key differences
- iPolloWork coordinates work across OpenCode, with optional Codex and DeepSeek Harness integrations; Kun provides a shared runtime for its desktop GUI and terminal TUI.
- iPolloWork supports editable outputs including documents, websites, presentations, designs, and video; Kun focuses on coding, design canvas, writing, research, and work modes.
- iPolloWork offers a unified lifecycle for plugins, Skills, and MCP servers; Kun includes options such as scheduled tasks, Loops, Hooks, MCP, Skills, and installable extensions.
- iPolloWork can work locally without an account and optionally connect to iPolloCloud; Kun requires a compatible model provider, and cloud providers may receive prompts, attachments, and task context.
- iPolloWork's license is described as source-available and restricts use by teams of three or more, while Kun's README describes a PolyForm Noncommercial License and separate authorization for commercial use.
- Both projects use TypeScript and are not archived; iPolloWork lists 6.7k stars and 1.1k forks, while Kun lists 6.3k stars and 595 forks.
Choose iPolloWork if you…
- want to coordinate projects across OpenCode, Codex, or DeepSeek Harness.
- need generated code and creative work to remain editable in one workspace.
- want a local desktop workflow that can run without an account.
Choose Kun if you…
- want tasks and approvals to continue between a desktop GUI and terminal TUI.
- need workflows spanning coding, writing, design, research, or automation.
- want Rooms for delegated work, isolated Git worktrees, and review.
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.