Skip to main content
Browser Use is available on enabled Famulor workspace plans, including a whitelabel reseller’s own workspace. It is not yet available in reseller customer workspaces. Workspace processing must be set to Global.
  1. Open Agent Tools → Agent Connectors and select Add on the Browser Use card. Alternatively, create a Built-in tool and choose Browser Use.
  2. Enter an HTTPS Start URL and the exact Allowed websites, including required redirects and page resources.
  3. Use Description (when to use) to tell the assistant when to choose this tool.
  4. Add Browser instructions for the website workflow, expected result and stopping conditions. These instructions are sent directly to every browser task.
  5. Add Required information with a unique label and optional question guidance for each answer the assistant must collect. The assistant asks for missing answers before starting the browser or reserving browser credits. Add only information needed for every task.
  6. Save the tool and assign it to the assistant. You do not need to duplicate its browser instructions in the assistant prompt.
  7. Start a Test Call or Test Chat. The browser drawer opens automatically when the assistant starts a browser task. Use View browser to close or reopen it. Public demos provide the same live view.
For an appointment lookup, use the doctor’s profile as the starting page. Browser instructions can say “Read available dates and times; stop before selecting or booking an appointment.” Required information could be “Patient category”, with guidance “Ask whether this is a new or existing patient.” Actual answers come from the conversation, not from fixed defaults. The description explains when to use the tool; browser instructions explain how to carry out the task. Phone, widget and messaging conversations keep their existing interface. The assistant can use its assigned browser tool in the background. Viewing is read-only.

​
Videos and credits

History shows Browser recording when a saved video is available. Open the icon to play the WebM video in a modal. Multiple tasks have separate recordings. Videos are private, expire within seven days or earlier under the workspace retention policy, and are removed when their stored conversation is deleted. Zero-retention workspaces produce no saved video. A capture limit can produce a partial video, marked in the player. Under Settings → Data Retention, Calls governs phone calls, Test Call, Test Chat and web-widget chat. Messaging uses its own category, such as WhatsApp for text conversations. Browser videos follow the matching category, capped at seven days. Expired videos stop being accessible; deleting the stored conversation or workspace queues physical video deletion, with automatic retries if storage is temporarily unavailable. Browser Use consumes separate workspace credits for browser session time, including its brief idle period, and decision processing. A temporary maximum budget is deducted when a task starts; unused credits are returned after the session closes and reconciliation finishes. Closing the viewer does not stop the task. Ask the assistant to stop the browser task to cancel it.

​
Supported tasks

The tool clicks visible elements, fills ordinary text fields with known values, scrolls and reads page content. Tasks have bounded steps and duration. It does not bypass CAPTCHA, two-factor authentication or website restrictions. Password fields, file uploads, complex dropdown controls and popup workflows are not supported. If a page changes or information is missing, the assistant must check the result before retrying. A task reporting completion does not replace a visible confirmation on the website.

​
Example workflows

Use these as configuration ideas and test the exact website flow with your assistant. They are not guarantees that every site’s controls are supported. Dynamic calendars, login requirements or complex selectors can prevent completion. A direct profile or prepared results page often needs fewer steps than a homepage search. For a flight tool, put https://www.google.com/travel/flights in Start URL and www.google.com in Allowed websites. Add other exact hosts only when the chosen flow actually needs their redirects or resources. A URL belongs in Start URL; Allowed websites contains hostnames, without paths or wildcards. Example Description (when to use): “Use when the customer asks to compare flight prices.” Example Browser instructions: “Use the route, dates and passenger details supplied by the customer. Return up to three visible options with price, currency, departure time and stops. Do not invent missing prices or conditions. Stop before booking, payment or login. If the search controls are unsupported, report that the comparison could not be completed.” Mark only universally needed answers as Required information; keep a conditional return date in the question guidance. Prices and availability can change after the lookup.

​
API, MCP, CLI & SDK

Create and assign the tool with POST /api/v1/tools and PUT /api/v1/assistants/{id}/tools, or MCP create_tool and set_assistant_tools. CLI: famulor create-tool and famulor set-assistant-tools. SDK: client.api.createTool(...) and client.api.setAssistantTools(...). Live-view tickets expire after 60 seconds. Send viewer_origin to request a read-only WebSocket URL for that exact page origin. Downloads require the same workspace credential and calls:read scope. MCP returns an authenticated download path. Keep API keys on your server.