01Intro

Software Development
Process Resolved

nmux is a workflow engine that executes your defined AI-driven development process consistently and repeatedly, the same way, every time.

Specification inProduction-grade PR out

  • TODO
  • └─ host-seam {spec slice 2} · 5/9
  • ├─ Sandbox crate and engine re-export so existing call sites compile
  • ├─ Move the accept loop into the leaf crate, generic over the trait
  • │ (blocked)
  • ├─ Stub-host test in the leaf crate: spawn, connect, invoke, callbacks
  • ├─ Gate: workspace check, clippy on the leaf crate, full touched-crate tests, e2e 37/37
  • └─ Adapt the moved loop's own tests against the stub host. The loop's ~350-line test module constructs SandboxServerState with the engine's registry and asserts on it, so the stub host (AC#5's deliverable) is what these tests must be rewritten against. The loop move and the stub-host test are one piece of work, not two.
  • Working

Shared

knowledge

Unified

process

Unlimited

scale

02Process

Spec in. Production PR out.

One pipeline. Your standards. Every run.

Use the standard workflow or build your own. Specialized agents handle each step, and every run leaves a full trail you can trace and repeat.

  1. 01

    Intent

    Developer

  2. 02

    Specify

    Agent + Developer

  3. 03

    Build

    Agent

  4. 04

    Verify

    Agent

  5. 05

    Deliver

    Developer

03Problem

AI made coding faster

And engineering harder to control.

Right now, your best AI workflow probably lives in one engineer's head. The rest of the team works their own way, reviews fall behind, and standards drift. Faster individuals don't add up to a faster team.

The problem

  1. 01

    How do we get everyone coding to the same standards?

  2. 02

    How do we know what the AI actually did?

  3. 03

    How do review and testing keep up with AI speed?

  4. 04

    How do we turn one good workflow into the team's workflow?

  • Developer A

  • Developer B

  • Developer C

  • Developer D

Repository

The solution

  1. 01

    Your standards are enforced in every run, not just written down in a doc.

  2. 02

    Every step is recorded, from spec to pull request, so you can see exactly what the AI did.

  3. 03

    Review and testing are built into every run, so they move at AI speed too.

  4. 04

    Define a good workflow once, and the whole team runs it, whatever tools they use.

  • Developer A

    nmux

  • Developer B

    nmux

  • Developer C

    nmux

  • Developer D

    nmux

nmux

Repository

04How it works

See nmux in action

The real product, as it runs today.

The final process is still taking shape. Book a short walkthrough to see the current system run live with one of our engineers.

  • TODO
  • └─ host-seam {spec slice 2} · 5/9
  • ├─ Sandbox crate and engine re-export so existing call sites compile
  • ├─ Move the accept loop into the leaf crate, generic over the trait
  • │ (blocked)
  • ├─ Stub-host test in the leaf crate: spawn, connect, invoke, callbacks
  • ├─ Gate: workspace check, clippy on the leaf crate, full touched-crate tests, e2e 37/37
  • └─ Adapt the moved loop's own tests against the stub host. The loop's ~350-line test module constructs SandboxServerState with the engine's registry and asserts on it, so the stub host (AC#5's deliverable) is what these tests must be rewritten against. The loop move and the stub-host test are one piece of work, not two.
  • Working

05Features

Key features

Built your way. Run by agents. Proven at every step.

Your process. Your rules.

Start from ours or build your own.

Pick a ready-made workflow or shape one around how your team already works. You decide the stages, the quality checks and who signs off where.

Workflow configuration

Custom

StandardCustom

Team development workflow

  • SpecifyRequirements

  • BuildImplementation

  • VerifyQuality gates

  • DeliverPull request

The right agent for every step.

Each one an expert. All in sync.

Specialized agents write the requirements, build, review and test. nmux passes the work between them, so nothing stalls between steps.

Workflow execution

In progress

  • SpecifyRequirements agent

    Complete
  • BuildImplementation agent

    Complete
  • VerifyReview agent

    In progress
  • DeliverDelivery agent

    Queued

Repeatable by design.

Same quality, whoever runs it.

Every task goes through the same stages and checks, whichever engineer starts it. Delivery becomes predictable, and quality stops depending on who's at the keyboard.

Workflow runs

Process v1.4

RUN-1042SpecifyBuildVerifyDeliver
RUN-1043Specify

Every step accounted for.

See what happened, and why.

Follow any task from spec to pull request. Every stage keeps its artifacts and check results, so reviewers can check the work before they approve it.

Run details

RUN-1042

  • Specificationspec.md

    Recorded
  • ImplementationChangeset

    Recorded
  • VerificationReview results

    Passed
  • DeliveryPull request #128

    Ready for review

06Compare

Comparison

Not prompting. Not replatforming.

Harnesses make individual engineers fast and platforms promise governance eventually, while nmux gives your team both on day one, on your terms.

Harnesses: Claude Code, Codex, Cursor. Enterprise platforms: “software factories”.

Adoption model

Harnesses
Bring your own
Platforms
Replatform
nmux
Augment

Time to first value

Harnesses
Minutes (per engineer)
Platforms
3 to 6 months
nmux
First day (team-wide)

Pipeline

Harnesses
None, one shot
Platforms
Platform-defined
nmux
Yours, end-to-end

Standards enforcement

Harnesses
Engineer's discretion
Platforms
Vendor-defined
nmux
Yours, enforced at the gate

Reproducibility

Harnesses
Stochastic
Platforms
Vendor-defined
nmux
Same spec, reproducible pipeline

Audit trail

Harnesses
Git history only
Platforms
Platform-managed
nmux
Per-artifact, in your repo

Code residency

Harnesses
Vendor inference
Platforms
Vendor cloud
nmux
Your environment, always

Failure mode if dropped

Harnesses
No process to fall back on
Platforms
Engineers route around it
nmux
Uninstall. Nothing breaks.

07FAQ

Frequently asked questions

08Get started

Ready to get started?

Watch a spec turn into a pull request.

30 minutes with an engineer. Nothing to prepare.