Are you the author? Sign in to claim
Loop-core multi-agent coding tool that orchestrates work through plan→implement→review cycles. The orchestrator is re
Multi-agent coding workspace — decompose, distribute, verify, remember.
Nori orchestrates multiple AI agents to plan, implement, review, and persist knowledge across sessions. Not another chat-over-code tool — a multi-agent engineering workspace.


[!NOTE] v1.0.0 is the first stable Nori Code and Nori Work release. Existing Nori Work installations are fully replaced during upgrade while user data is preserved.
.html and .htm files open in the embedded browser without granting arbitrary file:// access.| Nori Code | Nori Work | |
|---|---|---|
| What | Terminal CLI/TUI for focused coding sessions | Electron desktop workbench |
| Who for | Terminal-first power users | Full workspace with browser, terminal, Git, filesystem |
| Interface | Ink-based TUI with split panes | Multi-panel Electron desktop |
| Start | nori | Standalone installer (see releases) |
Most AI coding tools are single-agent chat shells: one model, one context, one turn at a time. Nori is built differently:
nori.yaml enforces deterministic rules: search memory before coding, run tests before exit, review before merge. AI flexibility backed by project discipline.AgentSwarm splits a task into parallel sub-agents with explicit dependency chaining. A multi-file refactor dispatches { plan, implement-1, implement-2, verify, review } concurrently — no manual turn-by-turn handholding.
Every decision, review, and pattern lands in an Obsidian-compatible vault with [[wiki-links]]. The planner searches it automatically before each implementation phase. Cross-session knowledge means Nori gets smarter about your project over time.
nori.yaml)Codify project rules that the agent loop enforces automatically:
rules:
- name: search_before_code
condition: { on_phase: implement, stage: enter }
prompt: "Search vault for prior decisions and patterns."
enforced: true
Orchestrator, coder, and reviewer can each use a different model/provider.
Bring any OpenAI-compatible provider — local (Ollama, LM Studio) or cloud. Each agent role (orchestrator / coder / reviewer) can run its own model.
Nori Work keeps the conversation, project files, live code changes, Git operations, LSP results, a persistent PTY terminal, and a multi-tab embedded browser in one resizable desktop layout. Inspector tools can be reordered or opened in standalone windows. Custom Agent roles define their own instructions and explicit read, write, terminal, web, and delegation permissions.
Agent and AgentSwarm work always runs in the background. The main model can inspect, pause, guide, resume, or stop a swarm while the collaboration view shows its project/session tree, status, output, and token usage.
The embedded browser is available to the main Agent through a structured Browser tool: navigate, snapshot stable element references, click, type, upload files, capture screenshots, inspect console/network activity, and work with page annotations. It supports web URLs and local .html/.htm files while blocking privileged URLs and arbitrary local files. User takeover can pause automation at any time, and actions fail immediately with actionable feedback when no page is open.
Memory notes use vault-relative [[folder/note|Title]] links. Nori Work renders outgoing links, backlinks, and the movable knowledge graph while retaining compatibility with legacy vault layouts and Obsidian.
| Priority | Feature | Status |
|---|---|---|
| P0 | Built-in LSP — diagnostics, hover, definitions, references, symbols, rename, and formatting | ✅ Implemented |
| P0 | Custom Agent Profiles — user-defined roles, prompts, base profiles, and tool permissions | ✅ Implemented |
| P0 | Nori Work — Embedded Terminal (persistent node-pty sessions) | ✅ Implemented |
| P0 | Nori Work — Embedded Browser (isolated WebContentsView tabs for research and preview) | ✅ Implemented |
| P0 | Nori Work — Filesystem Sandbox (whitelist + blocklist) | 📝 Planned |
| P0 | Nori Work — System Tray / Notifications | ✅ Implemented |
| P0 | Nori Work — Secure Preload Bridge | ✅ Implemented |
| P1 | Agent Browser Tool — navigation, snapshots, interaction, uploads, diagnostics, and annotations | ✅ Implemented |
npm install -g nori-code
# Interactive TUI
nori
# One-shot prompt
nori -p "your task"
# Start the local web workspace
nori web
Nori Work is available as a standalone desktop installer. Download the stable v1.0.0 release, or browse all builds on Releases.
git clone https://github.com/wangyuahn/nori-code.git
cd nori-code
corepack enable
pnpm install
pnpm dev:cli # Terminal TUI
pnpm dev:web # Web UI
pnpm dev:desktop # Desktop workbench
| Package | Role |
|---|---|
apps/nori-code | CLI/TUI entry point |
apps/nori-web | Web UI (loaded by desktop) |
apps/nori-desktop | Electron desktop workbench |
packages/agent-core | Agent, session, swarm, tool, workflow engine |
packages/server | REST/WebSocket server |
packages/kosong | Model/provider abstraction |
packages/kaos | File, process, environment abstractions |
packages/node-sdk | Public TypeScript SDK |
packages/oauth | Authentication and provider registry |
pnpm typecheck
pnpm lint
pnpm test
pnpm build
pnpm check:brand # Verify no stray Kimi branding
Run focused checks per affected package first; expand to root-level checks before commit.
MIT. Based on Kimi Code CLI (MIT), from which Nori forked and grew its own architecture: multi-agent DAG orchestration, persistent memory, desktop environment, policy engine, and independent branding. Required upstream compatibility is maintained where shared protocol surfaces apply.
⚠️ Experimentelle Skill-Sammlung für deutsches Recht (Arbeits-, Gesellschafts-, Insolvenz-, Datenschutz-, Prozessrecht u
Manage multiple Claude Code agents from TUI or Web with tmux and git worktrees
Project management using GitHub Issues + Git worktrees for parallel agent execution
Core skills library for Claude Code with 20+ battle-tested skills including TDD, debugging, and brainstorming