Audit which repositories Grok Build collected and whether xAI still lists the archives A developer created an open-source Python script to audit which repositories Grok Build has collected and whether xAI still retains the archives. The script inspects local Grok logs to find upload events and optionally checks with xAI's API whether archive IDs are still recognized, without uploading or downloading any source code. Paste this into Claude Code, Codex, or another local agent with filesystem and network access: Perform a read-only audit of Grok Build codebase collection and retention on this machine. Do the investigation with shell/Python; do not just give me instructions. Do not launch Grok, send it a prompt, upload/download archives, invoke /privacy, delete anything, or change configuration/account state. Never print tokens, session IDs, or storage object IDs. Do not create or delete even temporary files; process everything in memory or through stdin/stdout. Inspect ~/.grok/logs/unified .jsonl plus rotated logs beside it. Find repo state.upload.start and repo state.upload.enqueued . Correlate events by sid , ctx.turn number , and phase; derive an enqueued event's phase from its gcs path basename before codebase.tar.gz or after codebase.tar.gz . Map each archive to the start event's ctx.repo path . For every repository, count collection attempts and queued archives and show first/last timestamps. Then perform a metadata-only existence check: read the newest cached key from ~/.grok/auth.json without displaying it and POST the exact queued paths as {"paths": ... } batches to: https://cli-chat-proxy.grok.com/v1/storage/batch exists with Authorization: Bearer