Choose a durable home for the Telegram token #53

Activity

1. Simon-AI-coding

   added

   wayfinder:grillingWayfinder grilling ticketWayfinder grilling ticket

   on Aug 24, 2026
2. Simon-AI-coding

   added a parent issue on Aug 24, 2026

   • Map: repair phase to v1.0 minimal launch #49
3. Simon-AI-coding

   self-assigned this

   on Aug 24, 2026
4. Simon-AI-coding

   added a commit that references this issue on Aug 24, 2026

   Add #55 (menu-bar Telegram token) to the repair charter as order 11

   ...

   94d60ad
5. Simon-AI-coding commented on Aug 24, 2026

   

   Simon-AI-coding

   on Aug 24, 2026

   OwnerAuthor

   More actions

   Resolved (Simon, 2026-08-25, grilled in-session).

   Mechanism: the shell owns the token; the engine is unchanged. A menu-bar panel row ("Telegram bot token: set / not set → Set…", write-only SecureField) writes a KEY=VALUE file, mode 0600, under the shell's Application Support base; at engine spawn (ProcessLauncher.swift:63) the shell injects it into the engine's environment under the variable config.toml token_env names, read via MinimalTOML so no constant is duplicated across languages. A pre-spawn preflight replaces today's empty Retry panel with "token not set → Set…". Saving restarts the engine. Headless checkout runs keep export.

   Ruled out, with reasons on record:

   • Keychain — Simon: the system authorisation dialog reads like credential theft to an open-source user; ad-hoc signing would re-raise it every build.
   • launchd plist EnvironmentVariables — does not apply: the engine is spawned by the login-item shell (SMAppService.mainApp), not by a LaunchAgent. The com.gpt-voicecoding.bridge plist on the reference machine is gen-1 debris (unloaded; bridge-serve) → Dispose of the gen-1 bridge remnants #54.
   • Importing from the login-shell profile — already ruled out by LoginShellPath.swift ("a second, invisible configuration file").
   • A LaunchAgent that runs launchctl setenv at login — the same invisible-file shape, outside the repo.

   Evidence that made it urgent: launchctl getenv GPT_VOICECODING_TELEGRAM_TOKEN is already empty on the reference machine after a restart; the next engine start would refuse after log adoption (the acceptance step-0 failure).

   Where it lands: repair charter order 11, ticket #55, committed to main at 94d60ad (docs/repair-charter.md) — delivered before the bundle rebuild so the manual acceptance run uses the shipped mechanism. Precedent for the gen-1 shape: config.local.plist's credentialsFile (~/.claude/channels/telegram/.env).
6. Simon-AI-coding

   closed this as completedon Aug 24, 2026