Skip to content

docs: Update cookbook guides to use agents #8486

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 4, 2025
+73 −165
Merged

docs: Update cookbook guides to use agents #8486

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b9c0ee0
Update cookbook guides to use agents
BekahHW Oct 28, 2025
336e82d
Consolidate info callouts for headless mode
BekahHW Oct 28, 2025
b27bcc5
Update docs/guides/dlt-mcp-continue-cookbook.mdx
BekahHW Oct 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/guides/chrome-devtools-mcp-performance.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,10 +65,10 @@ After completing **Quick Setup** above, you have two paths to get started:

<Steps>
<Step title="Add the Pre-Built Agent">
Visit the [Chrome DevTools Continuous Agent](https://hub.continue.dev/continuedev/chrome-dev-continuous) on Continue Hub and click **"Install Agent"** or run:
Visit the [Chrome Dev Tools Agent](https://hub.continue.dev/continuedev/chrome-dev-tools-agent) on Continue Hub and click **"Install Agent"** or run:

```bash
cn --config continuedev/chrome-dev-continuous
cn --agent continuedev/chrome-dev-tools-agent
```

This agent includes:
Expand Down Expand Up @@ -438,7 +438,7 @@ jobs:
env:
CONTINUE_API_KEY: ${{ secrets.CONTINUE_API_KEY }}
run: |
cn --config continuedev/chrome-dev-continuous \
cn --agent continuedev/chrome-dev-tools-agent \
-p "Navigate to http://localhost:3000 and:
1. Record performance trace with reload
2. Extract LCP, FID, CLS values
Expand Down
60 changes: 16 additions & 44 deletions docs/guides/dlt-mcp-continue-cookbook.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ For all options, first:
## dlt MCP Workflow Options

<Card title="🚀 Fastest Path to Success" icon="zap">
Skip the manual setup and use our pre-built [dlt Assistant agent](https://hub.continue.dev/dlthub/dlt-assistant) that includes
Skip the manual setup and use our pre-built [dlt Agent](https://hub.continue.dev/continuedev/dlt-agent) that includes
the dlt MCP and optimized data pipeline workflows for more consistent results. You can [remix this agent](/guides/understanding-configs#how-to-get-started-with-hub-configs) to customize it for your specific needs.
</Card>

Expand All @@ -53,7 +53,7 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s
<Step title="Load the Pre-Built Agent">
Navigate to your pipeline project directory and run:
```bash
cn --config dlthub/dlt-assistant
cn --agent continuedev/dlt-agent
```

This agent includes:
Expand All @@ -73,7 +73,7 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s
</Steps>

<Info>
**Why Use the Agent?** The pre-built [dlt Assistant agent](https://hub.continue.dev/dlthub/dlt-assistant) provides consistent pipeline development workflows and handles MCP configuration automatically, making it easier to get started with AI-powered data engineering. You can [remix and customize this agent](/guides/understanding-configs#how-to-get-started-with-hub-configs) later to fit your team's specific workflow.
**Why Use the Agent?** The pre-built [dlt Agent](https://hub.continue.dev/continuedev/dlt-agent) provides consistent pipeline development workflows and handles MCP configuration automatically, making it easier to get started with AI-powered data engineering. You can [remix and customize this agent](/guides/understanding-configs#how-to-get-started-with-hub-configs) later to fit your team's specific workflow.
</Info>

</Tab>
Expand Down Expand Up @@ -117,7 +117,7 @@ After ensuring you meet the **Prerequisites** above, you have two paths to get s
</Tabs>

<Accordion title="Agent Requirements">
To use the pre-built [dlt Assistant agent](https://hub.continue.dev/dlthub/dlt-assistant), you need either:
To use the pre-built [dlt Agent](https://hub.continue.dev/continuedev/dlt-agent), you need either:
- **Continue CLI Pro Plan** with the models add-on, OR
- **Your own API keys** added to Continue Hub secrets (same as manual setup)

Expand Down Expand Up @@ -165,6 +165,8 @@ You can add prompts to your agent's configuration for easy access in future sess
changes, test your prompts in plan mode (see the [Plan Mode
Guide](/guides/plan-mode-guide); press **Shift+Tab** to switch modes in TUI/IDE). This
shows you what the agent will do without executing it.

To run any of the example prompts below in headless mode, use `cn -p "prompt"`
</Info>

<Info>
Expand All @@ -178,107 +180,77 @@ You can add prompts to your agent's configuration for easy access in future sess
<Card title="Inspect Pipeline Execution" icon="magnifying-glass">
Review pipeline execution details including load timing and file sizes.

**TUI Mode Prompt:**
**Prompt:**
```
Inspect my dlt pipeline execution and provide a summary of the load info.
Show me the timing breakdown and file sizes for each table.
```

**Headless Mode Prompt:**
```bash
cn -p "Inspect my dlt pipeline execution and provide a summary of the load info. Show me the timing breakdown and file sizes for each table." --auto
```

</Card>

### Schema Management

<Card title="Retrieve Schema Metadata" icon="diagram-project">
Get detailed schema information for your pipeline's tables.

**TUI Mode Prompt:**
**Prompt:**
```
Show me the schema for my users table including all columns,
data types, and any constraints.
```

**Headless Mode Prompt:**
```bash
cn -p "Show me the schema for my users table including all columns, data types, and any constraints." --auto
```

</Card>

### Data Exploration

<Card title="Query Dataset Records" icon="table">
Retrieve and analyze records from your destination database.

**TUI Mode Prompt:**
**Prompt:**
```
Get the last 10 records from my orders table and show me
the distribution of order statuses.
```

**Headless Mode Prompt:**
```bash
cn -p "Get the last 10 records from my orders table and show me the distribution of order statuses." --auto
```

</Card>

### Error Debugging

<Card title="Analyze Load Errors" icon="triangle-exclamation">
Investigate and understand pipeline load errors.

**TUI Mode Prompt:**
**Prompt:**
```
Check for any load errors in my last pipeline run. If there are errors,
explain what went wrong and suggest fixes.
```

**Headless Mode Prompt:**
```bash
cn -p "Check for any load errors in my last pipeline run. If there are errors, explain what went wrong and suggest fixes." --auto
```

</Card>

### Pipeline Creation

<Card title="Build New Pipeline" icon="plus">
Create a new dlt pipeline from an API or data source.

**TUI Mode Prompt:**
**Prompt:**
```
Help me create a new dlt pipeline that loads data from the
JSONPlaceholder API users endpoint into DuckDB.
```

**Headless Mode Prompt:**
```bash
cn -p "Help me create a new dlt pipeline that loads data from the JSONPlaceholder API users endpoint into DuckDB." --auto
```

</Card>

### Schema Evolution

<Card title="Handle Schema Changes" icon="code-branch">
Review and manage schema evolution in your pipelines.

**TUI Mode Prompt:**
**Prompt:**
```
Check if my pipeline schema has evolved since the last run.
Show me what columns were added or modified.
```

**Headless Mode Prompt:**
```bash
cn -p "Check if my pipeline schema has evolved since the last run. Show me what columns were added or modified." --auto
```

</Card>

## Continuous Data Pipelines with GitHub Actions
Expand All @@ -293,7 +265,7 @@ Navigate to **Repository Settings → Secrets and variables → Actions** and ad
- Any required database credentials for your destination

<Info>
The workflow uses the pre-built [dlt Assistant agent](https://hub.continue.dev/dlthub/dlt-assistant) with `--agent dlthub/dlt-assistant`. This agent comes pre-configured with the dlt MCP and optimized rules for pipeline operations. You can [remix this agent](/guides/understanding-configs#how-to-get-started-with-hub-configs) to customize the validation rules and prompts for your specific pipeline requirements.
The workflow uses the pre-built [dlt Agent](https://hub.continue.dev/continuedev/dlt-agent) with `--agent continuedev/dlt-agent`. This agent comes pre-configured with the dlt MCP and optimized rules for pipeline operations. You can [remix this agent](/guides/understanding-configs#how-to-get-started-with-hub-configs) to customize the validation rules and prompts for your specific pipeline requirements.
</Info>

### Create Workflow File
Expand Down Expand Up @@ -342,15 +314,15 @@ jobs:
- name: Validate Pipeline Schema
run: |
echo "🔍 Validating pipeline schema..."
cn --config dlthub/dlt-assistant \
cn --agent continuedev/dlt-agent \
-p "Inspect the pipeline schema and verify all required tables
and columns are present. Flag any missing or unexpected changes." \
--auto

- name: Check Pipeline Health
run: |
echo "📊 Checking pipeline health..."
cn --config dlthub/dlt-assistant \
cn --agent continuedev/dlt-agent \
-p "Analyze the last pipeline run for errors or warnings.
Report any issues that need attention." \
--auto
Expand All @@ -360,7 +332,7 @@ jobs:
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
REPORT=$(cn --config dlthub/dlt-assistant \
REPORT=$(cn --agent continuedev/dlt-agent \
-p "Generate a concise summary (200 words or less) of:
- Pipeline schemas and row counts
- Any load errors or warnings
Expand Down
Loading
Loading