Draft
Conversation
Updated 'Get a key' and 'Get started' links in introduction.mdx, llm-quickstart.mdx, and pricing.mdx to link directly to https://cloud.browser-use.com/new-api-key instead of the generic cloud homepage. Co-authored-by: Gregor Žunič <gregpr07@users.noreply.github.com>
|
Cursor Agent can help with this pull request. Just |
MagMueller
added a commit
that referenced
this pull request
Mar 31, 2026
When using client.run() with a sessionId for follow-up tasks, the async iterator started with cursor=undefined, replaying all messages from previous tasks in the session. This was the #1 pain point for chat/follow-up use cases. Fix: Before creating the follow-up task, snapshot the latest message cursor from the session. Pass it as the starting cursor for the iterator so only new messages from the current task are yielded. Both TS and Python SDKs are fixed (sync and async clients). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
MagMueller
added a commit
that referenced
this pull request
Mar 31, 2026
* Fix browsers.create() no-arg 422 and error message serialization
- browsers.create(): Default body to {} so no-arg calls work as
documented. Previously sent undefined body → API returned 422.
- Error serialization: Use JSON.stringify (TS) / json.dumps (Python)
for non-string error details instead of String() / str() which
produced "[object Object]" for validation error arrays.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* Fix workspace upload prefix option and files.items → files.files in docs
- TS upload(): Accept { prefix } options object alongside file paths.
Previously rest params treated the options object as a file path,
causing TypeError.
- Docs: Fix files listing examples from .items to .files to match
the actual FileListResponse schema (workspaces.list() uses .items
but workspaces.files() uses .files).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* Fix client.run() replaying all messages on follow-up tasks
When using client.run() with a sessionId for follow-up tasks, the
async iterator started with cursor=undefined, replaying all messages
from previous tasks in the session. This was the #1 pain point for
chat/follow-up use cases.
Fix: Before creating the follow-up task, snapshot the latest message
cursor from the session. Pass it as the starting cursor for the
iterator so only new messages from the current task are yielded.
Both TS and Python SDKs are fixed (sync and async clients).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* Clean up Python async follow-up cursor: use nonlocal + callback instead of run_holder hack
Replace the mutable run_holder list pattern with a cleaner approach:
- Use nonlocal to capture start_cursor in create_fn closure
- Pass a lambda ref to AsyncSessionRun so it reads the cursor after
create_fn sets it (the cursor is set inside create_fn before
sessions.create, and read in __aiter__ after create_fn returns)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update API key links in
ferndocs to point directly to/new-api-keyfor consistency with the mainbrowser-userepo.Slack Thread
Summary by cubic
Updated "Get a key" and "Get started" links in Fern docs to point directly to https://cloud.browser-use.com/new-api-key. This aligns with the main browser-use repo and reduces clicks when creating an API key.
Written for commit ceb69f1. Summary will update on new commits.