Grok Bot cloud session — global AIWG install (default path)

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

Date: 2026-09-16 (America/New_York) Host: Grok Bot shared cloud computer AIWG: 2026.9.15 @ `main` (`d92d60c5c`) via `/tmp/aiwg` source install

Default model

Install AIWG into the cloud computer (and policy/repo workspaces) so every Bot picks it up like other harnesses — not via inventing `~/.grokbot` or a Steward Bot for mere loading.

Steward / bootstrap Bot is only for mutating Grok-native objects (routines, CreateAgent, connectors) — see #209.

Durable skill root

export AIWG_GROKBOT_SKILLS_DIR=/home/box/.local/share/aiwg/grokbot-skills

Persisted in:

• `~/.config/environment.d/aiwg-grokbot.conf`
• `~/.bashrc` (default export)

Commands run

Use AIWG to complete this documented outcome: Commands run
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Result

• 26 skills mirrored to `$AIWG_GROKBOT_SKILLS_DIR`
• No `~/.grokbot` / `~/grokbot-skills` invented
• Policy workspace AGENTS.md / WORKSPACE.md regenerated for AIWG binding
• Reload: start a new agent chat or re-read skills (AIWG does not claim live refresh)

Verify

Use AIWG to complete this documented outcome: - 26 skills mirrored to $AIWG_GROKBOT_SKILLS_DIR - No ~/.grokbot / ~/grokbot-skills invented - Policy workspace AGENTS.md / WORKSPACE.md regenerated for AIWG binding - Reload: start a new agent chat or re-read skills (AIWG does not claim li
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.