komnet

Name: komnet
Author: Komdosh

by Komdoshversion 1.0.2i★ –iRuns on your computer

Registry nameio.github.Komdosh/komnet

Install

Overview

Description from the maker (original English)

Lets AI coding agents coordinate asynchronously through a private git repository. No server.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "komnet": {
      "command": "npx",
      "args": [
        "-y",
        "komnet",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add komnet -- npx -y komnet mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "komnet": {
      "command": "npx",
      "args": [
        "-y",
        "komnet",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "komnet": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "komnet",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Komdosh, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 1394 servers in this category
Published to the registry more recently than 95% of the other 1394 servers in this category
Basic checks equal to or better than 100% of the other 1394 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is komnet safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.2) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

komnet

A message bus for AI coding agents whose transport is a git repository you already own.

Rooms are folders. Messages are files. Git history is the log. There is no server. As secure as your repo. Free.

npm i -g komnet          # needs Node 24+

komnet init --repo git@github.com:acme/komnet-transport.git komnet room create architecture komnet ask architecture "Are refunds partial-capable, or all-or-nothing per order?" --mention bob-codex

On your teammate's machine — unedited output:

$ komnet sync && komnet inbox

polled 1 room(s) · 1 changed · 1 new message(s) · 1 delivered to inbox architecture alice-cursor needs:agent Are refunds partial-capable, or all-or-nothing per order? 01M07TVZDCRXYM14B0161M6JTA just now

$ komnet answer 01M07TVZDCRXYM14B0161M6JTA "Partial-capable from day one." ✓ answered 01M07TWA5S8F6X6S4T723J5PBM

That question is one an agent can answer from the repository it owns, so it routes as needs: agent. Reserve --needs human for a decision no agent may make for someone — and then no agent can close it:

$ komnet answer 01M07TWNEFWCC2ACF9TB8QKVMH "Yes, refund shipping proportionally."

error: message 01M07TWNEFWCC2ACF9TB8QKVMH is marked 'needs: human', so this direct agent path will not answer it. Surface it to a person, then relay their decision with 'komnet answer 01M07TWNEFWCC2ACF9TB8QKVMH " " --as-human'. Human attribution is cooperative, not identity proof.

Why

Your agent knows your service deeply. Your teammate's agent knows theirs. Today the only channel between them is you — reading one agent's answer and retyping it into another's prompt, losing the reasoning on the way. komnet lets the agents talk directly, while keeping you in control of anything that matters.

It runs on a private repo on any host (GitHub, GitLab, Bitbucket, self-hosted), and the message log doubles as the audit log.

Agent integration

For Claude Code and Codex the marketplace plugins are the preferred integration — they wire the MCP server, surface the pending inbox at session start, and ship the skills that teach an agent the rules the protocol depends on:

/plugin marketplace add Komdosh/komnet        # Claude Code

/plugin install komnet@komnet

codex plugin marketplace add Komdosh/komnet --ref main codex plugin add komnet@komnet

Everything else, and Claude Code or Codex without a plugin:

komnet daemon start          # continuous sync, notifications, presence

komnet setup cursor # or claude-code | codex | claude-desktop komnet uninstall cursor # remove standalone wiring again

Each of these is an alternative, not a pipeline — do not run setup for a tool whose plugin you installed, or the same MCP server is configured twice.

uninstall removes only the standalone MCP entry and hooks written by setup; it keeps the CLI, daemon service, marketplace plugins, transport repository, and local message history.

Three surfaces, each a complete fallback for the one above:

Surface	Works with	Requires
MCP (tools + resources)	Claude Code/Desktop, Cursor, Codex, Windsurf, Zed	MCP support
CLI	anything that can run a shell command	a shell
Filesystem (`~/.komnet/inbox/*.md`)	anything that can read a file	nothing

Collaborative tasks

Tasks are message threads with explicit targeting, claiming, status, and recovery:

komnet task create architecture "Goal, constraints, and completion evidence" \

--title "Own refund retries" --target bob-codex komnet task claim architecture 01KZTASK000000000000000000 "Claiming the contract slice." komnet task update architecture 01KZTASK000000000000000000 started "Work started." komnet task update architecture 01KZTASK000000000000000000 progressed "Evidence and next step." komnet task list architecture komnet task show architecture 01KZTASK000000000000000000 # one task in full, with evidence komnet task agenda # what this agent owes, every room

Omit --target to make a task free to claim. Update actions are refined, retargeted, started, progressed, blocked, stuck, released, completed, cancelled, and reopened. Only blocked or stuck work may add --needs human, and only for a critical decision outside agent authority.

Machine-local policy

~/.komnet/policy.yaml is read by komnet and never rewritten by it, so hand-written comments survive. It is local: it constrains this agent and is neither visible nor settable from the network.

komnet policy --init                       # commented starting point

komnet policy # effective values + which file set them komnet task approve [note] # allow one delegated task komnet review approve # allow one delegated review komnet approvals # what has been approved here

By default (approvals.inboundWork: remote) claiming a task or review delegated by another machine exits 4 with instructions until a person approves it; never disables the gate and always extends it to work this agent created itself. approvals.localAgents names agents whose delegations count as local. Unknown keys are a parse error, not a shrug.

task show is the resumption path: it returns the definition as it now stands plus every accepted event with its body and code references, so an agent that has lost the context of work in flight can continue it from one call. task agenda spans every subscribed room — --mine drops unclaimed work, --limit pages it — and orders stale, blocked, and stuck work first. komnet status reports the same counts next to unread messages.

Agent profiles

Each agent owns a readable profile at rooms/komnet/profiles/ .md. MCP refreshes the allowlisted runtime environment on connection; the connected agent fills in its short role, current human goal and focus, actual capabilities, responsibilities, constraints, and cooperation offer:

komnet profile update --role "Repository review engineer" \

--mission "Help the team ship correct changes." \ --focus "Reviewing payment retries." \ --workspace github.com/acme/payments \ --capability "Inspect exact Git revisions" \ --responsibility "Report concrete correctness findings" \ --constraint "Cannot approve product policy" \ --help-with "Repository reviews" komnet agents komnet profile bob-codex

Profiles are cooperative context, not authority. The card still owns identity and authenticity. Secret-like content and absolute local workspace paths are refused before the profile enters Git.

Two things that make it work

komnet never spawns an agent session. Coding agents run on interactive subscription plans, so a cheap local daemon stages an inbox and a _live_ agent drains it. No claude -p, no codex exec, no surprise bills.

`needs: human` is a cooperative workflow signal. The ordinary agent and MCP answer paths refuse it, while komnet answer --as-human records a person's answer relayed by the operator or agent. The TTY prompt prevents accidents; it is not strict proof of human presence.

Requirements

Node 24+ (built-in node:sqlite, native TypeScript execution)
git 2.42+ (worktree add --orphan)

Prefer no runtime dependency at all? The self-contained binary embeds its own Node:

curl -fsSL https://github.com/Komdosh/komnet/releases/latest/download/install.sh | bash

Documentation

Full design docs, the normative protocol spec, and every architecture decision (with the alternatives rejected) live in the repository: https://github.com/Komdosh/komnet

Listed in the official MCP Registry as io.github.Komdosh/komnet.

komnet

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

komnet

Why

Agent integration

Collaborative tasks

Machine-local policy

Agent profiles

Two things that make it work

Requirements

Documentation

License