Skip to main content

​
BrowserUse

Shanone’s BrowserUse integration gives your agent 27 tools for cloud browser automation — sessions driven by BrowserUse’s own browsing agent, reusable browser profiles, workspace file storage, and billing visibility.

​
Getting Started

1

Get a BrowserUse Cloud API key

In the BrowserUse Cloud dashboard, generate an API key.
2

Connect in Shanone

Ask your agent to run a browser automation task, or add the API key proactively from Integrations in the Shanone dashboard.
3

Retry your request

Once the key is stored, shanone_execute_tool calls for browseruse_* tools will succeed.

​
Available Tools

Shanone provides 27 tools for BrowserUse, organized into these categories:
browseruse_create_session, browseruse_get_session, browseruse_list_sessions, browseruse_stop_session, browseruse_delete_session, browseruse_list_session_messages, browseruse_wait_for_session
browseruse_create_browser, browseruse_get_browser, browseruse_list_browsers, browseruse_update_browser, browseruse_list_browser_downloads
browseruse_create_profile, browseruse_get_profile, browseruse_list_profiles, browseruse_update_profile, browseruse_delete_profile
browseruse_create_workspace, browseruse_list_workspaces, browseruse_get_workspace, browseruse_update_workspace, browseruse_delete_workspace, browseruse_list_workspace_files, browseruse_delete_workspace_file, browseruse_get_workspace_size, browseruse_upload_workspace_file
browseruse_get_billing_account

​
Common Use Cases

Agentic browsing tasks

Describe a goal in natural language and let a session drive the browser end-to-end

Reusable login profiles

Create a profile with saved cookies/auth state so repeat sessions skip manual login

Batch automation monitoring

Kick off multiple sessions and poll them via browseruse_wait_for_session until each completes

Workspace file handoff

Upload input files to a workspace before a session, then retrieve output files afterward

​
Troubleshooting

Sessions run asynchronously against a real goal description. Use browseruse_wait_for_session with a reasonable timeout, or poll browseruse_get_session and check browseruse_list_session_messages for progress.
Attach an existing profile_id (from browseruse_create_profile) when creating the session — sessions without a profile always start with a clean browser state.
Confirm the workspace ID matches the one the session is configured to use, and check browseruse_get_workspace_size for any storage quota issues.