Grok Bot / sand host install target (no agent-bundle install grok yet)

[ScriptedAlchemy]

Context

Plugin Library Delivery (Plugin Applier) needs to install plugins into the Grok Bot app, not only Cursor/Claude/Codex.

Current state

• BuiltInHost / default registry: amp | claude | codex | cursor | portable — no grok/sand adapter
• SearchPlugins / InstallPlugin are Cursor marketplace tools → Cursor account only; marketplace publish ≠ Grok Bot in-app install
• Exact command today: none (agent-bundle install grok does not exist)
• Consumers can still use node ./install.mjs / agent-bundle install cursor for Cursor local packs

Ask

Add a Grok Bot / sand host install surface (adapter + install + doctor) so packs can land where Grok Bot agents actually load plugins/skills/MCP — or document that this is out of scope and Grok must stay Cursor-honest.

Acceptance

• Documented install path that makes a pack visible inside the Grok Bot app runtime (not only ~/.cursor/plugins/local)
• Or an explicit “won’t do / blocked on …” decision

Filed from Plugin Applier for Plugin Library Delivery.

[ScriptedAlchemy]

Decision: no agent-bundle install grok host adapter. The documented install path into the Grok Bot runtime is gbot skills add.

Why an adapter has nothing to write to (Grok Bot harness source under grok-bot-harness/src):

• Skills live in one SQLite-backed library per box (GlobalSkillLibrary(<sandRoot>/workflows), runner/conversation-outline.ts:774), behind the gateway at POST /api/<method>. There is no plugin directory on the user's machine that the box reads.
• Plugin skills are a cache of Cursor-marketplace installs: SandPluginSkillsService syncs from the account's installed plugins and pruneUninstalledPluginDirs deletes anything not listed (mcp/host-mcp.ts). A file dropped there is removed on the next sync.
• MCP servers come only from the marketplace (installMcpEntry -> writer.installPlugin({ pluginId }), mcp/host-mcp.ts:771-783); the gateway exposes no route to add a custom server.

So the install surface is network, not filesystem, and it belongs in gbot, which already holds the gateway session. ScriptedAlchemy/grok-bot-cli#91 (merged) ships gbot skills add <SKILL.md|dir>, list, and remove. For a pack, run add once per skill directory; the skills become visible to every bot in the account (per-bot scoping does not exist, see #804). MCP servers in a pack cannot be installed into Grok Bot except through marketplace publication. agent-bundle keeps its host list as is.