Skip to content
Back to search

iPolloWork

SkillWorks with CodexGitHub

Enterprise-grade, local-first Agent Workbench for people and agent teams. A unified multi-engine workspace for Codex Harness, DeepSeek Harness, and OpenCode, with unified plugins and Skills, multi-agent projects and tasks, and editable code, documents, presentations, design, and video.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Devin-AXIS/iPolloWork with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Devin-AXIS/iPolloWork'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/devin-axis-ipollowork/badge.svg)](/listings/devin-axis-ipollowork)

HTML

<a href="/listings/devin-axis-ipollowork"><img src="/api/listings/devin-axis-ipollowork/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Download the desktop app

Official installers are published on [GitHub Releases](https://github.com/Devin-AXIS/iPolloWork/releases). If you prefer a manual download, choose the file that matches both your operating system and CPU:

| System | CPU | Installer to use | | --- | --- | --- | | macOS | Apple Silicon (M-series) | `ipollowork-mac-arm64-<version>.dmg` | | macOS | Intel | `ipollowork-mac-x64-<version>.dmg` | | Windows | Intel/AMD 64-bit | `ipollowork-win-x64-<version>.exe` | | Windows | ARM64 | `ipollowork-win-arm64-<version>.exe` | | Linux | Intel/AMD 64-bit | `ipollowork-linux-x64-<version>.AppImage` | | Linux | ARM64 | `ipollowork-linux-arm64-<version>.AppImage` |

The macOS `.zip` and Linux `.tar.gz` files are portable/update artifacts; most users should choose `.dmg`, `.exe`, or `.AppImage`. If the Releases page does not yet contain an installer for your system, run or package the app from source below.

Installation after downloading:

- **macOS:** open the `.dmg`, then drag **iPolloWork** into Applications. - **Windows:** run the `.exe` installer. A locally built, unsigned installer may trigger Microsoft Defender SmartScreen. - **Linux:** make the AppImage executable with `chmod +x ipollowork-*.AppImage`, then run it. The `.tar.gz` package can be extracted and run without installation.

Requirements for source development and packaging

- [Git](https://git-scm.com/downloads) - [Node.js](https://nodejs.org/en/download) 22 or newer - pnpm 11, enabled through Corepack with `corepack enable` - [Bun](https://bun.sh/docs/installation) 1.3.10 or newer, used to build the local Orchestrator sidecar - macOS: Xcode Command Line Tools (`xcode-select --install`) - Windows: [Visual Studio 2022 Build Tools](https://visualstudio.microsoft.com/visual-cpp-build-tools/) with **Desktop development with C++** and the Windows SDK; use PowerShell or Command Prompt - Linux: a standard Electron build environment with a C/C++ toolchain, Python 3, `pkg-config`, and the desktop libraries required by Electron; the release build uses Ubuntu 22.04

OpenCode is downloaded and prepared as a separate sidecar during the first desktop build. iPolloWork does not fork or rewrite OpenCode, and OpenCode can continue to be upgraded independently.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 112 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # iPolloWork
  2. English | [中文](README.zh.md)
  3. <p align="center">
  4. <a href="https://github.com/Devin-AXIS/iPolloWork/releases/latest"><img src="https://img.shields.io/github/v/release/Devin-AXIS/iPolloWork?display_name=tag&amp;sort=semver" alt="Latest release" /></a>
  5. <a href="https://github.com/Devin-AXIS/iPolloWork/releases"><img src="https://img.shields.io/github/downloads/Devin-AXIS/iPolloWork/total" alt="GitHub downloads" /></a>
  6. <a href="https://github.com/Devin-AXIS/iPolloWork/stargazers"><img src="https://img.shields.io/github/stars/Devin-AXIS/iPolloWork?style=flat" alt="GitHub stars" /></a>
  7. <a href="https://x.com/iPolloWork"><img src="https://img.shields.io/badge/X%20Global-%40iPolloWork-000000?logo=x&amp;logoColor=white" alt="Follow iPolloWork on X" /></a>
  8. <a href="https://x.com/iPolloCN"><img src="https://img.shields.io/badge/X%20%E4%B8%AD%E6%96%87-%40iPolloCN-000000?logo=x&amp;logoColor=white" alt="Follow iPolloCN on X" /></a>
  9. <a href="https://www.bestpractices.dev/projects/14127"><img src="https://www.bestpractices.dev/projects/14127/badge" alt="OpenSSF Best Practices" /></a>
  10. <a href="https://www.cloudflare.com/startups/"><img src="https://img.shields.io/badge/Cloudflare-for%20Startups-F38020?logo=cloudflare&amp;logoColor=white" alt="Cloudflare for Startups" /></a>
  11. <a href="https://github.com/opea-project"><img src="https://img.shields.io/badge/OPEA-Open%20Platform%20for%20Enterprise%20AI-ff7a00" alt="OPEA: Open Platform for Enterprise AI" /></a>
  12. </p>
  13. <p align="center">
  14. <a href="https://trendshift.io/repositories/88012?utm_source=trendshift-badge&amp;utm_medium=badge&amp;utm_campaign=badge-trendshift-88012"><img src="https://trendshift.io/api/badge/trendshift/repositories/88012/daily?language=TypeScript" alt="TypeScript repository daily trend | Trendshift" width="250" height="55" /></a>
  15. <a href="https://trendshift.io/repositories/88012?utm_source=trendshift-badge&amp;utm_medium=badge&amp;utm_campaign=badge-trendshift-88012"><img src="https://trendshift.io/api/badge/trendshift/repositories/88012/weekly?language=TypeScript" alt="TypeScript repository weekly trend | Trendshift" width="250" height="55" /></a>
  16. </p>
  17. **An enterprise collaboration platform for people and AI agents, built on the open-source DeepSeek Harness.**
  18. https://github.com/user-attachments/assets/201b561a-22ec-4c8e-a4e8-f34172cf0aa3
  19. [Download the original demo](docs/assets/ipollowork-demo.mp4)
  20. iPolloWork brings multi-agent teams, shared projects, plugins, Skills and editable work into one workspace. A main assistant coordinates specialists; people share context, follow progress and continue working together across code, documents, presentations, websites, design and video.
  21. The video above is the original iPolloWork demo. The current `main` branch uses the native DeepSeek Harness runtime; the earlier multi-engine edition remains on [`ipollowork-multi-engine`](https://github.com/Devin-AXIS/iPolloWork/tree/ipollowork-multi-engine).
  22. <div align="center">
  23. <h3>Join the official iPolloWork WeChat community</h3>
  24. <p>Scan with WeChat for product updates and community discussions.</p>
  25. <img src="./docs/assets/ipollowork-official-wechat-group.jpg" alt="QR code for the official iPolloWork WeChat community" width="220" />
  26. </div>
  27. ## What makes it different
  28. - **People and agent teams** — use a main assistant, reusable specialists and native task delegation in the same workspace.
  29. - **Enterprise projects** — organize members and departments, grant project access, share files and project memory, and review submitted changes.
  30. - **Live collaboration** — share a native conversation, let authorized people view or participate, and continue independently through a fork.
  31. - **Plugins and Skills** — use the native plugin lifecycle and curated market, with integrated messaging and project-specific agent instructions.
  32. - **Editable creative work** — use Design and Video views for presentations, websites and visual production, then keep editing the result.
  33. - **Shared services and app data** — discover account-authorized AI capabilities over HTTP and give small apps a record store without their own database.
  34. <a id="run"></a>
  35. <a id="run-from-source"></a>
  36. ## Start from source
  37. Use Node.js **24.15 or newer** and **pnpm 11**. Run these commands in a terminal on macOS or Linux:
  38. ```sh
  39. git clone --branch main https://github.com/Devin-AXIS/iPolloWork.git
  40. cd iPolloWork
  41. npm run setup:build
  42. npm run build
  43. npm start
  44. ```
  45. The same commands work in Windows PowerShell. `npm start` uses the compiled pinned DSH launcher, preserves the profile, and configures the reviewed Studio dependency builds.
  46. Open the local address printed by the launcher. The suite adds iPolloWork's account, agents and plugin views to the native Web UI. Sign in for configured account services and organization features; local model providers keep their own credentials. Do not paste an account or provider key into a project page.
  47. The account service is deployed separately. Its [setup guide](services/ipollowork/README.md) covers PostgreSQL, account configuration and storage; [capability API documentation](services/ipollowork/docs/capabilities.md) covers external HTTP access. The suite uses iPolloWork Cloud by default; configure `accountOrigin` as described in the [suite guide](plugins/ipollowork-suite/README.md) for your own service.
  48. ## Desktop and development
  49. The source Web UI runs on macOS, Windows and Linux. Native desktop development and installer packaging use the [Desktop guide](integrations/desktop/README.md) and [packaging guide](integrations/desktop/packaging/README.md). Published files on [GitHub Releases](https://github.com/Devin-AXIS/iPolloWork/releases) may belong to the earlier multi-engine edition; check the release description before installing.
  50. For ongoing development, see the [development guide](integrations/runtime/README.md), [integration overview](integrations/README.md) and [delivery guide](integrations/delivery.md). Agent instructions live in [AGENTS.md](AGENTS.md). DeepSeek Harness remains the execution runtime; this branch does not start a second agent engine.
  51. ## Community and contributing
  52. Use [GitHub Issues](https://github.com/Devin-AXIS/iPolloWork/issues) for iPolloWork bugs and requests. Read [CONTRIBUTING.md](CONTRIBUTING.md) before submitting changes and [SECURITY.md](SECURITY.md) before running agent tasks. The upstream runtime is maintained by [DeepSeek](https://github.com/deepseek-ai/deepseek-harness).
  53. ## Star History
  54. <p align="center">
  55. <a href="https://www.star-history.com/?repos=Devin-AXIS%2FiPolloWork&amp;type=date&amp;legend=top-left">
  56. <picture>
  57. <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/Devin-AXIS/iPolloWork/star-history/docs/star-history/star-history-dark.svg" />
  58. <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/Devin-AXIS/iPolloWork/star-history/docs/star-history/star-history-light.svg" />
  59. <img alt="iPolloWork Star History" src="https://raw.githubusercontent.com/Devin-AXIS/iPolloWork/star-history/docs/star-history/star-history-light.svg" width="900" />
  60. </picture>
  61. </a>
  62. </p>
  63. ## License
  64. Owned iPolloWork code uses the [iPolloWork Source Available License](LICENSE). This is source-available software, not an unrestricted MIT grant. Third-party code and previously granted licenses remain under their original terms; see [third-party notices](THIRD_PARTY_NOTICES.md). Git history and original author attribution are retained when upstream files are removed from the current tree.
  65. ## Synchronized release mirrors
  66. [Release mirror automation](.github/workflows/release-mirror.yml) copies the original GitHub release assets to S3-compatible mainland storage; it never rebuilds a second version. Each local download and each public mirror download must match GitHub's SHA-256 digest and size before a verified manifest is exposed. Published release changes trigger synchronization; after all platform assets reach a draft, dispatch the workflow with its tag to mirror, verify, and publish it. Failed copies are retryable and do not publish the draft.
  67. Configure the `release-mirror` GitHub environment once: variables `IPOLLO_MIRROR_S3_ENDPOINT`, `IPOLLO_MIRROR_BUCKET`, `IPOLLO_MIRROR_PUBLIC_URL`, `IPOLLO_MIRROR_REGION`; secrets `IPOLLO_MIRROR_ACCESS_KEY_ID`, `IPOLLO_MIRROR_SECRET_ACCESS_KEY`. The public origin must serve the bucket's `releases/<tag>/<filename>` paths over HTTPS without redirects. Use a dedicated mainland bucket with write access restricted to this prefix. Missing configuration fails explicitly; an unconfigured workflow is not an active mainland mirror.
  68. Published desktop versions use three numeric parts (for example `1.0.2`). A GitHub Latest release must include `stable-mac.yml` and `stable.yml` plus every referenced ZIP/installer; the release title alone cannot notify installed clients. Generate and verify feeds with `integrations/tooling/release-update-feed.mjs` before publication.
  69. The standard publication entrypoint is **Actions → Publish verified iPolloWork release** (`ipollo-publish.yml`). Upload the signed and notarized Apple Silicon/Intel DMGs, update ZIPs, blockmaps, clean-build records, Windows installer and current Design/suite packages to a numeric draft. Then dispatch this workflow with the tag. It rejects incomplete drafts and versions older than Latest, verifies every downloaded byte against GitHub, generates both update feeds and checksums, publishes Latest, and checks the public feeds and referenced downloads. A failed public check restores the previous Latest. The mirror workflow receives the same finalized files; it does not rebuild them. Do not publish a draft manually or promote a test suffix to Latest.
  70. The [Stage adapter](plugins/stage/README.md) is included in the complete desktop installer. Open it manually, link your existing Stage account once, and explicitly enable a workspace for conversation tools. Stage remains an independent editor/service; official model usage is settled in Work points from actual tokens without a balance hold.
  71. ## Independent plugins
  72. [Plugin development standard (Chinese)](docs/plugin-development.zh.md) · [Word document](docs/plugin-development.zh.docx) · [Plugin development skill](.agents/skills/ipollowork-plugin-development/SKILL.md)
  73. [Data annotation training](plugins/data-annotation/README.md) and [Operation recorder](plugins/operation-recorder/README.md) are separately installable DSH bundles. They reuse official authentication, workspaces and plugin lifecycle; neither modifies the DSH runtime. Recorder exports installable DSH Skill bundles. Independent plugins are distributed separately through the plugin marketplace; do not bundle them in the iPolloWork application installer.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.