Merge branch 'main' into danny/kernel-297-docs-mention-timeouts-for-async-invocation

Author: masnwilliams

browsers/persistence.mdx

@@ -2,17 +2,11 @@
 title: "Persistence"
 ---
 
-Persistence allows you to reuse a browser's state, including cookies, session auth, cache, and any other state that lives on a browser. This can be used to minimize CAPTCHAs and login flows.
-
-Kernel's platform provides multiple ways to persist and reuse state and browser sessions.
-
-## 1. Persisting a browser
-
-With Kernel, you can specify a browser to be persisted and then reuse that exact browser instance again. Using [standby mode](/browsers/standby), we put the browser to sleep in between connections, so you don't pay for idle clock time.
+With Kernel, you can specify a browser to be persisted and then reuse that exact browser instance again over hours or days. Using [standby mode](/browsers/standby), we put the browser to sleep in between connections, so you don't pay for idle clock time.
 
 Since we return the exact same browser instance upon subsequent connections, all browser state is preserved: web page, cookies, session auth, even the exact zoom settings on the page.
 
-Persisted browsers exist indefinitely until you [delete them](/browsers/termination). See [here](/info/pricing) for plan limits on persistence.
+Persistence is especially useful for human-in-the-loop workflows, where automated steps and human actions may be separated by hours or days. The browser can be paused and reconnected without losing state, enabling multi-step processes that combine automation and manual intervention.
 
 To specify a browser for persistence, specify its `persistence` settings in the `browsers.create()` method:
 
@@ -39,8 +33,8 @@ During runtime, Kernel will search for a browser with the specified `id`:
 
 The browser's `persistence id` can be any string. You can set it to an identifier in your system to match it to a user, environment, website, or something else.
 
-## 2. Persisting browser cookies
+Persisted browsers exist indefinitely until you [delete them](/browsers/termination). See [here](/info/pricing) for plan limits on persistence.
 
 <Info>
-  This feature is coming soon
+Use [Profiles](/browsers/profiles) if your goal is to reuse authentication state (cookies, local storage) — especially across concurrent browsers. Persistence is best for human-in-the-loop workflows where the same browser instance needs to be resumed later.
 </Info>

browsers/profiles.mdx

@@ -3,7 +3,7 @@ title: "Profiles"
 description: "Persist and reuse browser session state (cookies, local storage) across sessions"
 ---
 
-Kernel Profiles let you capture browser state created during a session — cookies and local storage — and reuse it in later sessions. This is useful for persisting login state or other site preferences across runs.
+Profiles let you capture browser state created during a session — cookies and local storage — and reuse it in later sessions. This is useful for persisting login state or other site preferences across browser sessions.
 
 ## 1. Create a profile
 
@@ -42,7 +42,7 @@ except ConflictError:
 
 ## 2. Start a browser session using the profile and save changes
 
-After creating the profile, you can reference it by its `name` or `id` when creating a browser.
+After creating the profile, reference it by its `name` or `id` when creating a browser.
 Set `save_changes` to true to persist any state created during this session back into the profile when the browser is closed.
 
 <CodeGroup>
@@ -113,11 +113,11 @@ print("Live view:", kernel_browser2.browser_live_view_url)
 
 </CodeGroup>
 
-### Other ways to use profiles
+## Other ways to use profiles
 
 The API and SDKs support listing, deleting, and downloading profile data as JSON. See the [API reference](/api-reference/profiles/list-profiles) for more details.
 
-### Notes
+## Notes
 
 - A profile's `name` must be unique within your organization.
 - Profiles store cookies and local storage. Start the session with `save_changes: true` to write changes back when the browser is closed.

docs.json

@@ -59,11 +59,11 @@
               "browsers/stealth",
               "browsers/standby",
               "browsers/persistence",
+              "browsers/profiles",
               "browsers/termination",
               "browsers/file-io",
               "browsers/live-view",
-              "browsers/replays",
-              "browsers/profiles"
+              "browsers/replays"
             ]
           },
           {

info/pricing.mdx

@@ -16,6 +16,7 @@ With Kernel, you only pay for what you use and nothing more. Our goal is to be c
 | Browser live view & logs | ✅ | ✅ | ✅ |
 | Browser replays | ❌ | ✅ | ✅ |
 | File uploads & downloads | ❌ | ✅ | ✅ |
+| Browser profiles | ❌ | ✅ | ✅ |
 | Configurable browser extensions | ❌ | Coming soon | Coming soon |
 | BYO images & storage mounts | ❌ | ❌ | Coming soon |
 | SOC2 compliance | ✅ | ✅ | ✅ |

introduction.mdx

@@ -7,14 +7,12 @@ Kernel is a developer platform that provides Crazy Fast Browser Infrastructure f
 
 ## kernel.browsers.create()
 
+If you are already familiar with browser vendors, you can immediately start using our browsers with `kernel.browsers.create()`. We return a CDP url that you can connect any Playwright or Puppeteer automation to.
+
 <Info>
-To use the Kernel SDK, install it first:
-- Typescript/Javascript: `npm install @onkernel/sdk`  
-- Python: `pip install kernel`
+Install the Kernel SDK with `npm install @onkernel/sdk` or `uv pip install kernel`
 </Info>
 
-If you are already familiar with browser vendors, you can immediately start using our browsers with `kernel.browsers.create()`. We return a CDP url that you can connect any Playwright or Puppeteer automation to.
-
 <CodeGroup>
 
 ```typescript Typescript/Javascript

style.css

@@ -1,5 +1,5 @@
 /* style sidebar titles */
 #navigation-items .sidebar-group-header #sidebar-title{
   font-weight: bold;
-  font-size: larger;
+  font-size: 15px;
 }