Open source · MIT · Node ≥ 22

Work on many repos
as if they were one project

Your code is split across many Git repos. Nemus pulls the ones you're working on into one folder, runs commands across all of them at once, and gives your AI coding agent the whole picture — a monorepo-style workflow without merging your repos.

$ npm install -g @nemus-cli/nemus
Nemus terminal demo: nemus create payments → clones 12 repos and writes AGENTS.md → nemus run payments "npm test" → 12/12 repos green → nemus -- launches the agent

Everything, across every repo

A workspace is just a folder holding the repos you're working on. One command clones them all; then status, sync, branch, and run act on every repo at once — and your agent sees the whole set.

Workspaces

Group repos, clone them all in parallel, and jump straight in.

Operate in bulk

status, sync, diff, run, and branch across every repo in one command.

Suites & snapshots

Save reusable repo collections and capture exact workspace states.

Agent-native

Generated context files, installable skills, and an MCP server for your agent.

Healthy by default

Health checks, dependency analysis, and retries on flaky networks.

Investigate-first

Create an empty workspace and let an agent discover and add the repos it needs.

Up and running in a minute

Install globally, configure once, then create your first workspace — or describe the task in plain English and let an agent set it up.

5
coding agents supported
1
command across N repos
MIT
open source
# Install globally
npm install -g @nemus-cli/nemus

# One-time setup (org, agent, clone protocol…)
nemus configure

# Create your first workspace
nemus create

# …or let an agent do it, in plain English
nemus -- "set up the payments stack
        and start on the refund bug"

Bring your own coding agent

Nemus generates context files, installs skills, and runs an MCP server so your agent understands the whole workspace — not just one repo.

Claude Code pi OpenCode Codex Gemini

A full clone per workspace — on purpose

Every workspace gets its own independent, full git clone of each repo: separate .git, index, stash, hooks, config, branches, and build outputs.

Why not git worktree? Worktrees share one object store and are great for one repo. Nemus targets many repos worked on in parallel — often by AI agents — where total isolation wins: two workspaces can both sit on main, and one agent’s rebase, gc, or dirty tree can’t touch another’s.
# Operate across every repo at once
nemus status   my-stack
nemus sync     my-stack
nemus run      my-stack "npm test"
nemus branch   my-stack feature/x

# Save & reuse a set of repos
nemus suite create payments
nemus create --suite payments

For humans and for machines

This site ships an llms.txt — a concise, structured overview of Nemus in the llmstxt.org format — so an LLM can read the project at a glance and follow links to the full docs.