Run /deep-research and /imagine inside Grok Build
Run /deep-research and /imagine inside Grok Build
Grok Build’s TUI ships slash commands for research and media inside the coding session. Official Modes and Commands lists /deep-research, /imagine, and /imagine-video among the core commands (some appear only when the feature is available on your build).
Research from the TUI
- Start a Build session in your repo (
grokafter install — see Start a Grok Build session in your repo). - Run:
/deep-research <what you need researched>
/deep-researchstarts a built-in research workflow in the background. Watch progress with/workflows(live run dashboard) or/tasks.- When the workflow returns, use the result in the same session (summarize findings, open files, draft changes).
Disable workflows entirely with [workflows] enabled = false in ~/.grok/config.toml, or GROK_WORKFLOWS=0, if you need Build without background workflows.
Consumer DeepSearch on grok.com is a different surface — see Run DeepSearch when you need a researched answer with sources. This page is the Build CLI command.
Images and video from the TUI
/imagine <text description>
/imagine-video <text description>
/imagine generates an image from text. /imagine-video generates a video from text. Both are session commands in the Modes and Commands table; they show up when those features are enabled for your CLI build.
For API-level Imagine (files, reference-to-video, extend), use the Imagine API how-tos under API / Imagine. Build’s slash commands are the in-session shortcuts, not the full HTTP schema.
Related Build commands
| Command | Use |
|---|---|
/context |
View current context usage |
/compact [context] |
Compact conversation history |
/usage |
View credit usage or manage billing |
/create-workflow / /workflow |
Author or run saved workflows |
Shift+Tab cycles Plan / Auto / Always-approve modes. Plan mode is covered in Use Plan mode in Grok Build.
Pitfalls
/deep-researchspends from your paid usage like other Build work — watch/usageand the web Usage tab.- A few commands (including
/imagineand/loop) appear only when the feature is available on that CLI version. - Workflows write under
.grok/workflows/in the project or~/.grok/workflows/for every project; treat those files as project config when you commit.