Workflows, Goals & Loops

When plain chat is not enough: timers (/loop), long goals, and multi-agent workflows.

Comfortable with sessions and permissions

When ordinary chat isn’t enough

Use these tools when work is repetitive, long-running, or needs structured multi-agent stages. Day-to-day shipping still uses normal prompts + verification.

/loop — recurring prompts

/loop 10m Run the project tests if present and report pass or fail only.
/loop 1h Summarize new git commits since yesterday in 5 bullets.
  • Minimum interval typically 60 seconds
  • Jobs expire after a limited lifetime (on the order of days)
  • Don’t spawn dozens of loops—they share your attention and quotas

If /loop does not appear in your slash menu, your version may not enable it yet. Check /docs, or skip this feature for now.

Tasks, queue, and monitors

ToolWhat it’s forHow you touch it
Background shellLong builds/servers while you keep chattingAsk Grok to background; or Ctrl+B on a running command
Tasks paneSee background tasks, subagents, scheduled work/tasks; full TUI also Ctrl+G (minimal mode may use Ctrl+G for external edit—prefer /tasks if unsure)
Prompt queueStack follow-ups while a turn runsType+Enter to queue; send-now chords; list with /queue
monitorStream filtered log lines into the sessionAgent tool; use line-buffered filters

/goal — long objectives with proof

/goal Migrate tests to the new folder layout without breaking npm test
/goal status
/goal pause
/goal resume
/goal clear

Goals are for multi-hour migrations—not typos. Completion should require evidence, not vibes.

Workflows & deep research

/workflow runs saved multi-agent scripts (project .grok/workflows/ or user workflows). /workflows is the run dashboard. /deep-research starts structured research with verification.

Authoring Rhai workflows is advanced. As a learner, run shared workflows when a teammate provides one; learn authoring after you’ve shipped interactively.

Related

For multiple concurrent Grok sessions (not just tools inside one chat), see Agent Dashboard & Multi-Session.

Lab

  1. Start a 60s or 2m loop that only prints the time or checks a local file exists—then cancel/remove it so it doesn’t linger.
  2. Start a long sleep 20 via Grok shell and background it; confirm you can keep typing.
Done when

You know which tool is for timers vs live logs vs multi-hour goals vs multi-agent scripts.