grok-build-upstream-mirror/crates/codegen/xai-grok-pager/docs/tutorial/08-make-it-yours.md
grokkybara[bot] 69f0ba880a Synced from monorepo
Synced from monorepo

Changes:
- Workspace server: report `/ready` as failed with dwell on hub connect failure
- Refresh OIDC token for the Grok agent in the shell
- ACP terminal output recorder
- Cross-platform provider auth commands in the shell
- Default `/resume` to Grok sessions with a hint for hidden external sessions
- Resume sessions by title with `--resume`
- Limit app-builder archive size
- Data-driven tag labels for slash commands
- Doctor fixes for tmux
- Custom provider gateways and subprocess environment policy in the shell
- `/tutorial` — opt-in onboarding tour of Grok Build
- Soft and required CLI version checks in the shell
- Privacy banner env overrides survive live settings updates
- Add remote flag to override the image-edit model
- Return profile fields from auth info even when the access token is expired
- Add edit control on queued prompt rows
- Keep fail-closed policy when clearing orphans with no team
- Setting to disable the Ctrl+Space/F8 voice shortcut
- Pass `--raw` to pw-record so Linux dictation works on older PipeWire
- Validate git URLs when adding marketplace entries
- Stop shipping stale tool-doc parameter and tool names
- Re-point dashboard attach after `/fork` only when the parent was attached
- Surface Grok Computer media-generation results as file-path chunks
- Clear web background-task tray on kill and keep the task description
- Show privacy upsell banner in agent view until acted on
- Add tools-server client callback surface
- Protect persistent global hook sources

Source-Revision: 95d84f443eddcbed6cbfd6eed22e2eafe6b3939d
2026-07-23 17:12:33 +00:00

1.3 KiB

Make It Yours

The easiest way: just ask

Grok knows its own capabilities and can configure itself. Try:

  • "add the Postgres MCP server for our staging db"
  • "switch to a light theme"
  • "write an AGENTS.md for this repo"

If you'd rather drive, everything below has a command too.

Teach Grok your project: AGENTS.md

Drop an AGENTS.md file in your repo root with build commands, conventions, and gotchas. Grok reads it automatically in every session — it's the single highest-leverage customization:

# My Project
- Run tests with `pnpm test`
- Never edit files under generated/

Teach Grok your facts: memory

Start a prompt with # (or use /remember) to save a note for future sessions: # the staging deploy uses eu-west.

Looks, keys, and extensions

  • /theme — color themes (or auto to follow your OS); /settings (or F2) for everything else; /vim-mode if that's your thing.
  • Skills (/skills) — reusable prompt packages; user-invocable skills become slash commands automatically.
  • MCP servers (/mcps) and plugins & hooks (/plugins, /hooks).

Start with AGENTS.md and a theme; add the rest when you need it.

Go deeper: /docs Project Rules (AGENTS.md), /docs Skills, or /docs MCP Servers