Repository navigation
Document 3GiB and 6GiB video memory for GPU browsers - #679
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
f59cce7 to
9843b1b
Compare
9843b1b to
2aec501
Compare
2aec501 to
8d65f3c
Compare
8d65f3c to
068448b
Compare
068448b to
4ea2fc5
Compare
4ea2fc5 to
96ca095
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit bed735f. Configure here.
| ### Read whole-session memory | ||
|
|
||
| `free` reports the memory allocated to your browser. non-gpu headless browsers use `1GiB` by default and support `2GiB` or `4GiB`; non-gpu headful browsers use `8GiB` by default and support `16GiB`. set `memory` when you [create a browser](https://www.kernel.sh/docs/api-reference/browsers/create-a-browser-session) to select the larger allocation. | ||
| `free` reports the memory allocated to your browser. Non-GPU headless browsers use `1GiB` by default and support `2GiB` or `4GiB`; non-GPU headful browsers use `8GiB` by default and support `16GiB`. Set `memory` when you [create a browser](/api-reference/browsers/create-a-browser-session) to select the larger allocation. GPU browsers use `6GiB` by default, or `12GiB` when you [request 6 GiB of video memory](/browsers/gpu-acceleration#request-more-video-memory). |
There was a problem hiding this comment.
Relative API reference link
Medium Severity
The create-a-browser link was changed from an absolute https://www.kernel.sh/docs/api-reference/... URL to a relative /api-reference/ path. API reference pages are generated from the remote OpenAPI spec and are not local MDX files, so relative /api-reference/ links fail mint broken-links.
Reviewed by Cursor Bugbot for commit bed735f. Configure here.


Summary
Documents
video_memoryfor GPU browsers using the values the API now takes:3GiB(standard, the default) and6GiB(large, 8 vCPUs and 12 GiB of memory). The SDKs support both from 0.141.0.2GiBand4GiBare still accepted as deprecated aliases, and responses report3GiB/6GiB.browsers/gpu-acceleration.mdx: new "Request more video memory" section with TypeScript, Python, Go, and CLI examples. Covers the allowed values, the deprecated aliases, the requirement thatgpuistrue, thatmemorycan't be set on GPU browsers, the response fields, billing (2x the standard GPU rate), and the 529no_gpu_browsers_availableresponse when the large tier is at capacity without falling back to3GiB.browsers/process-execution.mdx: the whole-session memory paragraph covers GPU allocations (6 GiB, or 12 GiB with 6 GiB of video memory) and fixes sentence-case consistency and relative link path.Before merging
kernel/clirelease (includingkernel/cli#311) so--video-memory 6GiBworks in the latest released CLI, and add its minimum version next to the SDK version.mint broken-linkspasses.Note
Low Risk
Docs-only change describing existing API behavior; no runtime or security impact.
Overview
Adds a “Request more video memory” section to
gpu-accelerationdocs covering the3GiBdefault vs6GiBlarge tier (vCPU/RAM), TS/Python/Go/CLI examples,video_memoryrules (requiresgpu: true, ties systemmemory, SDK 0.141.0+), deprecated2GiB/4GiBaliases, 2× billing for the large tier, and HTTP 529 /no_gpu_browsers_availablewhen large-tier capacity is exhausted (no fallback).Updates the whole-session memory guidance in
process-executionto note GPU defaults (6GiB/12GiBwith large video memory), fixes sentence case, switches the create-browser link to a relative path, and cross-links to the new video-memory section.Reviewed by Cursor Bugbot for commit bed735f. Bugbot is set up for automated code reviews on this repo. Configure here.