-
Notifications
You must be signed in to change notification settings - Fork 1
Docs: Scrapybara Migration Update #89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: Scrapybara Migration Update #89
Conversation
Co-authored-by: null <>
|
@tembo please change the intro language to make clear that Scrapybara already shut down their service since it's past Oct 15th |
Updated the intro text to clearly state that Scrapybara has already shut down their service, using past tense to reflect the current status as of October 15, 2025. |
|
@tembo Please make the following changes:
client.browsers.computer.drag_mouse(
|
I've made all the requested changes:
All changes have been implemented as requested. |
|
@tembo please update the drag_mouse example in the Key Concepts section and the Full API section too |
Updated the drag_mouse examples in both the Key Concepts and Full API sections to use the path parameter with coordinate arrays instead of from_x/from_y/to_x/to_y parameters. The examples now show how to properly define a path with multiple coordinates matching Kernel's implementation. |
|
@tembo can you use this as the example for the screenshot in the Kernel example: Take a full screenshotwith open('screenshot.png', 'wb') as f: |
Updated the screenshot example to save the image to a file as requested. The new example shows how to take a full screenshot and write the image data to a PNG file. |
Mesa DescriptionDescriptionThis PR enhances the Scrapybara migration guide by:
Implementation Checklist
Testing
Docs
Visual ProofPlease provide a screenshot or video demonstrating that your changes work locally: [Drag and drop your screenshot/video here or use the following format:] Related IssueFixes [Github issue link] [If this corresponds to a fix from another Kernel OSS repo, include this:] Fixes [Link to other repo] [Replace with actual issue link, e.g., Fixes https://github.com/username/repo/issues/123] Additional Notes[Any additional context, concerns, or notes for reviewers]
Description generated by Mesa. Update settings |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Performed full review of 4b99cea...344e788
Analysis
- No architectural issues identified with the documentation update PR. The changes are primarily content updates rather than architectural modifications.
- Documentation updates appropriately reflect the current state of the service and provide comprehensive migration guidance.
Tip
⚡ Quick Actions
This review was generated by Mesa.
Actions:
Slash Commands:
/review- Request a full code review/review latest- Review only changes since the last review/describe- Generate PR description. This will update the PR body or issue comment depending on your configuration/help- Get help with Mesa commands and configuration options
1 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings
Mesa DescriptionDescriptionThis PR updates the Scrapybara migration guide to better assist users transitioning to Kernel. It adds a shutdown notice for the Scrapybara service, effective October 15, 2025. The guide is significantly expanded to detail Kernel's Computer Controls, with updated API comparison tables and a new section featuring side-by-side code examples for mouse actions, keyboard inputs, and screenshots. Implementation Checklist
Testing
Docs
Visual ProofPlease provide a screenshot or video demonstrating that your changes work locally: [Drag and drop your screenshot/video here or use the following format:] Related IssueFixes [Github issue link] [If this corresponds to a fix from another Kernel OSS repo, include this:] Fixes [Link to other repo] [Replace with actual issue link, e.g., Fixes https://github.com/username/repo/issues/123] Additional Notes[Any additional context, concerns, or notes for reviewers] Description generated by Mesa. Update settings |
Mesa DescriptionDescriptionThis PR significantly updates the Scrapybara migration guide to better assist users transitioning to Kernel, particularly with the addition of Computer Controls. Key changes include:
Implementation Checklist
Testing
Docs
Visual ProofPlease provide a screenshot or video demonstrating that your changes work locally: [Drag and drop your screenshot/video here or use the following format:] Related IssueFixes [Github issue link] [If this corresponds to a fix from another Kernel OSS repo, include this:] Fixes [Link to other repo] [Replace with actual issue link, e.g., Fixes https://github.com/username/repo/issues/123] Additional Notes[Any additional context, concerns, or notes for reviewers] Description generated by Mesa. Update settings |
|
@tembo Ok the Kernel doc part is close to set. On to the Scrapybara APIs review. A few other changes:
The hallucinations only apply to the computer api changes introduced. For example: |
I've updated all the Scrapybara API examples to match the patterns from the official docs. For the Computer API section, I replaced the hallucinated methods with the correct syntax using |
Mesa DescriptionDescriptionThis PR significantly updates the Scrapybara migration guide to better assist users transitioning to Kernel, particularly with the addition of Computer Controls. Key changes include:
Implementation Checklist
Testing
Docs
Visual ProofPlease provide a screenshot or video demonstrating that your changes work locally: [Drag and drop your screenshot/video here or use the following format:] Related IssueFixes [Github issue link] [If this corresponds to a fix from another Kernel OSS repo, include this:] Fixes [Link to other repo] [Replace with actual issue link, e.g., Fixes https://github.com/username/repo/issues/123] Additional Notes[Any additional context, concerns, or notes for reviewers] Description generated by Mesa. Update settings |
1 similar comment
Mesa DescriptionDescriptionThis PR significantly updates the Scrapybara migration guide to better assist users transitioning to Kernel, particularly with the addition of Computer Controls. Key changes include:
Implementation Checklist
Testing
Docs
Visual ProofPlease provide a screenshot or video demonstrating that your changes work locally: [Drag and drop your screenshot/video here or use the following format:] Related IssueFixes [Github issue link] [If this corresponds to a fix from another Kernel OSS repo, include this:] Fixes [Link to other repo] [Replace with actual issue link, e.g., Fixes https://github.com/username/repo/issues/123] Additional Notes[Any additional context, concerns, or notes for reviewers] Description generated by Mesa. Update settings |
|
@tembo for the scrapybara code snippet example, please use the below for click_mouse with specific coordinates: instance.computer(action="click_mouse", button="right", coordinates=[300, 400]) |
Updated the code example to use right-click with specific coordinates [300, 400] as requested. Thanks for catching this! |
|
@tembo Can you also make this final change? Use this for scroll in full API reference of Scrapybara: |
Updated the scroll example in the API comparison table to use the exact syntax you requested, showing the proper usage with coordinates parameter. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thx Tembo 😄
Description
Updates the Scrapybara migration guide to include Kernel's Computer Controls. Added a new section with code examples and expanded API comparison tables.
Implementation Checklist
Testing
mintlify devworks (see installation here)Docs
Visual Proof
Please provide a screenshot or video demonstrating that your changes work locally:
[Drag and drop your screenshot/video here or use the following format:]
]
[
Related Issue
Fixes [Github issue link]
[If this corresponds to a fix from another Kernel OSS repo, include this:]
Fixes [Link to other repo]
[Replace with actual issue link, e.g., Fixes https://github.com/username/repo/issues/123]
Additional Notes
[Any additional context, concerns, or notes for reviewers]