Install it globally, as shown. Do not run setup with npx: npx runs the package from npm’s cache, and npm can clean that cache at any time. The plugin and the router service would then point into the cache and break. stolik service install refuses to run from there.
Setup asks for the bot token. Typing is hidden. Then it pairs the bot with your Telegram account.
Setup prints a six-digit code.
Open a private chat with the bot (not a group). Send it the code. The code works for 5 minutes and 5 tries. After 5 wrong codes, run stolik setup --pair to get a new one.
Setup shows the account that sent the code. Answer y to confirm it is you.
Setup does not ask again if the install already has an owner. To pair a different account, run stolik setup --pair. For scripts, stolik setup --owner-id <number> sets the owner without pairing.
You can keep the router running during pairing. Until you pair, the router answers nobody. stolik doctor reports “not paired yet”.
Setup writes two files and prints the next steps:
~/.config/stolik.env: the bot token and the owner’s chat id. Only your user can read it (mode 600).
~/.config/stolik/config.json: everything else. The owner is stored as chat.telegram.ownerUserId. A missing file means defaults.
It also offers the optional model worker for voice notes and the digest. Say no for now. You can run setup again later.
This writes a systemd user unit named stolik and starts it. The router runs in your login session, not as root. The unit runs the copy of stolik that wrote it, so keep the global install in place. Restarting the router leaves your tmux sessions and the Claude Code sessions in them running.
If you change the Node version, run stolik service install --start again so the unit uses the new one. Logs: journalctl --user -u stolik -f.
tg-claude is claude with one extra flag: --dangerously-load-development-channels plugin:stolik@indicozy. STOLIK_PLUGIN=1 selects that plugin. Without it, tg-claude looks for a user-level MCP server named stolik, and the plugin does not create one. Claude Code shows a warning screen. Press Enter. For sessions that you start from Telegram, the router presses Enter on that screen for you. Why the flag? explains what it does and why stolik needs it.
A topic named orbit-api appears in your group. Write in it from your phone.
To keep the variable, add export STOLIK_PLUGIN=1 to your shell profile. Then alias claude=tg-claude works too. Subcommands such as claude mcp and claude -p pass through unchanged.
Use this section in place of steps 1 and 2. Steps 3 to 5 of the Telegram guide stay the same. One install uses one chat app, so pick Telegram or Discord.
You need a Discord account and a server where you have Manage Server. The privacy check warns when someone else is in the server.
Setup asks for the bot token. Typing is hidden. It then prints an invite link. Open the link and add the bot to your server. The invite needs Manage Server. It grants the rights stolik needs: view and send messages, read history, add reactions, attach files, manage channels and send voice messages.
Setup then prints a six-digit code. Add the bot to your server before you send the code. Send the code to the bot in a direct message, not in a channel. The code works once, for 5 minutes. After five wrong codes it stops. Run stolik setup --chat discord --pair to get a new code.
Setup shows the account that sent the code. Answer y to confirm it is you.
Setup stores the token as DISCORD_BOT_TOKEN in the secrets file, which only your user can read. It sets chat.app to discord in the config file. Your user id goes to chat.discord.ownerUserId.
Each project folder gets its own text channel, named after the folder. The channel sits under a category named stolik. The bot creates both.
Private. @everyone cannot view folder channels or the stolik categories. Only you and the bot can.
Idle. About 2 minutes after the last session in a folder ends, the channel moves to a category named stolik-idle. A session that starts again before then keeps the channel in stolik.
More categories. A category holds 50 channels. When one is full, stolik makes the next one: stolik 2, stolik 3, and so on. Idle folders use stolik-idle 2 and up in the same way.
Server limit. Discord allows 500 channels per server. Past that, stolik cannot make a folder channel. It logs the error, and the session uses the lobby.
stolik doctor runs privacy checks on the Discord server. The router runs the same checks at start and logs what it finds. The checks only warn. They never stop the router. They report:
Whether the bot is public. A public bot gets a warning.
Whether the Message Content intent is on.
How many members the server has. Expect two: you and the bot.
Whether @everyone can see the lobby, a stolik category or a folder channel. This check runs only when the server has more than two members.
Invites are not checked, because listing them needs Manage Server. Check them yourself under Server Settings, then Invites. Remove any invite you do not know.
Voice notes, voice cleanup and the digest use a local model worker: faster-whisper for speech and a small Qwen model for text. Models download on first use, load on demand and unload after 10 minutes idle.
Run stolik setup again and say yes at the model step. The worker lives in the package folder (ml/.venv), so you must be able to write to the global npm folder. If you cannot, set a prefix you own first with npm config set prefix ~/.local, then reinstall. It needs:
macOS (untested).brew install tmux node, then the same steps. The service is a LaunchAgent. Nobody ran this on a Mac yet. Tell us what breaks.
Windows (WSL2, untested). Install Ubuntu in WSL2, turn systemd on in /etc/wsl.conf, then follow the Linux steps inside WSL. WSL has no desktop session, so stolik treats you as always away and sends every answer.
stolik migrate copies your old tg-bridge settings and state into the stolik locations. It does not move anything. Your old files stay where they are.
Stop the old service. Run systemctl --user disable --now tg-bridge. On macOS, run launchctl bootout gui/$(id -u)/com.tg-bridge.router. stolik migrate refuses to run while the old service is up.
Run stolik migrate. stolik setup runs the same copy first when it finds the old files. Then start stolik with stolik service install --start.
In Claude Code, remove the tg-bridge@indicozy plugin and add stolik@indicozy. The channel tools are now named mcp__stolik__…. Update any CLAUDE.md, hook or setting that names mcp__tg-bridge__.
Doctor checks Node, tmux and claude, the config and token file, the database, the addons and, with the token, the bot and its rights in the group. It names the check that fails.
On Discord, doctor also checks the bot token, the lobby channel and the stolik categories. It runs the privacy checks described above.