Claude Code
Native terminal agent with deep tool use and autonomous subagents
github.com/IAPro-Community/nexus Your local workstation
Your local workstation
for coding agents.
Turn goals into executable work: coordinate persistent agents, pick AI resources, and only reach done when there is verifiable evidence.
Supported today:
Linux amd64Windows amd64macOS arm64macOS Intel
To get started, the recommended path is Direct: Project → + New → AI Session → Provider → Terminal.
$ curl -fsSL https://nexus.iapro.club/install.sh | bash
# Fetching verified release...
# nexus installed to ~/.local/bin/nexus
$ nexus doctor --check-all
✓ Local SQLite ready ✓ Git worktrees ok ✓ CLI providers detected
$ ./nexus web
🚀 Nexus Workstation UI running on http://localhost:8080
$
$ nexus worktree create feat/checkout --agent claude
✓ Isolated worktree created at .worktrees/feat/checkout
✓ Claude Code attached with dedicated branch
$ nexus run --task "fix checkout address validation"
● Inspecting src/checkout/validators.ts...
● 1 command executed: PASS 18 unit tests
✓ Mission completed with verified evidence
$
$ nexus team run --spec ACTIVE.md
● Lead: Maestro Orchestrator active (planning & routing)
● Worker 1: Claude Code -> Implementation in isolated worktree
● Worker 2: Codex -> Tests & regression coverage
● Gatekeeper: WCAG AA contrast check passed
✓ All 4 workstreams synchronized successfully
$
1 Core Web, Desktop and CLI operating the same state
3 surfaces visual, native and headless
4 platforms Linux amd64 · Windows amd64 · macOS arm64/Intel
0 third-party telemetry
Agents & Models
Bring your own agents. Command the fleet.
Nexus runs 100% locally on your machine. Plug in the CLI coding agents you already subscribe to or run locally, each isolated in its own Git worktree.
OpenAI Codex
Precise execution with reasoning and verified file diffs
OpenCode
High-performance open-source multi-provider client for terminal
Google Gemini
Ultra-long context window for whole-repository ingestion
xAI Grok
Rapid reasoning and full-stack software synthesis
Antigravity
Autonomous orchestration and evidence-gated verification
Pi / oh-my-pi
Terminal multiplexing and lightweight, resilient agents
Cursor CLI
Fast codebase indexing and semantic symbol navigation
Core
Everything Nexus brings together in a single Core
One system to operate coding agents — not a patchwork of scripts.
Projects and Workspaces
Local work areas with isolated context, terminals and configuration per project.
Persistent agents
An Agent is a durable identity. Codex, Claude, Gemini and others are selectable runners bound by capacity and policy.
Providers, profiles and quota
Models, profiles and limits managed in the Core, never coupling the agent role to a provider.
Supervised terminals and runtimes
Supervised execution, diagnostics via nexus doctor and headless scripting through the CLI.
Versioned Plans & Directives
Intent structured into versioned work plans with clear steps and acceptance criteria before execution.
Durable Missions
Execution under policies, gates and isolation, with GO as a real boundary and recovery on failure.
Isolated worktrees and scheduler
Safe parallel writing in worktrees, plus resource policies for agents and runtimes.
Evidence and Definition of Done
Receipts, artifacts, memory and verification: textual "done" is not success. The destination is COMPLETED_VERIFIED.
Workflow
How Nexus works
From a text objective to a verified result — with you authorizing every material step.
Objective
You describe what you want to achieve, in natural language, inside a Project.
Work Plan
Intent is turned into a versioned work plan: steps, dependencies and acceptance criteria.
Authorization (GO)
You review and authorize a specific plan revision before running — a real boundary.
Mission + Agents
The Mission runs under policies, isolated worktrees and quotas, coordinating agents through a closed protocol.
Evidence → COMPLETED_VERIFIED
Tests, artifacts and Definition of Done decide. Textual "done" does not close a mission.
Agent ≠ provider
An Agent is a persistent identity with a role and memory. Codex, Claude, Gemini and other runners are resources selected by capacity, policy and availability — switching providers does not switch your agent.
Agent → AgentSpec → AgentRevision → RuntimeGeneration → ProviderSession
This avoids coupling the worker's role to a specific provider: models change; the agent persists.
Agent-to-agent coordination
Agents never chat loose: all coordination goes through the MissionRunner, which tries memory and receipts before creating another run and blocks replay without proof of safety.
NEED_INFOARTIFACT_REQUESTREVIEW_REQUESTDELEGATE
Fail closed, by default
- Push and deploy are not implied permissions
- Reviewers and investigators are read-only
- Parallel writes only in isolated worktrees
- Retries and no-progress loops are bounded
- Missing evidence never becomes success
- Material changes require human intervention
Three surfaces, one Core
Web
local visual operation: Projects, Agents, Workspaces and Missions
Desktop
native shell when the platform has matching native evidence
CLI
automation, diagnostics, scripting and headless execution
The HUD projects the Core state in real time — Capacity, Scheduler, Costs, Agents and Missions — into the Web OS and a native gadget.
Why Nexus
Why Nexus is different
Not another AI chat: a complete runtime for coordinating software work.
Completion by evidence
Missions only close as COMPLETED_VERIFIED: tests, artifacts and Definition of Done. No declared "done".
You approve every plan
GO is a real boundary: nothing executes without your approval of a specific plan revision.
No provider lock-in
Agent ≠ provider: your agent survives model changes. Capacity and routing are chosen by the Core.
Fail closed everywhere
Push/deploy permissions are never implied; no evidence means no success; replay without proof is blocked.
Safe parallelism
Isolated worktrees, scheduler and resource policies let agents collaborate without collisions.
Local-first
Workspaces, terminals, runtimes and memory run on your machine — Nexus reports status, it does not hoard your data.
Tour
See Nexus from the inside
Real product captures — no mocks.
The full visual tour lives in docs/product/visual-tour.md in the repository.
Intelligence
Orquestrador Maestro — the intelligence layer
Nexus is the runtime. Maestro is the method that governs what agents do inside of it.
An open source (Apache-2.0) AI agent orchestration kit that runs alongside the Nexus CLI and your favorite tools: Codex, Claude, OpenCode, Cursor, Gemini, Windsurf and more. Instead of letting the AI decide what to read and declare "done" without proof, Maestro organizes the path before execution — with verification and handoff as part of the work.
Lead • Orquestrador Maestro
Decisão & Roteamento
Planeja, Roteia e Sintetiza
Mantém a memória durável e distribui as fatias de código para os agents especialistas em worktrees isolados, mantendo o humano no controle de cada merge.
📐 Spec & Contrato ACTIVE.md
Escopo delimitado e critérios de aceite antes de tocar no código.
⚡ Implementação Worktree #1
Claude Code ou Codex executando fatias limpas sem colisões de branch.
🧪 Verificação Smoke & Diffs
Execução observável dos caminhos alterados. Evidência em log real.
🛡️ Quality Gate WCAG AA
Auditoria de contraste de tokens e integridade da arquitetura.
Nexus
execution: agents, runtimes, providers, workspaces, UX and evidence
Maestro
methodology: skills, risk, gates and verification policies
Apache-2.056 canonical skills79 public skillsRouter v3Stable V1
What the Maestro layer brings
- Complexity Gate + Router v3: the right skill and problem-proportional context — from 1.5k tokens on MICRO tasks to 16k on DEEP ones
- Resolution Engine: separates a closed process from a Validated Outcome, with Evidence and Proof Bundle
- 56 canonical and 79 public skills: from planning to release engineering and security
- Durable DEV/ memory: objective, decisions and verification live in the project, not in chat history
- Privacy by default: telemetry off; your content stays local
$ npm install -g @iapro/orquestrador-maestro-cli@latest
$ orquestrador-maestro install
$ orquestrador-maestro verify
Without the Maestro: Nexus is not left blind: Direct, Workspaces, Terminal and Mission remain native capabilities. The Maestro is accumulated method, not a dependency to run.
Modes
Pick the mode that matches the problem size
From a small fix to long-running multi-agent work with gates.
| Situation | Use |
|---|---|
| Small fix, debugging, exploration | Direct |
| Supervised terminal session | Terminal |
| Long, multi-Agent work with gates | Mission |
| Methodology, skills and external gates | Maestro (optional) |
Mission and Maestro are not prerequisites: Direct alone is enough to start.
Download
Get Nexus
Two ways to run it: a native app on your machine, or Nexus Web built straight from source.
A
Native app on your PC
Binaries from the official pipelines for Linux, Windows and macOS: Desktop, CLI and HUD per platform. No third-party telemetry.
Download ↓B
Nexus Web via git clone
Compile the Web workspace locally from source. This is the recommended path for first use and development.
$ git clone https://github.com/IAPro-Community/nexus.git
$ cd nexus
$ bun --cwd web install --frozen-lockfile
$ make build
$ ./nexus doctor
$ ./nexus web
Download per platform
Each card below lists the current release assets for that OS, straight from the project CI.
Unsigned preview: Current binaries are development previews produced by CI: no Authenticode certificate, Developer ID or notarization. Windows SmartScreen and macOS Gatekeeper may warn. These are not stable releases.
Linux
tar -xzf nexus-*.tar.gz && sudo mv nexus /usr/local/bin/ && nexus doctor
Windows
Extract the .zip and run nexus.exe doctor in a terminal.
macOS
[cli] nexus-preview-macos-arm64-cli.tar.gz 8.8 MB [desktop] nexus-preview-macos-arm64-desktop.zip 9.5 MB [hud] nexus-preview-macos-arm64-hud.zip 9.5 MB
tar -xzf nexus-*.tar.gz && sudo mv nexus /usr/local/bin/
macOS
[cli] nexus-preview-macos-intel-cli.tar.gz 9.3 MB [desktop] nexus-preview-macos-intel-desktop.zip 10.0 MB [hud] nexus-preview-macos-intel-hud.zip 10.0 MB
tar -xzf nexus-*.tar.gz && sudo mv nexus /usr/local/bin/
install.sh / install.ps1 — The repo install scripts ship with certified releases. Until then, use the preview assets or build from source.
Native packages (.deb for Linux; signed installers for Windows and macOS) will land on this site as they are certified by the exact-SHA program — follow the release status.
How the build reaches you
Nothing is announced stable without evidence: each step is pinned to an exact SHA and to certification gates.
CI produces the preview
GitHub-hosted runners build Linux amd64, Windows amd64 and macOS arm64/Intel on every development merge.
Immutable snapshot
The build is published under a preview-<SHA> tag with SHA256SUMS.txt. Version and source are bit-for-bit reproducible.
exact-SHA certification
Native jobs certify the SAME source SHA per platform: signing, notarization and tests before any announcement.
Signed stable release
Only after certification does the release enter stable channels. Signed updates never point at preview tags.
LIVECACHEDESTIMATEDVERIFIEDUNVERIFIED
Docs
Documentation
The canonical entry point is docs/README.md in the repository.
Quick Start Install and run your first session in minutes. How it works The product workflow, end to end. Visual tour Real captures of the main surfaces. CLI Commands, diagnostics and automation. Architecture How Core, Agents and Missions fit together. Release status The authoritative truth about what is published.
Community
Contribute to Nexus
The project is built in public. Docs, tests, screenshots and code are equally welcome.
1. Set up your environment
Go 1.25+, Bun 1.3.9+, Git and Make. Then: bun --cwd web install --frozen-lockfile && make build.
2. Open an issue
Before large changes, align scope in an issue or discussion on the repo.
3. Create a branch
E.g. feat/worktree-gates. Commits follow Conventional Commits — the repo runs commitlint + husky.
4. Send a PR
Describe what changed and how to verify it. See CONTRIBUTING.md for the full contract.
Want an easy start? Docs improvements and fresh screenshots for the visual tour are great first PRs.
FAQ
Frequently asked questions
The short answers, no marketing.
What is Nexus?
A local workstation and control plane for coding agents: Projects, persistent Agents, supervised terminals, evidence-backed Missions and downloads for Linux, Windows and macOS.
Why not keep running the agent the way I do today?
For small fixes, do it however works — the Direct mode exists for that. Nexus matters when the work is long, parallel or multi-agent: isolated worktrees, gates, quotas and evidence-based completion — COMPLETED_VERIFIED, not a declared "done".
Does Nexus see my code?
Nexus runs on your machine. Workspaces, terminals, runtimes and memory are local: it reports the status of the work, it does not collect your data. No third-party telemetry.
Which agents and providers work?
Agents are persistent identities; Codex, Claude, Gemini and other runners are selectable resources bound by capacity and policy. Switching providers does not switch your agent.
Is Nexus stable?
Not yet: current binaries are development previews without a signing certificate. The exact path to stable releases lives in docs/release-status.md — nothing is announced stable without evidence.
How much does it cost?
It is open source from IAPro Community, subject to LICENSE and Beta Terms. For questions and updates, join the community on WhatsApp.
Put your agents to work.
Downloads for Linux, Windows and macOS — or explore the source on GitHub and come build with the community.