docs: reference dedicated /checks page in Mission Control

[sestinj]

Summary

• Updates 6 docs files to reference the new dedicated /checks page on the hub
• Adds /checks and /checks/new links alongside existing /agents links
• Adds "Mission Control page" row to both "Checks vs. agents" comparison tables
• Adds a "Manage Checks" card to the Mission Control overview page

Context: The hub now has a separate top-level /checks page for PR-triggered review checks, distinct from the /agents page.

Test plan

• Verify all links resolve correctly on the docs site
• Check that the comparison tables render properly with the new row

🤖 Generated with Claude Code

---

Continue Tasks: ✅ 7 no changes — View all

---

Summary by cubic

Update Mission Control docs to point PR-triggered reviews to the new dedicated /checks page, separate from /agents, for clearer navigation. Adds /checks and /checks/new links across six pages, a “Mission Control page” row to both “Checks vs. agents” tables, and a “Manage Checks” card on the Mission Control overview.

^{Written for commit 0f03313. Summary will update on new commits.}

[continue]

Docs Review: No changes needed

I reviewed this PR and found the documentation updates to be well-written and accurate. The changes appropriately reference the new dedicated /checks page in Mission Control across all relevant documentation pages.

What looks good:

• Consistent terminology and formatting throughout
• All relevant pages updated (agents/create-and-edit, agents/intro, agents/overview, mission-control/beyond-checks, mission-control/index, mission-control/workflows)
• Includes a helpful typo fix ('montitor' → 'monitor')
• New table row for 'Mission Control page' is a useful addition to the checks vs. agents comparison

No additional documentation changes are necessary.

[cubic-dev-ai]

1 issue found across 6 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="docs/agents/intro.mdx">

<violation number="1" location="docs/agents/intro.mdx:29">
P2: The new `/checks` link makes this Cloud Agents quick-start internally inconsistent with the next step, which assumes the user is on the Agents page to run an agent.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: The new /checks link makes this Cloud Agents quick-start internally inconsistent with the next step, which assumes the user is on the Agents page to run an agent.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At docs/agents/intro.mdx, line 29:

<comment>The new `/checks` link makes this Cloud Agents quick-start internally inconsistent with the next step, which assumes the user is on the Agents page to run an agent.</comment>

<file context>
@@ -26,7 +26,7 @@ Use Mission Control to kick off Cloud Agents for:
 <Steps>
   <Step title="Navigate to Your Agents Page">
-    Go to [Mission Control Agents page](https://continue.dev/agents) and select an existing workflow with a pre-configured Cloud Agent.
+    Go to the [Agents page](https://continue.dev/agents) or the [Checks page](https://continue.dev/checks) in Mission Control and select an existing workflow.
   </Step>
   
</file context>

Suggested change

	Go to the [Agents page](https://continue.dev/agents) or the [Checks page](https://continue.dev/checks) in Mission Control and select an existing workflow.
	Go to the [Agents page](https://continue.dev/agents) in Mission Control and select an existing workflow with a pre-configured Cloud Agent.