Web Search and Browser
“Search” and “browser” refer to several different Captain Who capabilities with different permission and data-flow boundaries.
Quick comparison
| Capability | Purpose | Where data goes |
|---|---|---|
| Left-sidebar search | Find local conversations | Remains on the device |
| Agent web search | Search public web sources | Query is sent to Tavily |
| Agent web-page reading | Read the body of a specified web page | Target URL is sent to Tavily |
| Right-sidebar browser | User browses manually | Connects directly to the visited website |
| Browser automation | Agent operates the managed browser | Connects to websites with additional authorization and risk checks |
Search local conversations
Select “Search” in the left sidebar and enter a keyword. Results show the conversation title, a matching excerpt, and its project. Select a result to open that conversation.
This is local text search. It does not send your query to Tavily and does not search by semantic similarity.
Configure agent web search
- Open “Settings → Configuration.”
- Find “Web search.”
- Enter a Tavily API key.
- Enable web search.
Without a key, the interface does not allow the setting to be enabled. After you disable the setting or clear the key, agents no longer receive the Tavily search capability.
Example task:
Search the official release notes for this library from the past month. Use official sources only. List each version, release date, and link, and distinguish confirmed facts from inferences.
An agent can use “Web search” to find results, then “Read web page” to inspect a specific page. Search summaries may be incomplete. For version, pricing, policy, or security information, ask the agent to open the original source and provide a link.
Use the right-sidebar browser manually
- Open “New panel → Browser” in the right sidebar.
- Enter an HTTP or HTTPS address in the address bar.
- Use back, forward, refresh, zoom, and new tabs.
- To sign out of a website account or remove cookies, open the browser menu and select “Clear browsing data.”
The browser uses a separate, persistent session. Cookies, site storage, and cache persist between tabs and app restarts until you clear browsing data.
To reduce risk, requests from web pages for camera, microphone, location, system-notification, and similar permissions are denied. Arbitrary custom protocols are also unsupported. Valid links that open a new window use a new managed page instead of receiving an unrestricted system pop-up.
When browser automation is appropriate
Web search is appropriate for finding sources and reading pages. Browser automation is appropriate for clicking, filling fields, paginating, taking screenshots, uploading, or downloading. It controls only the managed browser in the Captain Who right sidebar and does not connect to your system browser.
See Browser Automation for setup and use. Even if you have already signed in to a site manually, the agent still needs capability authorization, and sensitive operations may require a separate approval.
Privacy and safety notes
- Do not paste a Tavily key, website password, or cookie into a task.
- Web content may contain instructions designed to induce an agent to disclose information or perform a dangerous action. Treat it as untrusted input.
- Automated access to localhost, private networks, downloads, uploads, storage, scripts, and similar targets may require approval or be denied.
- Clearing browsing data removes the managed browser cache, site data, and icon cache. It does not delete conversation history.
Current limitations
- Agent web search currently connects only to Tavily; there is no selector for another search service.
- The browser supports only HTTP/HTTPS and controlled PDF viewing paths.
- All website permission requests are denied, so features that rely on a camera, location, or notifications may not work.
- Browser artifacts produced by downloads are short-lived resources. Explicitly export them when they need to be retained.