Skip to content

Link GPU availability section to pricing page#331

Merged
ehfeng merged 2 commits intomainfrom
hypeship/add-gpu-pricing-link
Apr 16, 2026
Merged

Link GPU availability section to pricing page#331
ehfeng merged 2 commits intomainfrom
hypeship/add-gpu-pricing-link

Conversation

@ehfeng
Copy link
Copy Markdown
Contributor

@ehfeng ehfeng commented Apr 16, 2026

Summary

Adds a link to the pricing page from the GPU acceleration docs. The Availability section mentions Start-Up and Enterprise plans but didn't link to pricing — now it does.


Note

Low Risk
Documentation-only change that adds links and clarifies pricing/availability; no runtime or API behavior is affected.

Overview
Updates the GPU Acceleration docs to link plan availability to the pricing page and clarifies in the warning callout that GPU-enabled browsers have separate pricing from standard headful/headless browsers.

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

ehfeng and others added 2 commits April 16, 2026 17:43
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@mintlify
Copy link
Copy Markdown
Contributor

mintlify bot commented Apr 16, 2026

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

Project Status Preview Updated (UTC)
Kernel 🟢 Ready View Preview Apr 16, 2026, 5:45 PM

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

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Risk assessment: Very Low.

I reviewed the actual diff and found a single file change in browsers/gpu-acceleration.mdx with two documentation-only edits:

  • Added a pricing link in the warning text
  • Linked plan availability text to the pricing page

Why this is very low risk:

  • No application code, runtime logic, configuration, or infrastructure was changed
  • No auth, billing behavior, data model, API, or shared codepaths were modified
  • Blast radius is limited to documentation content and outbound links
Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@ehfeng ehfeng marked this pull request as ready for review April 16, 2026 21:41
@firetiger-agent
Copy link
Copy Markdown

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

Any PR that changes the kernel API. Monitor changes to API endpoints (packages/api/cmd/api/) and Temporal workflows (packages/api/lib/temporal) in the kernel repo

Reason: PR only updates documentation links in the GPU acceleration docs, with no changes to API endpoints or Temporal workflows.

To monitor this PR anyway, reply with @firetiger monitor this.

@ehfeng ehfeng merged commit 67eb74d into main Apr 16, 2026
4 checks passed
@ehfeng ehfeng deleted the hypeship/add-gpu-pricing-link branch April 16, 2026 21:41
Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Risk assessment: Very Low.

I reviewed the actual diff at the current head and found one documentation file change in browsers/gpu-acceleration.mdx (2 insertions, 2 deletions):

  • Added a pricing link in the warning text
  • Linked plan availability text to the pricing page

Why this remains very low risk:

  • No application/runtime code changed
  • No infrastructure, config, auth, billing logic, or data model changes
  • Blast radius is limited to docs content and outbound links

Approval status check:

  • This PR is already approved at the current head commit, so I did not add a duplicate approval.
Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

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.

1 participant