Introduction
What Niuniu is, what it solves, the capability landscape, and the two deployments at a glance.
Niuniu is a goal-driven, local-first AI work platform: write the work down as issues, and a fleet of AI Agents plan, execute, and verify them in parallel — across projects and repositories. It started as a way to drive many parallel coding agents and has grown to cover software development, office work, data analysis, and content creation.
What problem it solves
Traditional AI assistants work in a one-to-one chat model: one session, one task at a time, and you have to babysit each step. When you’re juggling three projects and five open issues, the constant back-and-forth becomes the bottleneck.
Niuniu raises the unit of work from “a chat” to “a goal.” Each workspace maps to one issue and comes with its own isolated git worktree, its own agent session, and its own shell environment. The agent autonomously closes the loop on that goal — only coming back to you when it’s actually blocked. Multiple workspaces run in parallel without interfering with each other.
Capability landscape
- Parallel engineering orchestration — isolated parallel workspaces, kanban project management, Harness engineering gates, code review, and an autohost watchdog that keeps work moving unattended.
- Any agent, any model — drive Claude Code / Codex / Qwen Code, and point them at GLM / DeepSeek / MiniMax / Kimi or any compatible endpoint, switchable per workspace — no vendor lock-in.
- Scenes — 18 one-click work modes spanning software / office / data / content, declaratively projecting MCP servers + plugins + quick actions.
- Data intelligence — connect SQL / Redis / Mongo / ES / HTTP data sources, run governed read queries, and pin inline charts as continuously refreshing dashboards.
- Knowledge & memory — ingest local directories into a searchable knowledge base; a white-box project memory captures patterns, decisions, and gotchas.
- IM bots — Lark / DingTalk / Telegram two-way conversational collaboration, one bot routed across multiple projects.
Two deployment options
- Personal — a desktop app that runs entirely on your local machine, distributed as a single binary for all three platforms.
- Self-Hosted Team — deploy via docker compose on your own infrastructure, backed by PostgreSQL, with fully private data, organizations, members, and audit logs.
For installation details, see the Install guide.
Next steps
- Try the 5-minute quickstart — get your first workspace running end to end.
- Read Core concepts — understand how Project / Repository / Workspace / Agent / Scene / Harness relate.
- Connect an IM bot — drive work from Lark / DingTalk / Telegram group chats.