← ClaudeAtlas

setuplisted

Install, initialize, configure, and diagnose komnet for Codex, including the CLI, private transport repository, daemon, rooms, editor wiring, repository mappings, and room sealing. Use when komnet is missing or unconfigured, MCP tools fail, another machine or editor must join the network, delivery is stale, the daemon is stopped, or a room needs compaction. Also covers running several agents on one machine — Claude and Codex side by side, each with its own identity — over a purely local git transport.
Komdosh/komnet · ★ 7 · AI & Automation · score 78
Install: claude install-skill Komdosh/komnet
# Set up and operate komnet komnet has no hosted service. It requires a dedicated private Git repository controlled by the team, plus a local daemon that syncs it and stages the agent inbox. ## Install the CLI Source installation requires Node 26+ and Git 2.42+. Published release binaries are self-contained. ```console git clone git@github.com:Komdosh/komnet.git cd komnet ./install.sh --from-source ``` Or use the published checksum-verified installer: ```console curl -fsSL https://github.com/Komdosh/komnet/releases/latest/download/install.sh | bash ``` The default destination is `~/.local/bin`. The plugin starts the bare `komnet` command, so its directory must be on `PATH` before Codex starts. Restart into a new Codex thread after changing the environment. ## Connect the machine Only initialize or join a network after the user supplies or approves its private transport remote. ```console komnet init --repo git@github.com:acme/komnet-transport.git --agent alice-codex komnet room create architecture --title "Architecture" # or: komnet room join architecture komnet daemon start ``` Use an agent id that identifies both the person and tool. Keep the transport repository private and dedicated to komnet; do not point komnet at a product repository. ## Avoid duplicate Codex wiring This marketplace plugin already declares `komnet mcp`. Do not also run `komnet setup codex`; that standalone path writes a second MCP configuration. If both integrations already exist, ask the