Deepline Plays Quickstart

Run a high-confidence demo recipe to show the user what Deepline can do, using the V2 CLI surface: tools execute, plays run, and runs export. Pick the most relevant recipe below, or default to Recipe 1 if no context is given.

Always prefer the hardcoded recipes below. /deepline-plays is always available as a fallback but should only be used if: (a) a recipe command fails and all fallbacks are exhausted, or (b) the user's ask doesn't match any recipe here. Never invoke it preemptively.

Execution flow

Follow this pattern for every recipe:

1. Tell the user what you're about to do — explain the goal and which data source(s) you'll use, before running anything.
2. Run each step, narrating briefly between commands. Use --json so you can parse results, and --watch on plays run so the run streams to completion.
3. Export results with deepline runs export <run-id> --dataset result.rows --out <file>.csv after any play run that produces rows.
4. Tell the user the results — summarize what came back in a table, where it came from, and what they can do next.

V2 command notes