Coming soon

For macOS 26

Every Coding Agent, One Console

nodConsole runs Claude Code, Codex, Cursor, OpenCode and Grok on your Mac, next to local models and any OpenAI-compatible API you already use. Give them tasks in your repositories, or describe a job once and let it run, asking you where it matters.

Coming soon to macOS 26 See how it works
  • Ollama
  • LM Studio
  • OpenAI
  • DeepSeek
  • Mistral
  • OpenRouter
  • Groq
  • xAI
  • Together
  • Claude Code
  • Codex CLI
  • Cursor Agent
  • OpenCode
  • Grok Build

Runs the coding agents already on your Mac

…and models on your own Mac, or any OpenAI-compatible API you already pay for

Two sides, one app

How will you use nodConsole?

Sign-up asks one question, and it only picks where the app opens. Both sides are always one click away.

Code

I write code

Agents take tasks in your repositories, work on their own branch, and you ship the result.

  • Overview
  • Inbox
  • Tasks
  • Projects
  • Workflows
  • Chats
Follow a task

Automate

I want to automate my work

Describe a job once (answer messages, send reports) and it runs on its own, asking you where it matters.

  • Overview
  • Runs
  • Workflows
  • Chats
  • Connections
Follow a workflow

Code

From a task to a merged branch, with you at every turn that matters.

  1. 01

    Write the task

    One thing the team has agreed to do. It gets its project's next number, like BIL-14, and a place on everyone's list.

  2. 02

    Put a workflow on it

    Each step names the agent and model that does it, and the agent that checks it. Steps can run side by side, and go back when the work isn't right.

  3. 03

    It runs on its own branch

    Every run works in its own git worktree, one commit per step. A step you want to see for yourself waits: approve and continue, see the changes, or send it back.

  4. 04

    You ship the result

    Read every changed file, then merge the branch, open a pull request on GitHub, or throw the run away. Nothing lands until you say so.

Automate

Describe a job once. It runs on its own and stops where you want to look.

  1. Say it in a chat

    “Every Friday at 17:00, post the week's new signups from Stripe to Slack.” The agent makes the workflow, and asks before it connects anything.

  2. Give it a clock

    Every 15 minutes between 09:00 and 22:00, or Mondays at 09:00. It runs on this Mac while the Mac is awake and nodConsole is open.

  3. Check it before it goes out

    A step you check stops the run. Read what came in, edit the words that go out, skip what shouldn't, approve the rest.

  4. See what it got done

    The Overview counts the week: what ran, what got done, what waits on you and what comes next. Every run keeps a record of what it did, searchable and exportable as CSV.

Workflows

Workflows Run, You Review

A workflow is a set of steps, each done by an agent on your Mac. Draw it on the canvas, or ask an agent to draw it for you. One canvas for both sides: a workflow lives on one, and can be moved to the other.

illustrative screen · sample data

  1. 1

    Any agent, any model

    Each step picks its CLI, its model and how hard it thinks.

  2. 2

    A second agent checks

    Another agent reads the work before the run goes on.

  3. 3

    Side by side

    One step hands on to several that run at the same time.

  4. 4

    If it isn't right, back

    A step goes back to an earlier one, up to the times you set.

  5. 5

    You approve

    Mark a step as yours and the run waits for you there.

  6. 6

    Ask an agent

    Say what should change and an agent builds or changes the workflow.

Chats

A chat that uses the app for you.

Ask in your own words. The agent makes the task, runs the workflow, reads what it did and tells you, inside nodConsole itself.

Move the webhooks to v2Claude Code · Sonnet
Merge run 1 into main?

Anything that goes out, can't be undone or speaks in your name waits on a card like this until you say yes.

illustrative screen · sample data

Agents on this Mac

Local CLIs, Live Output

nodConsole doesn't bring its own model. It runs the CLIs you already use, signed in with your own accounts, and shows what they do as they do it.

  1. 01

    Finds each CLI on this Mac and reads its version.

  2. 02

    Installs and updates it with the vendor's own command.

  3. 03

    Checks the sign-in of every CLI that has one, and opens it when it's missing.

  4. 04

    Adds any OpenAI-compatible API, local ones like Ollama included. Its key stays in this Mac's Keychain.

Models

Your own models, on your own Mac.

Next to the coding CLIs, nodConsole takes any model that speaks the OpenAI API: one running on this Mac, or one you already have a key for. A workflow step, the check on another agent's work, or a chat can use it.

OllamaOn this Mac · no key
LM StudioOn this Mac · no key

Local models

The models you pulled with Ollama, picked from its local server.

The models you loaded in LM Studio, picked from its local server.

  • OpenAI
  • DeepSeek
  • Mistral
  • OpenRouter
  • Groq
  • xAI
  • Together
  • Custom

APIs

Or any other address that speaks the OpenAI API, like z.ai's GLM models: add it as Custom, with its URL and key.

  1. 01

    Keys stay in this Mac's Keychain, never on nodConsole's server.

  2. 02

    Asks the API for its models: pick the ones to use, and test that it answers.

  3. 03

    Mix them in one workflow: a local model writes the plan, Claude Code makes the change, DeepSeek checks it.

A model reached this way writes words: plans, reviews, drafts, answers. Editing files, running commands and acting on connected services stays with the coding CLIs.

Connections

The tools your work lives in, one sign-in away.

Each service has its own page in the app: what an agent can do with it, what it needs, and how to connect it. Each side offers the ones that serve its work.

450+

services in the catalog, from Slack and Stripe to Shopify and Trendyol

200+

sign in through the service's own MCP server, in your browser

The rest take a key. It stays in this Mac's Keychain, not on the server, and not in a transcript.

Code

Where the work is planned

Issues, beside the code that closes them

Linear, Jira, GitLab: an agent reads the issue it works on and writes back when it is done, after your yes.

Know when it breaks

Errors and traces, where they are fixed

Sentry, Datadog, Grafana: an agent reads the error it was asked to fix, with its stack trace, logs and traces.

Where it runs

Deploys and databases, looked after

Vercel, Railway, Supabase: a deploy's logs or a database's tables, read without leaving the task.

Automate

Where most workflows start

Mail and forms, answered for you

nodConsole watches a mailbox and takes calls from any app, a form among them. A step drafts the answer; it goes out after your yes.

Answer people where they write

Messages, one place to answer from

A Slack channel, a Telegram bot, a Discord server.

Follow what changes

Orders and payments, looked after

Shopify and Trendyol orders, Stripe payments: a step reads what changed and prepares what comes next.

Team

Everything belongs to a team, even if it's just you.

You stay in charge

Agents do the work. You choose what waits for your yes.

Its own branch

A run works in its own worktree. Your checkout stays as it is until you merge.

Asks first

In a chat, sending, deleting, merging or anything in your name shows a card first and waits for your yes, unless you told it to always allow.

Keys in the Keychain

Handed only to the steps of workflows that use them, and removable any time.

Your agents, your accounts

The CLIs run on your Mac with your own subscriptions. nodConsole adds none of its own.

Made for the Mac

Native to the Mac.

Every Coding Agent, One Console

Bring the agents you already pay for into one app, and let them work while you decide what matters.

Coming soon to macOS 26

It starts on the Mac. Windows, the web and phones come later.

  • macOSFirst
  • WindowsComing soon
  • WebComing soon
  • MobileComing soon

Hear when nodConsole is out

Leave your email and we'll write once, when you can download it.

We keep only your address and language, for this one mail. See our privacy policy; write to info@nodconsole.com to be taken off.