NexCoderFull access
Agent
The full agentic loop: plans, edits files, runs permitted commands, and verifies the result end to end.
One engine. Every surface.
The agentic coding IDE that verifies its own work.
NexCoder plans with a visible todo list, edits files with checkpoint-backed revert, asks before running commands, and checks the result. Six chat modes and a terminal CLI - all thin policy profiles over the same agentic core.
- Modes
- Agent, Ask, Edit, Debug, Review, Scan
- Runtime
- Local GGUF or hosted endpoint
- Safety
- Checkpoints + permission gates
nexcoder - agent mode
Launch
NexCoder launches July 27, 2026.
The desktop app and terminal CLI go public on launch day - downloads for Windows, macOS, and Linux unlock then.
See it in action
A full IDE with the agent built in.
Editor, file tree, terminal, and an always-present agent panel that plans, edits, and reports back - watching your active file the whole time.
NexCoder - editor + agent
Built for real work, not demos
Direct file edits with revert, structural safety, auto-context, retrieval, skills, and hard context guarantees - in the desktop IDE and the CLI.
Agentic loop
Plans with a visible todo list, edits files directly with checkpoint-backed revert, asks permission before running commands, and verifies its own work.
Explore ->Structural safety
Read-only modes simply never receive mutating tools. Permission gates and a per-project command allowlist guard everything else.
Explore ->Auto-context
The active editor file and text selection travel with every run - "fix this" means the selected code.
Explore ->Skills
A skill catalog (commit, code-review, systematic-debugging, ...) the agent loads on demand. Projects add their own under .nexcoder/skills/.
Explore ->Context management
Token budgeting, two-stage compaction, and a hard force-fit guarantee before every model call - with a live context meter in the composer.
Explore ->Local-first
Runs fully offline against a local GGUF model server. Switching to a hosted GPU endpoint is config-only.
Explore ->Six modes, one engine
Every mode is a thin policy profile - system prompt, tool subset, turn budget - over the same v2 agentic core. Read-only modes never even receive mutating tools.
Full access
Edit
Focused file mutation. Direct edits with checkpoint-backed revert per run or per file.
Full access
Debug
Investigates failures systematically, reproduces them, and applies the minimal fix.
Read-only
Ask
Answers questions about your code. Structurally incapable of changing anything - mutating tools are never offered.
Read-only
Review
Code review over files, diffs, or modules with findings you can act on.
Read-only
Scan
Sweeps a project for issues, risks, and structure - a fast way to learn an unfamiliar codebase.
Agent Mesh
One goal, a team of specialists.
For bigger jobs, an orchestrator decomposes your goal into bounded work units and hands them to specialist agents - Explorer, Implementation, Test, and Review - then verifies the combined result. You watch the whole plan unfold, inspect any node, and cancel at any time.
- Bounded work units keep each agent focused and reviewable.
- A live timeline and per-node inspector show exactly what happened.
- One click cancels the run - queued units simply never start.
NexCoder - Agent Mesh
The same agent in your terminal
Everything the IDE agent can do, scriptable from the shell - interactive permission prompts, full-auto mode, mode profiles, skills, and JSONL event streams.
nexcoder --project C:\MyApp "fix the failing test"
nexcoder --auto --project C:\MyApp "build a landing page"
nexcoder --mode review --project C:\MyApp "review the auth module"
nexcoder "/commit group and commit my changes"The CLI shares sessions, checkpoints, permissions, memory, and skills with the desktop app through the per-project .nexcoder/ directory. Start a task in the IDE, continue it from the terminal - or wire the JSONL event stream into CI.
Local-first by design
Run fully offline against a local GGUF model server, or point at the hosted NexCoder endpoint - switching is config-only.
Your code stays local
Relevant-code retrieval ranks files and snippets on your machine. Repository content never has to leave it.
Consumer-GPU friendly
The NexCoder MoE coding model (3B active) runs on 32GB RAM plus a consumer GPU by housing the KV cache in system RAM.
Hosted when you want it
Production clients default to the hosted, OpenAI-compatible NexCoder endpoint. No local model required - just an API key in your .env.