The MeshKore daemon

One file. Pure Python standard library. No pip, no npm, no installer, no admin rights — runs identically on Mac, Linux, and Windows with any Python ≥ 3.8.

py

Install + run

canonical · stdlib only

From the root of any repo that has (or will have) a .meshkore/ folder: 

# 1. Download the daemon (one stdlib-only Python file)
mkdir -p .meshkore/scripts
curl -fsSL https://meshkore.com/reference/cluster/scripts/daemon.py \
     -o .meshkore/scripts/daemon.py

# 2. Run it. That's the whole install.
python3 .meshkore/scripts/daemon.py

First run mints a bearer token at .meshkore/credentials/portal-token, binds the first free port in 5570–5589, and starts serving HTTP + WebSocket. Open architect.meshkore.com in a browser — the cockpit auto-discovers the daemon on localhost.

Files in this directory

File Purpose Stable URL
daemon.py The cluster daemon. HTTP + WebSocket server. Cron scheduler. Chat coordinator. Single file, stdlib only, ~1700 lines. /reference/cluster/scripts/daemon.py

Every URL above is stable — bookmark it, link to it from agent prompts, paste it in your editor's rules file. The published bytes equal the source of truth at webapp/reference/cluster/scripts/daemon.py in the meshkore monorepo (deploy is one-shot via wrangler pages deploy; integrity verifiable with diff <(curl -fsSL …)).

Why a single Python file?

Audit friction = 0

Enterprise laptops quarantine unsigned binaries. They don't quarantine plain text scripts you can cat. Your security team can read 1700 lines of stdlib Python in 30 minutes and approve it once for the company.

No platform fork

Same file on Mac, Linux, Windows. No meshcore-darwin-arm64, no .exe. Whatever architecture has Python 3.8+, has the daemon.

Stdlib only

No pip install, no venv, no requirements.txt. It uses http.server, socket, threading, subprocess, json — all batteries-included.

One process owns everything

State server, cron scheduler, chat coordinator, WS hub, runner spawner. No LaunchAgent, no systemd unit, no cron-tab. The daemon you start is the cluster, end-to-end.

Multi-project on the same machine

Each daemon owns one repo. To run several projects on the same machine, start one daemon per repo — each picks the next free port in 5570–5589: 

$ cd ~/dev/foo  && python3 .meshkore/scripts/daemon.py &     # → :5570
$ cd ~/dev/bar  && python3 .meshkore/scripts/daemon.py &     # → :5571
$ cd ~/dev/baz  && python3 .meshkore/scripts/daemon.py &     # → :5572

The Architect cockpit's Projects rail lists all of them. Click one to scope every action to that project.

Verify integrity

The daemon you download is the same file that lives in the meshkore monorepo. To verify: 

$ curl -fsSL https://meshkore.com/reference/cluster/scripts/daemon.py | sha256sum
# Compare against the commit hash printed at the top of webapp/reference/cluster/scripts/daemon.py
# in the open-source monorepo.

After install