# API tokens saved as plain text in Grokbot

**URL:** <https://forum.cursor.com/t/api-tokens-saved-as-plain-text-in-grokbot/178000>\
**Category:** Bug Reports\
**Tags:** security, grok-bot\
**Created:** [November 10, 2026, 8:19pm UTC](https://forum.cursor.com/t/api-tokens-saved-as-plain-text-in-grokbot/178000 "2026-11-10T20:19:39Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [November 11, 2026, 2:36pm UTC](https://forum.cursor.com/t/api-tokens-saved-as-plain-text-in-grokbot/178000/12 "2026-11-11T14:36:56Z")

</div>

Hi @bee, that settles it: the token wasn’t copied out of the secret store, your bot built it into those git remote URLs, and a clone with the token in the URL saves it into that repo’s `.git/config`. Bots are instructed to never write a secret’s value anywhere, but as you saw, that isn’t enforced.

Until that changes, I’d give your bots a standing instruction: never put a token in a clone or remote URL, keep remotes as plain `https://github.com/owner/repo.git`, and pass the token through a git credential helper that reads the environment variable.

---

_[View the full topic](https://forum.cursor.com/t/api-tokens-saved-as-plain-text-in-grokbot/178000)._
