Skip to content
Public template

About

An enterprise collaboration platform for people and multi-agent teams, built on the open-source DeepSeek Harness. Shared projects, plugins and Skills, integrated messaging, and editable code, documents, presentations, design, websites and video.

Topics

Resources

Contributing

Security policy

Stars

7.5k stars

Watchers

529 watching

Forks

Repository files navigation

iPolloWork

English | 中文

Latest release GitHub downloads GitHub stars Follow iPolloWork on X Follow iPolloCN on X OpenSSF Best Practices Cloudflare for Startups OPEA: Open Platform for Enterprise AI

TypeScript repository daily trend | Trendshift TypeScript repository weekly trend | Trendshift

An enterprise collaboration platform for people and AI agents, built on the open-source DeepSeek Harness.

d1cf1a78c030e110f2029d2170479d18.mov

Download the original demo

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.

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.

Join the official iPolloWork WeChat community

Scan with WeChat for product updates and community discussions.

QR code for the official iPolloWork WeChat community

What makes it different

  • People and agent teams — use a main assistant, reusable specialists and native task delegation in the same workspace.
  • Enterprise projects — organize members and departments, grant project access, share files and project memory, and review submitted changes.
  • Live collaboration — share a native conversation, let authorized people view or participate, and continue independently through a fork.
  • Plugins and Skills — use the native plugin lifecycle and curated market, with integrated messaging and project-specific agent instructions.
  • Editable creative work — use Design and Video views for presentations, websites and visual production, then keep editing the result.
  • Shared services and app data — discover account-authorized AI capabilities over HTTP and give small apps a record store without their own database.
  • Project Board — A suite component with a conversation tab for project tasks, scheduling, dependencies, organization assignments and notifications.
  • Notification Center — A suite component with one inbox beside the account avatar for conversation and plugin notifications.

Start from source

Use Node.js 24.15 or newer and pnpm 11. Run these commands in a terminal on macOS or Linux:

git clone --branch main https://github.com/Devin-AXIS/iPolloWork.git
cd iPolloWork
npm run setup:build
npm run build
npm start

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.

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.

The account service is deployed separately. Its setup guide covers PostgreSQL, account configuration and storage; capability API documentation covers external HTTP access. The suite uses iPolloWork Cloud by default; configure accountOrigin as described in the suite guide for your own service.

Desktop and development

The source Web UI runs on macOS, Windows and Linux. Native desktop development and installer packaging use the Desktop guide and packaging guide. Published files on GitHub Releases may belong to the earlier multi-engine edition; check the release description before installing.

For ongoing development, see the development guide, integration overview and delivery guide. Agent instructions live in AGENTS.md. DeepSeek Harness remains the execution runtime; this branch does not start a second agent engine.

Community and contributing

Use GitHub Issues for iPolloWork bugs and requests. Read CONTRIBUTING.md before submitting changes and SECURITY.md before running agent tasks. The upstream runtime is maintained by DeepSeek.

Star History

iPolloWork Star History

License

Owned iPolloWork code uses the iPolloWork Source Available 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. Git history and original author attribution are retained when upstream files are removed from the current tree.

Synchronized release mirrors

Release mirror automation 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.

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.

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.

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.

Independent plugins

Plugin development standard (Chinese) · Word document · Plugin development skill

Data annotation training and Operation recorder 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.

About

An enterprise collaboration platform for people and multi-agent teams, built on the open-source DeepSeek Harness. Shared projects, plugins and Skills, integrated messaging, and editable code, documents, presentations, design, websites and video.

Topics

Resources

Contributing

Security policy

Stars

7.5k stars

Watchers

529 watching

Forks

Releases

Packages

Used by

Contributors

Languages