charlesrhoward · Oct 10, 2026 · Oct 10, 2026 · Oct 10, 2026
@@ -0,0 +1,53 @@
+---
+title: AI Provider Keys
+description: Bring your own Vercel AI Gateway, Anthropic, OpenAI, or OpenRouter key so Mogplex model usage bills to your provider account.
+---
+
+By default, Mogplex bills model usage to your Mogplex plan. Add your own
+provider key to send usage to your own provider account instead, or to use
+models and harnesses that your plan does not include.
+
+## Supported providers
+
+| Provider | Used for | Key format |
+| --- | --- | --- |
+| Vercel AI Gateway | Every model and both CLI harnesses, through one key | AI Gateway API key |
+| Anthropic | Claude models and the [Claude Code](/integrations/claude-code-and-codex) harness | `sk-ant-…` |
+| OpenAI | OpenAI models and the [Codex](/integrations/claude-code-and-codex) harness | `sk-…` |
+| OpenRouter | OpenRouter models | `sk-or-…` |
+
+## Add a key
+
+1. Open **Settings → Provider Keys**.
+2. Paste the key for the provider and select **Save**.
+3. Select **Verify** to confirm that the provider accepts the key.
+
+Personal keys belong to your account. To set keys for a team, open
+**Team Settings → Provider Keys**. Team permissions control who can manage
+them. Keys are stored encrypted and are never shown again after you save them.
+
+## Which key a run uses
+
+For sandbox harness runs (Claude Code and Codex), Mogplex chooses the first
+match:
+
+1. **Your AI Gateway key.** Usage bills to your gateway account.
+2. **Mogplex platform AI**, if your plan includes it. Usage bills to your
+   Mogplex balance.
+3. **Your Anthropic key** (Claude Code) or **OpenAI key** (Codex). Usage bills
+   to that provider.
+
+If none of these is available, the harness is unavailable, and the automation
+harness picker disables it.
+
+Chat and native Mogplex agent runs use the provider of the selected model.
+Models served through OpenRouter need an OpenRouter key.
+
+## Troubleshooting
+
+| Message | Fix |
+| --- | --- |
+| "Hosted AI requires a positive billing balance" | Add funds or choose a plan in **Settings → Billing**, or add your own key. |
+| "No Anthropic API key configured" | Add an Anthropic or AI Gateway key, or choose a different harness. |
+| "No OpenRouter API key configured" | Add an OpenRouter key, or choose a model from another provider. |
+| Verification fails when you save | The key is invalid, revoked, or lacks API access on the provider's side. |
@@ -0,0 +1,42 @@
+---
+title: Browserbase
+description: Connect Browserbase so Mogplex agents can drive cloud browsers to test pages, scrape content, and automate web flows.
+---
+
+Connect Browserbase to give agents a real cloud browser. Agents can load pages,
+click through flows, take screenshots, and extract content.
+
+| | |
+| --- | --- |
+| Type | Remote MCP server, `https://mcp.browserbase.com/mcp` |
+| Credential | Browserbase API key (`bb_live_…`) |
+| Where tools load | Every surface that loads [connection tools](/configure-and-extend/connections-and-mcp#where-connection-tools-load) |
+
+## Connect
+
+1. In Browserbase, copy an API key from the dashboard. See
+   [Browserbase MCP setup](https://docs.browserbase.com/integrations/mcp/setup).
+2. In Mogplex, open **Connections → Integrations**.
+3. Under **Quick Add — MCP Presets**, select **+ Add** on **Browserbase**.
+4. Paste the key, then select **Add**.
+5. Test the saved connection and confirm that it lists tools.
+
+Mogplex sends the key to Browserbase as the `browserbaseApiKey` query parameter.
+The key is stored encrypted and is not shown again.
+
+## Use it
+
+- "Open the preview URL for this PR, sign up with a test account, and report
+  any step that fails."
+- "Capture the pricing page on staging and production and list the
+  differences."
+
+Browser sessions use your Browserbase plan and bill to your Browserbase
+account.
+
+## Troubleshooting
+
+| Symptom | Check |
+| --- | --- |
+| Test fails | The key is invalid or the Browserbase account has no remaining sessions. |
+| The agent cannot reach a preview URL | The preview is protected. Give the agent a URL it can open without signing in, or a bypass token. |
@@ -0,0 +1,59 @@
+---
+title: Claude Code and Codex
+description: Run Anthropic's Claude Code or OpenAI's Codex as the agent harness for Mogplex runs, automations, and Slack tasks.
+---
+
+A harness is the agent program that does the work inside a sandbox. Mogplex
+runs three harnesses:
+
+| Harness | ID | What runs |
+| --- | --- | --- |
+| Mogplex | `mogplex` | Mogplex's native agent. It is always available and uses any model in your catalog. |
+| Claude Code | `claude-code` | Anthropic's `claude` CLI, in the sandbox. |
+| Codex | `codex` | OpenAI's Codex, in the sandbox. It runs through the Agent Client Protocol (ACP). |
+
+Mogplex installs a pinned version of Claude Code or Codex in the sandbox for each
+run, gives it the repository checkout, and streams its events into
+[Observability](/web/observability). Claude Code runs also receive your MCP
+connections; see [where connection tools load](/configure-and-extend/connections-and-mcp#where-connection-tools-load).
+
+## Requirements
+
+Claude Code and Codex need model access. Each harness is available when you have
+one of these:
+
+- **Claude Code:** an AI Gateway key, Mogplex platform AI on your plan, or an
+  Anthropic key.
+- **Codex:** an AI Gateway key, Mogplex platform AI on your plan, or an OpenAI
+  key.
+
+Add keys in **Settings → Provider Keys**. See
+[AI provider keys](/integrations/ai-provider-keys) for the order in which keys
+are used.
+
+## Choose a harness
+
+| Where | How |
+| --- | --- |
+| [Automations](/web/automations) | Select the agent node, then choose **Harness** in the inspector. Unavailable harnesses are disabled. |
+| Slack | `/mogplex harness claude-code`, `/mogplex harness codex`, or `/mogplex harness mogplex`. The choice applies to your future repository runs in that channel. |
+| [Hosted API](/reference/api) and [MCP](/mcp) | Pass `harness` when you start a run. The API defaults to `codex`. |
+
+## Run modes
+
+Claude Code and Codex runs accept a mode that controls what the harness can do
+in the sandbox:
+
+- `SAFE`: the harness does not change the checkout.
+- `AUTO` (default): the harness edits files and runs commands.
+- `YOLO`: the harness runs without approval prompts. Claude Code still blocks
+  its deny-listed tools and commands.
+
+The Mogplex harness takes no mode. See [Start a run](/reference/api#start-a-run)
+for the details.
+
+## Use Mogplex from Claude Code or Codex on your machine
+
+This page covers Claude Code and Codex running **inside** Mogplex. To let a
+local Claude Code, Codex, Cursor, or OpenCode session call Mogplex, install the
+[Mogplex MCP endpoint](/mcp/install).
@@ -0,0 +1,63 @@
+---
+title: Dependabot
+description: Have Mogplex open a reviewed fix PR when GitHub reports a new Dependabot alert, using the Dependabot autopilot workflow template.
+---
+
+When GitHub creates a Dependabot alert, Mogplex can start an agent that prepares
+the smallest safe dependency fix and opens a PR for review. GitHub still detects
+vulnerabilities and decides when an alert is fixed.
+
+## Requirements
+
+- The [GitHub](/integrations/github) integration is connected, and the Mogplex
+  GitHub App is installed on the repository.
+- **Dependabot alerts** are turned on for the repository in GitHub.
+- The GitHub App has the **Dependabot alerts: Read-only** permission and
+  subscribes to the **Dependabot alert** event. The hosted Mogplex App already
+  has both. For a self-hosted App, see
+  [GitHub App setup](/self-hosting/github-app). Each installation must accept
+  new permissions.
+
+## Set it up
+
+1. Open [Automations](/web/automations) and create a workflow from the
+   **Dependabot autopilot** template.
+2. Select the GitHub installation, the repository scope, the agent, and the
+   model.
+3. Publish the workflow.
+4. Optional: after you confirm that it works, turn off **Dependabot security
+   updates** in GitHub, so that Mogplex is the only tool that opens remediation
+   PRs. Keep **Dependabot alerts** on.
+
+## What the agent does
+
+1. Reads the alert from GitHub. If the alert is already closed, the agent stops.
+   If no patched version exists, the agent reports that the alert needs a human
+   decision.
+2. Checks open PRs to avoid duplicate work.
+3. Uses the repository's own package manager to make the smallest manifest and
+   lockfile change.
+4. Runs the available install, lint, typecheck, test, and build checks.
+5. Opens a PR that lists the alert, GHSA and CVE IDs, severity, package, old and
+   new versions, and check results.
+
+The agent never merges the PR and never dismisses the alert. Major upgrades,
+risky indirect dependency changes, and failed checks are reported for a human
+to decide.
+
+## Alert events
+
+The workflow start node can match `created`, `dismissed`, `fixed`, `reopened`,
+`reintroduced`, and `auto_dismissed`. The template selects only `created`.
+
+- An omitted action list also means `created`. An empty list matches nothing.
+- The other actions record the alert's state. They do not start remediation,
+  close PRs, or cancel runs.
+- Each GitHub delivery starts each matching workflow at most once.
+  Redelivering the same event does not create a second run.
+
+## Verify
+
+In the GitHub App's **Advanced → Recent deliveries**, find a
+`dependabot_alert.created` delivery and confirm that it started one run in
+[Observability](/web/observability).
@@ -86,11 +86,18 @@ rules, including entry-agent behavior in automations.
 - **PR review work starts in the wrong shape**: use an Assignment for standing
   repo responsibility, not a one-off Trigger.
 
+## Dependabot alerts
+
+GitHub can also start work when it reports a vulnerable dependency. See
+[Dependabot](/integrations/dependabot) to have Mogplex open a reviewed fix PR
+for each new alert.
+
 ## Read next
 
 <Cards>
   <Card title="GitHub App Coverage" href="/web/guides/github-app-coverage" />
   <Card title="GitHub Mention Routing" href="/web/guides/github-mention-routing" />
   <Card title="Project Workflow" href="/web/guides/project-workflow" />
   <Card title="Choose the Right Routing Surface" href="/web/guides/choose-routing-surface" />
+  <Card title="Dependabot" href="/integrations/dependabot" />
 </Cards>
@@ -1,62 +1,63 @@
 ---
 title: Integrations
-description: Connect Mogplex to GitHub, Vercel, Slack, CI, the hosted API, MCP clients, and local agent hosts.
+description: Every system Mogplex connects to, including GitHub, Slack, Linear, Notion, Sentry, Supabase, Neon, model providers, agent harnesses, webhooks, the API, and MCP clients.
 ---
 
-Integrations connect Mogplex to the systems that own source code, identity,
-runtime credentials, automation, and external tools.
+Integrations connect Mogplex to the systems that own your code, your
+conversations, your tools, and your models. Start with GitHub. Add the others
+when a workflow needs them.
+
+## Source control and chat
+
+<Cards>
+  <Card title="GitHub" href="/integrations/github" description="Repo access, App coverage, PR reviews, @mogplex mentions, triggers, and automations." />
+  <Card title="Dependabot" href="/integrations/dependabot" description="Open a reviewed fix PR when GitHub reports a new Dependabot alert." />
+  <Card title="Slack" href="/integrations/slack" description="DM the bot, @mention it in channels, link channels to repos, and control runs with /mogplex." />
+</Cards>
+
+## Tool connections
+
+Agents call these services as tools during chat, Control, Slack, and sandbox
+runs. Add them from **Connections → Integrations**.
 
 <Cards>
-  <Card
-    title="GitHub"
-    href="/integrations/github"
-    description="Connect identity, confirm App coverage, import repos, and route GitHub comments, PRs, issues, and reviews."
-  />
-  <Card
-    title="Vercel"
-    href="/integrations/vercel"
-    description="Understand repo-linked Vercel project metadata, env sync, and preview troubleshooting."
-  />
-  <Card
-    title="Slack"
-    href="/integrations/slack"
-    description="Install Mogplex in Slack, link channels to repos, control repo-agent runs, and debug DMs, threads, and attachments."
-  />
-  <Card
-    title="CI Integration"
-    href="/cli/automation/ci-integration"
-    description="Run Mogplex from GitHub Actions or another CI system and tail structured run events."
-  />
-  <Card
-    title="Hosted API"
-    href="/reference/api"
-    description="Use the versioned public API for repositories, agents, models, sandboxes, automations, runs, and MCP."
-  />
-  <Card
-    title="GitHub App Coverage"
-    href="/web/guides/github-app-coverage"
-    description="Deep dive on OAuth visibility versus App-backed triggerability."
-  />
-  <Card
-    title="GitHub Mention Routing"
-    href="/web/guides/github-mention-routing"
-    description="Route bare and targeted `@mogplex` mentions through Triggers or Automations without ambiguity."
-  />
-  <Card
-    title="External Connections"
-    href="/configure-and-extend/connections-and-mcp"
-    description="Configure external REST and MCP tools, repo scope resolution, and CLI MCP sync."
-  />
-  <Card
-    title="Mogplex MCP Clients"
-    href="/mcp/install"
-    description="Connect Cursor, Codex, Claude Code, or OpenCode to the live hosted MCP endpoint."
-  />
+  <Card title="Linear" href="/integrations/linear" description="Issues, projects, cycles, and comments." />
+  <Card title="Notion" href="/integrations/notion" description="Search and update pages, databases, and comments." />
+  <Card title="Sentry" href="/integrations/sentry" description="Issues, events, and stack traces." />
+  <Card title="Supabase" href="/integrations/supabase" description="Databases, auth, storage, and edge functions." />
+  <Card title="Neon" href="/integrations/neon" description="Postgres projects, branches, and SQL." />
+  <Card title="Browserbase" href="/integrations/browserbase" description="Cloud browsers for testing and scraping." />
+  <Card title="Sanity" href="/integrations/sanity" description="Structured content, media, and releases." />
+  <Card title="Zapier" href="/integrations/zapier" description="Actions across thousands of apps." />
+  <Card title="Trigger.dev" href="/integrations/trigger-dev" description="Tasks, runs, schedules, and deploys." />
+  <Card title="Custom REST or MCP" href="/configure-and-extend/connections-and-mcp" description="Connect any REST API or MCP server that has no preset." />
+</Cards>
+
+## Models and agents
+
+<Cards>
+  <Card title="AI provider keys" href="/integrations/ai-provider-keys" description="Bring your own Vercel AI Gateway, Anthropic, OpenAI, or OpenRouter key." />
+  <Card title="Claude Code and Codex" href="/integrations/claude-code-and-codex" description="Run Anthropic's or OpenAI's coding agent as the harness for a run." />
+  <Card title="Vercel" href="/integrations/vercel" description="Sandbox compute, repo runtime settings, and env vars." />
+</Cards>
+
+## Start work from anywhere
+
+<Cards>
+  <Card title="Signed webhooks" href="/integrations/webhooks" description="Start an automation from any system that can send an HTTP POST." />
+  <Card title="CI" href="/cli/automation/ci-integration" description="Run Mogplex from GitHub Actions or another CI system." />
+  <Card title="Hosted API" href="/reference/api" description="Repositories, agents, models, sandboxes, automations, and runs over REST." />
+  <Card title="MCP clients" href="/mcp/install" description="Let Claude Code, Codex, Cursor, or OpenCode call Mogplex over MCP." />
 </Cards>
 
 ## Integration order
 
-Start with GitHub identity, GitHub App coverage, and managed account access
-before debugging webhook routing. Add optional Vercel metadata, Slack, MCP
-servers, and CI entry points only after the account can see and cover the repo
-that should run.
+1. Connect GitHub and install the Mogplex GitHub App. Confirm coverage in
+   [Installations](/web/installations) before you debug webhook routing.
+2. Add Slack if your team requests work in chat.
+3. Add tool connections for the services agents must read or change.
+4. Add provider keys only if you want usage billed to your own provider
+   account.
+
+Running Mogplex on your own infrastructure? Each integration needs your own
+app or credentials. See [Self-hosting](/self-hosting).