shadok-ai weekly downloads statistics

<div align="center"> <h1>shadok-ai</h1> <h3>Many Claude Codes. One cockpit. And it wrote itself.</h3> <p>Run <b>real</b> Claude Code sessions side by side, each in its own git worktree, on the Claude subscription you already pay for. When one of them has a question, you answer it with a click — in the browser, or from Telegram when you are not at the desk.</p> <p> <a href="https://www.npmjs.com/package/shadok-ai"><img alt="npm" src="https://img.shields.io/npm/v/shadok-ai?color=F5A524&amp;label=npm"></a> <a href="LICENSE"><img alt="licence AGPL-3.0" src="https://img.shields.io/badge/licence-AGPL--3.0-7C6CF0"></a> <a href="https://shadok.ai"><img alt="shadok.ai" src="https://img.shields.io/badge/shadok.ai-F5F0E6?labelColor=08090D"></a> </p> <p><code>npx shadok-ai</code></p>

<a href="https://shadok.ai"><img width="720" alt="The cockpit: three agents running in parallel, one of them asking a multiple-choice question that is answered with a click, then the diff it wrote" src="https://shadok.ai/demo.gif"></a>

</div>

It does not stop at one. An agent can start other agents — each with its own worktree, branch and role — and it is told when one of its own finishes, blocks on a question, or dies. Nothing else wakes it.

It keeps working when you are not there. Mirror an agent to a Telegram topic and answer from your phone, one topic per agent. Put a prompt on a schedule with a guard that runs without the model: prints nothing, nothing happened, zero tokens spent.

It stays on a leash. A profile is a role plus guardrails — forbid git commit and the agent cannot commit. Secrets live in a vault outside your repository and are injected only into the agents that need them. Quota gauges show the 5h and 7d windows, and can hold an agent back when it is burning faster than the window elapses.

It wrote itself. shadok-ai is largely built by agents running inside shadok-ai, in their own worktrees, landed as reviewed pull requests. The section below is what that produced.

Quick start

npx shadok-ai

It opens your browser for you once the server is listening — at the port it actually landed on, which is not always 3789 (a busy port walks to the next free one). Only on the launch you asked for: an auto-update respawn never pops a tab. Skipped where it would make no sense — in a container, over SSH, or on a Linux box with no display — and --no-open turns it off.

Prerequisites: Node ≥ 20. shadok-ai drives the claude CLI on your Claude subscription — if it isn't installed, the cockpit installs it for you on the first agent launch (npm i -g @anthropic-ai/claude-code; if that can't write the global dir it tells you the one command to run). Either way you sign in to your Claude account once on first use — that step is yours and can't be skipped (see below). tmux makes agents survive the server restarting, so shadok-ai auto-installs it at boot if it's missing (brew on macOS, apt/apk/dnf/pacman on Linux — with sudo when not root). If it can't (no package manager, or a sudo password it can't provide), it falls back to node-pty and tells you the one command to run. SHADOK_TMUX=0 skips all of that.

On the first run it asks once for an optional Telegram bot token (press Enter to skip; you can add it later from the web UI).

Flag	Effect
--port, -p <n>	HTTP/WS port (default 3789; falls back to the next free one)
--no-telegram	web-only; don't prompt for or use a bot token
--no-open	don't open the browser on launch
--password <p>	require this password to open the GUI (stored in config)
--version, -v · --help, -h	version / help

What you get…