Proposal: import a team from Grok Bot on first run

[inchTodd]

Summary. DS Bot's desktop app already imports a team from DSH on first run. Add a second source: the Bot roster that Grok Bot keeps on this computer, so a user can bring their Bots over in one step instead of retyping charters.

What is actually on disk. I checked the macOS app (read-only). The sidebar roster lives in

~/Library/Application Support/Grok Bot/sand-client-persistence/*.blob

as JSON. One blob holds value.rows, one row per Bot, with fields such as id, name, description, title, avatarShape, avatarColor, avatarPhoto, and timestamps. The rest of Grok Bot is not there: the longer system prompt, memory, automations, plugins/connectors and conversations live in its cloud store. Some recent chat entries are cached locally, but in an internal, partial format.

What could be imported (v1).

• name, role/title, description as instructions, avatar shape and color mapped to the closest DS Bot character and palette, optional photo if stored locally;
• creation order, so the roster looks familiar;
• a checklist of what still needs reconnecting (plugins/apps), not an automatic migration.

What cannot be imported, and why.

• memory, cloud files and conversations: not on disk in a usable form;
• automations: cloud-only; they would be rebuilt as DS Bot scheduled tasks by hand;
• connectors/plugins: need a new sign-in; the importer can only list names;
• work folders: Grok paths (/home/box, /workspace) don't exist here, so the user picks folders after import.

Flow.

1. Detect the Grok Bot store (macOS path above; Windows path best-effort).
2. Show a preview: which Bots, duplicate names flagged, which fields are missing.
3. Create the selected Bots through the normal create-Bot path — same name handling, same folder and permission rules, no bypass.
4. Report: imported, skipped, and why; list what the user still has to reconnect.

Safety and compliance.

• read-only; never read sand-secrets.json or any credential file; no network;
• the format is undocumented and may change: fail gracefully, import nothing on a parse error;
• only the user's own local data; no Grok branding, no copied UI text;
• original code, Apache-2.0; no DSH changes.

Non-goals (v1). Chat history, memory, automations, connectors, cloud data, Windows path unless someone can verify it, any automatic install or sign-in.

Open questions.

1. Does this belong in first run, in Settings → Import, or both?
2. The store is undocumented. Ship it as “best effort, may change”, or wait for an official export?
3. Avatars: skip photos in v1 and keep shape/color only?
4. Should description be imported verbatim (it is the user's own text) or adapted to DS Bot's instruction style?

Prior art. A one-off script produced a migration list outside the repo, but there is no code or proposal in the project. I found no open issue or discussion on this.

Ask. Does this fit the project, and which area should own it (app/ first-run, or a new import entry)? If yes, I'll open an issue with the agreed scope.