When a saved token is missing from the Grok Bot agent environment

On Grok Bot 0.47.0 (darwin reports in forum 171441), a token can show as saved in the UI and still be absent when an executor starts a fresh process on the Agent Computer. The field looks filled; printenv / process env inside that executor does not see the value.

What is going wrong

The secure token field and the executor environment are separate paths. Saving in the UI writes the value into the secrets / token store the app shows you. A new executor process on the shared Agent Computer may start without that value injected into its environment. Work that expects $TOKEN (or a named env var) then fails even though the UI still displays a saved token.

Official computer docs: Use the computer and apps. Prefer a connector when the vendor has one — connectors avoid parking long-lived tokens in env for many flows.

Work around it with a file (same pattern as GSC-style setups)

1. Ask the Bot to write the token into an agent folder file under /workspace (for example /workspace/<project>/secrets/token.txt) with mode 0600, using the secure secret input when the Bot prompts — do not paste the token into ordinary chat.
2. Point the skill, routine, or script at that file path (cat / read), not at an env var the UI claimed to inject.
3. After any desktop reconnect, Update Agent Computer, or Recover, open the secrets UI and confirm the file still matches what you expect before a credential-dependent routine fires. Reconnect can also wipe the secrets store (When desktop reconnect wipes Grok Bot box secrets).
4. Prefer a first-party or marketplace connector when one exists for that vendor so the Bot never needs a raw env token.

Reply on 171441 with app version, OS, and whether the miss happens only in fresh executor processes so staff can verify a fix.

Pitfalls

• Trusting the filled UI field as proof the executor env has the var — check inside a fresh Shell on the Agent Computer.
• Pasting the token into chat history so it lands in transcripts.
• Leaving the only copy in the secrets store with no file bridge when a routine must survive overnight reconnects.