Power user

Little-known features & functions

The moves that separate casual use from SuperGrok Heavy mastery — CLI, web, Imagine, and deploy.

Browser and Bot — what is actually new

Browser Automations — schedule for everyone, email triggers on SuperGrok, @ a connector so every run uses it.
Connector catalog now covers Workspace, Microsoft 365, GitHub, Linear, Notion, Salesforce, Vercel, plus your own MCP server.
Grok Bot — one shared cloud computer, a screen per Bot, skills then routines, Teach a task, voice chat and voice memos, drafts before send.
Team Bots (Teams and Enterprise beta) share context and credentials. Conversations stay per person.
Build stable 1.0.46: memory GA, workflows on by default, /auto vs /always-approve, /deep-research, themes, MCP token files re-read every request. Grok 4.7 Fast is inside Build only.

CLI / PowerShell — underused powers

Feature	Why it is quiet	How to use it
grok inspect	Not in the marketing hero	See which skills, hooks, MCP, and AGENTS.md actually loaded
/skillify	Buried in advanced workflows	Turn a winning session into a reusable skill for the team
/marketplace	Easy to ignore	Install community/official skills & plugins instead of reinventing
Worktree subagents	Sounds abstract	Parallel experiments without dirtying main; merge the winner
Headless -p	Developers stay in TUI	CI autofix, scheduled chores, PR bots
CLAUDE.md compatibility	Migration detail	Drop into a Claude Code repo and keep instruction files
ACP	Platform-y	Build custom orchestrators / internal bots on the agent protocol
Hooks	Config-heavy	Enforce formatters, secret scanning, allowlists on tool use
Shift+Tab modes	Keyboard folklore	Cycle Normal / Plan / Auto-approve without typing
/feedback	Overlooked	Route bugs during beta with session context

PowerShell: inspect + headless combo

grok inspect
grok -p "Only touch tests. Fix failing unit tests. Stop when npm test is green."

Design-related secrets

Custom /design skill in ~/.grok/skills/design beats re-explaining taste every time.
“Do not implement yet” is a first-class move — you want the artifact.
Concentric radii + freeze palette in the skill text prevents 90% of generic UI.
Demand production-build verification, not only dev HMR screenshots.

Web Build Mode — quiet superpowers

Browser QA loop — ask it to screenshot, read the image, and fix overflow/console errors.
Mobile viewport checks — require ~390px validation.
Skill steering — “strict design-ui, no purple, Lucide only” dramatically changes output.
Parallel asset + code — sprites, maps, and systems in one build when you state the full product.
Auth is real in preview — test sign-in paths properly instead of mocking users.
Export then Hostinger — web for speed, your host for ownership (see websites).

Imagine & video — quiet superpowers

One ref per concern beats seven redundant selfies.
End-frame as next ref creates true progressive stories.
Voice pack reuse is as important as face lock for series.
Still → I2V when composition is hard; T2V when exploring.
6s shot discipline — editors will thank you.
1080p finals / 720p drafts — save quota while iterating.

Hostinger Cloud Startup — quiet superpowers

Dedicated IPv4 — point the A record at it; never leave a leftover shared IP from a Business Pro migration
On-demand backups before every deploy (plus daily automatic)
Staging → production push as a habit
LSCache + CDN + ObjectCache triad
10 managed Node web apps when static public_html is not enough
100 PHP workers + PHP version pin for Woo/builders
Traffic power boost the week of a launch
SSH/rsync instead of FTP spaghetti
Cron for sitemap / cache warm
Access sharing for clients — never share admin passwords in chat
Email DNS (SPF against the dedicated IP + DKIM/DMARC) fixed once, forever

Combo moves (where Heavy feels unfair)

/design skill → Web Build landing page → Hostinger Cloud Startup (dedicated IP + CDN) in one afternoon.
Character bible → game sprites → Imagine Video trailer with same face + voice.
CLI worktree subagents: one agent on API, one on UI, one on tests.
/skillify your studio’s brand kit; every future project inherits it.
Headless nightly: dependency bump + test repair PR.

Power move

The ultimate Heavy move is not one feature — it is systems: skills, refs, shot lists, staging, and verification checklists. The model is the engine; your process is the chassis.

Stay sharp

/yolo persists — do not leave it on in production repos.
Never paste production secrets into casual chat logs.
Beta surfaces change; re-run grok inspect after upgrades.

Continue: CLI · /design · Video · Games