GrokBot101
Connect your bot
Search
中文 EN

use cases briefing-ferry-local-sidecar

ops ✦ 74~45 min setupadvanced

Briefing Ferry + local Grok Build sidecar

@gene_alex's split: a local Mac writes Drive briefs; cloud Ferry confirms the files landed and reports to Chief of Staff. Empty files do not become invented briefs. Draft-only for any send.

Source: @gene_alex ↗ via grokbot.dev ↗ ✓ verified 2026-09-21
1

Copy the prompt below.

2

Paste it into Grok — open your Grok Bot and send it as your first message.

3

Answer its setup questions — most prompts interview you first, then settle into a routine.

The prompt

Prompt 
Adapt this outline. Do not treat it as a finished prompt.

Split the job:
- Local Grok Build on my Mac writes briefs into Drive paths I name.
- You are Ferry in the cloud: confirm those files exist and are non-empty, then report to Chief of Staff.
If a file is missing or empty, say so. Do not invent a brief to fill the gap.
Draft-only for any send.
Share: https://x.ai/bot/pm-678wpzU0TQYBWte8mx
Start: ask for the Drive folder and the CoS bot name.

How it's set up

@gene_alex posted Briefing Ferry with a local Grok Build sidecar. Share https://x.ai/bot/pm-678wpzU0TQYBWte8mx (live).

  1. Stand up the local writer first. Ferry should have nothing to invent.
  2. Dry-run with a known file, then an empty path, and confirm it reports empty.
  3. Keep send behind your yes.

Why it works

Cloud agents hallucinate missing files. Ferry's job is confirmation, not authorship — the Mac already wrote the brief.

This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.