Grok Bot 0.47.0 on Ubuntu 24.04: first-time setup fails with ENAMETOOLONG writing sand-client-<huge token>

Support Bug Reports
, ,
1

Describe the Bug

Use category Grok Bot if the form asks.

Copy everything below the line.

Title: Grok Bot 0.47.0 on Ubuntu 24.04: first-time setup fails with ENAMETOOLONG writing sand-client-<huge token>

Where the bug appears (feature/product): Grok Bot

Describe the Bug

Official Linux package grok-bot 0.47.0 (amd64) fails first-time setup after browser sign-in at Auth | Cursor - The best way to code with AI.

The app shows:

Grok Bot couldn’t finish setting up

edge/handler-failed: ENAMETOOLONG: name too long, open ‘/home/jamie/.config/Grok Bot/sand-client-<very long token>’

The last path component is longer than Linux NAME_MAX (255 bytes). The client is using a long session/device token as a filename. Setup dies on a local open(), not on reaching the cloud computer.

Screenshot of the dialog is attached. The on-screen path is already truncated; I am not pasting the full token.

Steps to Reproduce

  1. Install grok-bot 0.47.0 on Ubuntu 24.04. Package status: ii grok-bot 0.47.0 amd64. Binary: /usr/bin/grok-bot → /opt/Grok Bot/grok-bot.
  2. Sign in through the browser login flow (Auth | Cursor - The best way to code with AI).
  3. Continue first-bot setup.
  4. Setup dialog shows ENAMETOOLONG and Try again.

Expected Behavior

Sand-client state is stored under a short name (hash or directory). First bot / agent computer is created.

Operating System

Linux (Ubuntu 24.04)

Linux jamie-ThinkPad-T470s 7.0.0-31-generic #31~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Aug 10 09:38:02 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

ThinkPad T470s. Config dir: /home/jamie/.config/Grok Bot (space in the directory name).

Version Information

ii  grok-bot  0.47.0  amd64
/usr/bin/grok-bot -> /etc/alternatives/grok-bot
real binary: /opt/Grok Bot/grok-bot
package files dated 9 Sep 2026

grok-bot --version does not print a version. It starts Electron and emits:

(node:…) ExperimentalWarning: vm.USE_MAIN_CONTEXT_DEFAULT_LOADER is an experimental feature and might change at any time

Local state after the failed setup (12 Sep 2026, 16:19–16:21 BST)

~/.config/Grok Bot contains Electron state including blob_storage, Cache, Code Cache, Cookies, Crashpad, and box-secrets-push-state.v1.json. The failing path is the oversized sand-client-<token> name shown in the dialog.

Already tried

  • Clicked Try again
  • Inspected ~/.config/Grok Bot and the /opt/Grok Bot install tree

Additional Information

Linux cannot create a filename that long. Please hash the id for the basename, or write the token as file contents under sand-client/<short-id>.

Happy to share more files from that config dir privately if you specify which are safe.

Does this stop you from using Cursor?

No — Cursor works, but with this issue. Grok Bot first-time setup does not complete.

Steps to Reproduce

see post

Screenshots / Screen Recordings

Screenshot at 2026-09-12 16-35-24.png
Screenshot at 2026-09-12 16-35-24.png1920×1080 155 KB

Operating System

Linux

Version Information

0.47.0 amd64

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey @jamie_burt, thanks for the detailed report!

Grok Bot keeps some per-account state in ~/.config/Grok Bot/sand-client-persistence/ under encoded file names that are around 140 to 200 characters long. Linux itself allows 255, but an encrypted home folder (eCryptfs, the “Encrypt my home folder” option from older Ubuntu installers) caps file names at 143 characters, which matches exactly what you are seeing. We are working on shortening those names.

Could you confirm that is what is going on? In a terminal:

  1. Run getconf NAME_MAX ~/.config and note the number.
  2. Run mount | grep -i ecryptfs and note whether anything is printed.

If step 1 prints 255 and step 2 prints nothing, please reply with the output of df -T ~/.config so we can see what filesystem the config folder is on.