SurfaceWhat it is
Mac appStandalone Telekit.app. Wizard, Settings, compiled bridge, account/credits.
CLItelekit on PATH. Same bridge. Source checkout or compiled runtime.
LinuxCLI + systemd user unit. No Settings UI.
Every later Telegram command is the same.

​
Mac Settings (Mac app only)

Settings → General — harness, working folder, Keep Awake, logs, updates. Settings → Personas / Skills — file bodies, apply a persona to a bot tile. Linux uses telekit persona / telekit skill instead.

​
Compiled vs source

  • Compiled (~/.telekit-runtime/<version>/): telekit self-update talks to https://telekit.io/api/v1/bridge.
  • Source / editable (this is a git checkout): self-update refuses. Upgrade with git. Reload the daemon with telekit restart or /restart.
The installer never touches ~/.telekit state or the Keychain.

​
Linux notes

  • Token and owner id live in the Linux secrets file, not Keychain.
  • telekit install writes a systemd user unit.
  • Codex, Claude, OpenCode, SOV, and Grok still must be on PATH (or pinned with TELEKIT_*_BIN).

​
Working folder

  • Default: every message runs in TELEKIT_WORKING_DIR (the home lane).
  • /node ~/path/ seats a folder for later turns (owner).
  • If a named project list is present on this Mac, /node shows it and /node <name> switches.