nodConsole for macOS

Every coding agent, one console

Claude Code, Codex, Cursor and the rest run as background processes on your Mac. nodConsole streams what they do and turns them into flows your team can run, watch and review.

macOS 26 · Apple silicon · direct download, notarized

The loop

Describe the work. Let it run. Review what came back.

The same four steps whether the agent is fixing a bug in a repo or drafting replies in an inbox. nodConsole only changes what you see at review time.

  1. 1 · Task

    Say what needs doing

    A task sits with the team, not a person. It names the work and the project it targets, and anyone can pick it up.

  2. 2 · Run

    Pick a flow, press run

    Each step of the flow chooses its own agent, model and effort. The run happens on your Mac, inside the project's folder.

  3. 3 · Review

    Watch it, then read it

    Output streams live while the agent works. At the end you get a branch and a diff, not a wall of chat.

  4. 4 · Approve

    Apply, or throw it away

    Approve to keep the branch, open a pull request, or discard it. A comment on your task reaches you wherever you are.

Flows

A few steps on a canvas, each with the agent it deserves

A flow is a reusable recipe: plan with one agent, implement with another, review with a third. It isn't tied to a project, so the same flow works on every codebase your team has.

  • Per-step agent, model and effort level.
  • Flows start personal. Share one with the team, and anyone can fork it and keep their own version.
  • Long runs can be watched step by step, or left alone until the review card shows up.
Start
Plan the changeClaude Code · Fable · high
Implement itCodex CLI · gpt-5-codex · medium
Review the diffCursor Agent

Works with

The agents you already have installed

nodConsole finds the CLIs on your PATH and runs them headless. Missing one? It installs through npm or Homebrew, never a script piped from the internet.

Next up: Gemini CLI Copilot CLI Qwen Code Kimi Code

Built for teams

One table of work, many Macs running it

Tasks belong to the team. Projects belong to the team. The only thing that's yours is where a project lives on your machine.

  • To do
  • In progress
  • Waiting
  • Done

Tasks

Four states anyone can set. A task targets a project, picks a flow, and keeps its runs and comments in one place.

nodconsole → ~/Developer/nodworks

Projects

A project is a repo the team shares. Each person points it at a folder on their own Mac once, and every task of that project runs there.

Ece commented on Rate-limit invites2 min ago · Notifications

Notifications

A comment on your task, a run that finished, a review waiting on you. The bell in the rail keeps the list.

Local by design

Your agents, your keys, your folders. The cloud carries the team.

Agents run as ordinary processes on your Mac with the PATH and credentials you already use. nodConsole cloud holds only what the team shares: tasks, flows, projects and notifications. The app ships as a notarized direct download, outside the App Store, because a sandboxed app can't run your CLIs.

Early access

Get an early build

Builds go out by hand, in order. Tell us which agents you run so yours is set up for them.

Agents you run