Skip to content

Restructure How it works: Configure, Control, Scale, Observe, Manage - #671

Open
andrewleesteele wants to merge 1 commit into
mainfrom
hypeship/ia-how-it-works
Open

andrewleesteele wants to merge 1 commit into
mainfrom
hypeship/ia-how-it-works

Conversation

@andrewleesteele

@andrewleesteele andrewleesteele commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Summary

First layer of the guides IA restructure (stack: #671 → #672 → #673 → #674). Adds the How it works section — Configure, Control, Scale, Observe, Manage — each with an overview page, and reorganizes the pages under it so readers see the features that matter before the knobs.

Configure

  • New overview covering browser creation, browser types (headful, headless, GPU), viewport, standby, and timeouts. The individual browser setting pages leave the sidebar and are linked from it.
  • Stealth, Proxies, Profiles, Vaults, Authentication, Payments, Config Registry.
  • Authentication nests the managed auth pages in their own group. Managed Auth Credentials is merged into Configuration (redirected), and the managed auth overview gets a connection options table.
  • The hCaptcha beta page folds into Stealth Mode (redirected). Vaults gets a credential-source comparison. Link by Stripe and AgentCard titles fixed.

Control

  • Overview leads with the control surface choice (now including WebMCP and the REPL) and where the loop runs. The "why" sections move into the computer controls and Playwright execution pages.
  • Sidebar: Playwright Execution, Computer Controls, WebMCP, Browser REPL, Process Execution, File I/O, Code Execution Platform. Curl and SSH are linked from the overview; Browser Loop is a new page linked from the overview (and from integrations in Add Start building: quickstart, agent skills, integrations, cookbooks #672).
  • Code execution platform: secrets folds into Deploy and stopping into Invoke (both redirected); pages get task titles.

Scale

  • Overview leads with limits and performance, then the on-demand versus pool decision with on-demand as the default.
  • New Concurrency and Limits page holds every per-plan limit and the API rate limits; links to the old pricing anchors point at it.

Observe — Browser telemetry pages grouped under their own section.

Manage — New overview with a multi-tenant setups section. Network Access is retitled as the firewall allowlist. Projects headings move to sentence case.

Across the section, overview pages get specific titles (for example "Proxies Overview") and headings use sentence case.

Stack notes

Merge the stack in order. Until #673 merges, pages not yet moved stay in their existing sidebar groups, so every layer builds and has no broken links on its own.

Open PRs to reconcile when merging

Testing

  • mint validate and mint broken-links pass on this branch.
  • Rendered locally to check the Configure, Control, Scale, Observe, and Manage overviews.

🤖 Generated with Claude Code


Note

Low Risk
Documentation and navigation-only changes with redirects; no product or API behavior changes.

Overview
Restructures the Guides tab around a new How it works flow — Configure, Control, Scale, Observe, and Manage — each with an overview page and regrouped sidebar pages so readers hit the important concepts before deep dives.

Configure adds introduction/configure and nests stealth, proxies, profiles, vaults, authentication (managed auth subgroup), payments, and config registry. Control rewrites introduction/control around control-surface vs where-the-loop-runs choices, adds Browser Loop, and folds the code-execution platform into this section (develop/deploy/invoke/status/logs). Scale adds browsers/concurrency-and-limits (plan limits + rate limits) and retargets links that used to point at pricing anchors. Observe and Manage get overviews; manage covers projects, keys, audit logs, and the retitled firewall allowlist.

Several standalone pages are merged and redirected in docs.json: app secrets → deploy, stop invocation → invoke, managed auth credentials → connection configuration, hCaptcha → stealth. Cross-links and changelog entries follow the new anchors.

Copy polish: task-oriented titles/descriptions (sidebarTitle), sentence-case headings, vault credential-source table, expanded auth configuration content (formerly the credentials page), and wallet page title fixes.

Reviewed by Cursor Bugbot for commit 4647ff9. Bugbot is set up for automated code reviews on this repo. Configure here.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
Kernel 🟢 Ready View Preview Oct 5, 2026, 7:58 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@andrewleesteele
andrewleesteele added this pull request to stack #675 October 5, 2026 19:58
@andrewleesteele andrewleesteele changed the title hypeship/ia how it works Restructure How it works: Configure, Control, Scale, Observe, Manage Oct 5, 2026
@dprevoznik
dprevoznik marked this pull request as ready for review October 5, 2026 21:15

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4647ff9. Configure here.

</Card>
<Card title="Authentication" icon="key" href="/auth/overview">
Fill logins from a vault, or let managed auth handle the login and keep the session alive.
</Card>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Managed Auth over-claims session recovery

Medium Severity

New overview copy says managed auth will keep the session alive and will reauthenticate when a session expires. Automatic reauth is only an attempt on eligible flows, so this reads as a guarantee the rest of the auth docs already narrow.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 4647ff9. Configure here.

Comment thread apps/develop.mdx
title: "Developing"
title: "Develop an App"
sidebarTitle: "Develop"
description: "Build an app with actions that run next to KERNEL browsers"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
description: "Build an app with actions that run next to KERNEL browsers"
description: "Build an app with actions that run co-located with KERNEL browsers"


| Resource | Headful | Headless |
| --- | --- | --- |
| Default memory | 8 GB | 1 GB |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

consider mentioning support for up to 16 GB in headful.

@dprevoznik dprevoznik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some comments!

</CodeGroup>

- **[Viewport](/browsers/viewport):** defaults to 1920x1080 at 25Hz. A custom viewport restarts Chromium on creation, so use a [browser pool](/browsers/pools) if you need it to be instant.
- **[Standby](/browsers/standby):** after 5 seconds with no CDP, WebDriver, live view, or computer controls activity, a browser goes into standby. It keeps its state and stops accruing usage cost until something reconnects.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'd remove this here. not sure it belongs contextually.


## More browser settings

Most agents never need these, but they're there when you do:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Most agents never need these, but they're there when you do:
Often agents don't require these, but they're there when you do:

Comment thread introduction/control.mdx
| [Playwright execution](/browsers/playwright-execution) | **Default.** You know what to do on the page — navigate, fill, extract, upload. | Needs a selector or DOM path that exists. |
| [Computer controls](/browsers/computer-controls) | **Recommended fallback.** A model is looking at pixels, or the page can't be driven programmatically. | Slower per step, and the model has to see the state to act. |
| [WebMCP](/browsers/webmcp) | The site exposes structured tools for the action you need. | Only works on sites that register tools. |
| [Browser REPL](/browsers/repl) | An agent writes its own helpers and reuses them across turns. | JavaScript only, and state lives until the REPL resets. |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd actually lean on Browser Repl as the default at this time for on-vm control

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"state lives until the REPL resets." i actually think this is a positive too of repl!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On second thought, We can leave playwrighht execution as the default for now, but worth likely overhauling to default to browser repl once the dust settles on the docs

Comment thread introduction/control.mdx

| Surface | Use it when | Trade-off |
| --- | --- | --- |
| [Playwright execution](/browsers/playwright-execution) | **Default.** You know what to do on the page — navigate, fill, extract, upload. | Needs a selector or DOM path that exists. |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

another trade-off here is that each playwright execution api call is stateless (vs. browser repl which is stateful across cells)

Comment thread introduction/control.mdx
**Costs:** a network round trip per action, disconnects to handle, screenshot and DOM bandwidth, and the CDP fingerprint above. It's fine for low-frequency or deterministic work, and it hurts most in a vision loop.
</Tab>
<Tab title="Playwright execution API">
Send code, not commands. Each call runs in the browser's VM against the live session, so state carries across calls and an agent can drive the page turn by turn — one tool call per step, structured data back.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"so state carries across calls" this is true for browser repl but not playwright execution api

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'd reco adding browser repl as a tab here too

Comment thread introduction/control.mdx

If you're building your own agent, [Browser Loop](/browsers/browser-loop) packages these surfaces as tools for each model provider and runs every action against a KERNEL browser, so you don't write the translation layer yourself.

## Going deeper

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'd add browser repl in this list of additional reading options too

Comment thread browsers/browser-loop.mdx
@@ -0,0 +1,87 @@
---
title: "Browser Loop"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider removing from current PR and postpone inclusion till further internal discussion is done.

This branch was successfully deployed

1 active deployment
staging — 4647ff93 Deployed Oct 5, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants