telekit: command not found
Compiled: ~/.local/bin not on PATH. Source: run ./install.sh again.
Daemon not loaded
telekit restart, then telekit daemon status.
getUpdates conflict: yes
telekit daemon status prints this when the bridge itself lost Telegram’s
one-reader-per-bot rule. Another consumer holds this token (another Mac user,
another machine, or a pasted shared token). Create a new bot with
@BotFather for this Mac user. Do not paste someone else’s token.
This is not the same as telekit inbox while the daemon is running. That
conflict is expected: stop the daemon, read the inbox, start it again.
Bot does not answer
- Private chat with no reply: continue below. Allowed group with no reply: Group chats — when it stays silent. The bot never says “not allowed” in a group.
telekit auth status— token and owner id.- Passcode on? Send
/pw. - Message paused? Send
/accountor open telekit.io/account. - Check
~/.telekit/bridge.log.
/node empty or one folder
No named catalog on this Mac, or the catalog has no projects you can see. The owner can still /node ~/path/ to seat a folder. /node home returns to TELEKIT_WORKING_DIR.
Harness refused
/harness lists Installed vs Not installed. Put the CLI on PATH or pin TELEKIT_*_BIN and telekit install again, then telekit restart.
Codex fails in home
Codex refuses to run outside a git repo. PinTELEKIT_WORKING_DIR to a real repo.
self-update refuses
You are on a source/editable install. Use git + telekit restart.
Formatting looks like raw Markdown
Reload the daemon (/restart) so it is running this version. Local file links render as label — path. Web URLs are tappable.
Fast lane never fires
telekit ack status — need a stored OpenRouter key and /ack on.
Voice note arrives as a file
Runtelekit voice status. Voice may be off, or ffmpeg, ffprobe, whisper-cli, or the model may be missing. Follow the printed fix, or rerun telekit voice setup --yes on a Mac with Homebrew. Then run telekit voice test /path/to/note.oga on a local audio file. Setup failures leave the bridge usable; if a first install reported one, run setup again after fixing it. See Voice notes.
/stop says it stopped, but the turn is still running
Send /stop (or /x) again. Do not /restart to unstick one turn — that
kills every other live turn too.
A long quiet think is not a stop. After 15 minutes of no output you get one
still running note. /stop cancels now.
”I got an unreadable response from the session”
The harness process died mid-turn (usually its API stream dropped — it hits several lanes at once). Your thread is kept. Send your next message as normal. On that next message the harness first repairs the broken turn. If it answers with nothing, Telekit sends the same message once more by itself. If it comes back empty twice, you get “that message was not answered” — resend it, or/new to start fresh. You never get a silent (the session returned no text)
for a lost message.
Send did nothing
You omitted--yes. That is a dry run.