docs: mission control updates

[BekahHW]

Description

This pull request updates documentation throughout the project to rename "Continue Hub" to "Continue Mission Control" for consistency and clarity. The changes affect references in guides, configuration instructions, and UI descriptions, as well as internal and external links.

Most important changes:

Global terminology and documentation updates:

• Replaced all references to "Continue Hub" with "Continue Mission Control" in documentation files, including guides, setup instructions, and feature descriptions.

File and section renaming:

• Renamed documentation files and section headers to use "Continue Mission Control" instead of "Continue Hub", such as in agent creation and overview docs. [1] [2]

Link and UI reference updates:

• Updated all internal and external links, as well as UI navigation instructions, to point to "Continue Mission Control" URLs and terminology. This includes API keys, secrets management, and model/rule configuration pages. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

These updates ensure that all documentation is aligned with the new "Continue Mission Control" branding and provide a clearer experience for users navigating the platform.

closes CON-4841

AI Code Review

• Team members only: AI review runs automatically when PR is opened or marked ready for review
• Team members can also trigger a review by commenting @continue-review

Checklist

• I've read the contributing guide
• The relevant docs, if any, have been updated or created
• The relevant tests, if any, have been updated or created

Screen recording or screenshot

[ When applicable, please include a short screen recording or screenshot - this makes it much easier for us as contributors to review and understand your changes. See this PR as a good example. ]

Tests

[ What tests were added or updated to ensure the changes work as expected? ]

---

Summary by cubic

Renamed “Continue Hub” to “Continue Mission Control” across the docs and expanded Mission Control with Tasks, Workflows, Sharing, Metrics, and integrations (GitHub, Sentry, Slack). Implements the branding and navigation updates requested in CON-4841.

• New Features

  • Added Mission Control overview, Tasks, Workflows, Sharing, and Metrics pages.
  • Added integration docs for GitHub, Sentry, and Slack, plus an Integrations index with setup and permissions.
  • Reorganized governance, configs, and secrets under Mission Control.
  • Updated index/home to highlight Mission Control and agent-driven workflows.

• Refactors

  • Replaced all “Continue Hub” references with “Continue Mission Control” in guides, CLI, customization, and IDE docs, and updated terminology (e.g., “Background Agents” → “Cloud Agents”).
  • Standardized paths under /mission-control; updated links for API keys, secrets, models, rules, and prompts.
  • Restructured navigation in docs.json (Hub → Mission Control); removed the old Hub intro and image; renamed “Automations” to “Workflows”.

^{Written for commit e37ac0b. Summary will update automatically on new commits.}

[cubic-dev-ai]

4 issues found across 59 files

Prompt for AI agents (all 4 issues)

Understand the root cause of the following 4 issues and fix them.


<file name="docs/docs.json">

<violation number="1" location="docs/docs.json:450">
`/mission-control/source-control` does not exist, so this new redirect will send `/hub/source-control` visitors to a 404. Please point the redirect at an existing Mission Control page instead.</violation>
</file>

<file name="docs/mission-control/sharing.mdx">

<violation number="1" location="docs/mission-control/sharing.mdx:31">
Fix the grammar so the sentence refers to multiple items (e.g., &quot;Public or Private items&quot;) to keep the documentation clear.</violation>
</file>

<file name="docs/customization/models.mdx">

<violation number="1" location="docs/customization/models.mdx:107">
The gpt-oss-20b setup instructions now point to `ttps://hub.continue.dev/...`, so the hyperlink is broken. Please correct it to `https://` so the documentation link works.</violation>
</file>

<file name="docs/customize/model-providers/top-level/tetrate_agent_router_service.mdx">

<violation number="1" location="docs/customize/model-providers/top-level/tetrate_agent_router_service.mdx:49">
Update the Mission Control secrets link to use the new /mission-control/secrets/secret-types path so readers don’t hit the removed /hub page.</violation>
</file>

_{React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.}

[cubic-dev-ai]

Update the Mission Control secrets link to use the new /mission-control/secrets/secret-types path so readers don’t hit the removed /hub page.

Prompt for AI agents

Address the following comment on docs/customize/model-providers/top-level/tetrate_agent_router_service.mdx at line 49:

<comment>Update the Mission Control secrets link to use the new /mission-control/secrets/secret-types path so readers don’t hit the removed /hub page.</comment>

<file context>
@@ -32,28 +32,28 @@ Go to the [API keys page](https://router.tetrate.ai/api-keys) to get your key
 
 &lt;Step title=&quot;Add your API key&quot;&gt;
-Add your API key to Continue. See [adding secrets in Continue Hub](/hub/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables)
+Add your API key to Continue. See [adding secrets in Continue Mission Control](/hub/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables)
 &lt;Tip&gt;
-Add it as a Continue Hub secret named `TETRATE_API_KEY` to reuse across projects.
</file context>

Suggested change

	Add your API key to Continue. See [adding secrets in Continue Mission Control](/hub/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables)
	Add your API key to Continue. See [adding secrets in Continue Mission Control](/mission-control/secrets/secret-types) and [managing local secrets in the FAQ](/faqs#managing-local-secrets-and-environment-variables)

[cubic-dev-ai]

2 issues found across 17 files (reviewed changes from recent commits).

Prompt for AI agents (all 2 issues)

Understand the root cause of the following 2 issues and fix them.


<file name="docs/guides/snyk-mcp-continue-cookbook.mdx">

<violation number="1" location="docs/guides/snyk-mcp-continue-cookbook.mdx:114">
Please keep the sentence grammatical by retaining the article: &quot;The Mission Control listing automatically configures the MCP command.&quot;</violation>
</file>

<file name="docs/mission-control/configs/intro.mdx">

<violation number="1" location="docs/mission-control/configs/intro.mdx:99">
Please update the sentence to read &quot;the Mission Control interface&quot; and replace the remaining &quot;hub-managed&quot; phrasing so the branding stays consistent.</violation>
</file>

_{React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.}

[cubic-dev-ai]

1 issue found across 7 files (reviewed changes from recent commits).

Prompt for AI agents (all 1 issues)

Understand the root cause of the following 1 issues and fix them.


<file name="docs/mission-control/integrations/slack-agent.mdx">

<violation number="1" location="docs/mission-control/integrations/slack-agent.mdx:32">
The colon is immediately followed by the link text, so this renders as `from:Integrations Settings` and reads awkwardly. Please add a space after the colon so the sentence is legible.</violation>
</file>

_{React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.}

[cubic-dev-ai]

The colon is immediately followed by the link text, so this renders as from:Integrations Settings and reads awkwardly. Please add a space after the colon so the sentence is legible.

Prompt for AI agents

Address the following comment on docs/mission-control/integrations/slack-agent.mdx at line 32:

<comment>The colon is immediately followed by the link text, so this renders as `from:Integrations Settings` and reads awkwardly. Please add a space after the colon so the sentence is legible.</comment>

<file context>
@@ -29,10 +29,7 @@ Mention @Continue in any channel with a task description, and it will:
-
-- [Personal Integrations Settings](https://hub.continue.dev/settings/integrations)
-- Org Integrations Settings - `https://hub.continue.dev/organizations/{your-org}/settings/integrations`
+Continue&#39;s Slack Bot can be installed to a Slack workspace via Mission Control, from:[Integrations Settings](https://hub.continue.dev/integrations)
 
 &lt;Warning&gt;
</file context>

Suggested change

	Continue's Slack Bot can be installed to a Slack workspace via Mission Control, from:[Integrations Settings](https://hub.continue.dev/integrations)
	Continue's Slack Bot can be installed to a Slack workspace via Mission Control, from [Integrations Settings](https://hub.continue.dev/integrations)

[bdougie]

I went through each file and name changes look good. Also I think the files do a great job of introducing concepts for the Mission Control feature. I want to avoid going into specific details since we will be updating this based on user feedback a lot in the coming weeks.