Ketchup
Catch up on autonomous runs, unattended tasks, and background execution without reading lengthy transcripts.
Strict Concise Summary Format
Executive summaries must remain strictly under 100 words. Deliver the core status in plain declarative sentences. Name the current goal, the completed phase, any active blockers, and the next step. Avoid narrative filler and conversational preamble. Detailed logs belong in companion artifacts rather than the chat summary.
Action Items and Decisions Formatting
Format pending decisions and open questions so the user can easily select options or picks. Present choices as structured options labeled with clear tags:
- Option A. Description of the first choice and its immediate tradeoff.
- Option B. Description of the alternative choice and its immediate tradeoff.
The user can respond with a single token or pick such as Option A. Do not ask open-ended questions when a structured pick settles the fork. When an action is blocked on external input, state the exact input required and the default fallback.
Native Antigravity Artifacts
Deliver comprehensive context through native Antigravity Artifacts in <appDataDir>/brain/<conversation-id>/.
Point to artifacts using clickable file links.
Do not dump artifact bodies into chat responses.
Key companion artifacts include:
walkthrough.mdfor verified changes and test receipts.decision_trail.mdfor sequential forks, rationales, and results.implementation_plan.mdfor roadmap progress and checked boxes.
Visual Media Embedding
Link or embed visual media directly to provide immediate visual receipts.
Always copy screenshots and recordings to <appDataDir>/brain/<conversation-id>/ before referencing them.
Screenshots are linked or embedded using standard Markdown syntax:

Provide direct file links alongside embeds so the user can open them in external viewers. Every visual receipt must prove a concrete assertion such as passing gates or rendered UI states.
Periodic Audit Reporting
Use /ketchup at the conclusion of periodic audit ticks during autonomous playbooks.
An audit tick evaluates progress across subagents, verifies side effects, and outputs a concise ketchup report.
This practice keeps the operator informed without context overload.


