Otto opened its own browser window and wandered onto pages you didn't want

You set Autopilot going with the Run my booking operation preset, came back later, and something was clearly wrong. One performer opened his note to us with I ran into a problem with this morning's Run My booking operation. Instead of working in the browser you already had open and signed in, Otto opened its own browser, and once it was in there it went somewhere you would never have sent it. The same morning gets described in different words: it opened a separate browser window, it went to pages I did not want, it landed on sketchy pages. There is a real cause and a fix that holds, and the order of the steps matters more than any single step in it.

First, the thing you are probably worried about: nothing was sent, posted, or submitted on those pages. Otto can open and read pages on its own, but anything that submits, uploads, or posts always waits for you first. So if seeing that it browsed somewhere weird made you wonder what it did in your name, the answer is nothing. It read, and it wandered.

Why it used a browser you never opened

Booked Solid has two ways of doing web work, and on older builds a plain "do this on the web" request goes to the wrong one for what you wanted.

The first is the app's own browsing window. It is real Chrome, or Microsoft Edge when Chrome is not installed on the computer, which has worked since version 1.11.8. It runs on a dedicated profile of its own on purpose, so its sign-ins survive between runs and never touch your personal browser. That is why it opened a separate browser window, and why none of your everyday logins are in it: unless you signed in inside that window yourself, every site it opens meets a stranger. That is the honest answer to why isn't it using the browser I already have open. On an older build, the web task was never pointed at your window in the first place.

The second way is Otto clicking and typing in the browser you use every day, with your real logins. That is what you wanted, and it is a setting.

The part nobody guesses: an open chat keeps the browser it started with

Which browser a conversation uses is decided once, when that conversation starts. Updating the app does not change it. Turning the setting on does not change it. The chat carries on with whatever it was wired to when it opened. That is why the most common follow-up we get is "I updated and it still did it" - the update was real, but it was tested in a chat that had already made its choice. So what follows is one sequence, not three suggestions. Doing the last part first fails quietly and looks exactly like the fix not working.

The fix, in this exact order

1. Quit Booked Solid fully, then open it again. Not minimize, not close the window and leave it running, not click the update badge and carry on. Then open Settings and read the Updates section, which names the version you are running. You want 1.11.25 or newer. If it is older, take the update with Check for updates at the top of the window, or from booked.kivimedia.co/download, and quit fully once more after it installs.
2. Start a fresh chat. Do not reuse the conversation that misbehaved, however much context is in it. Use the Start fresh link in that tab, or open a new task tab. Have the browser you want Otto to use open on screen and signed in before you begin.
3. Ask for the web task and name the window, in words. Put it in the request itself: tell Otto to use my Edge window that is already open, or your Chrome window, whichever one you live in. Do not assume it will work this out from context.

Make it the standing behavior

You should not have to name the window every time. To make your own browser the default for web work:

1. On the Connections screen, under Tool access, switch on Control this computer.
2. On the Permissions tab, set Control this computer to Read & write, so it may act and not only look. This is the step that catches people. Switched on by itself it is look-only: it sees your screen and cannot click or type, and web tasks keep using the app's own browser rather than strand you with one nobody can drive. When Booked Solid detects that state it says so and offers an Allow actions now button in place.
3. In Settings, switch on Web tasks use my own browser. With that on and computer control able to act, the separate browsing window never launches for a web task.

This is also the path for marketplaces that reject automated browsers, GigSalad and The Bash among them. And the rule above still applies: the setting reaches your next chat, not the one you are sitting in.

On a Mac

Computer control needs one permission from macOS itself. Open System Settings > Privacy & Security and turn on Booked Solid under both Accessibility and Screen Recording. Come back to Booked Solid afterward and it picks the change up when the window regains focus.

On Windows

There is no operating-system permission to grant. Allowing actions on the Permissions tab is all it needs.

Signing in to Otto's own browser window is a dead end

Almost everyone tries this first. The separate window opens logged out, so the natural move is to sign in to it. The sign-in does stick, and that window will still never be your browser: it runs on a dedicated profile that exists precisely so it never touches your personal one. You end up maintaining a second set of logins in a window you are not watching, and the original complaint is untouched. Skip that step and send the work to your own browser instead.

You do not need to switch web browsing off

You may meet older advice, some of it from us, saying to turn Web browsing (Chrome) off entirely so the separate window stops appearing. That was the only workaround before Web tasks use my own browser existed. It works, and it costs you browsing on every run where the app's own window is the right tool. On 1.11.25 or newer, do not make that trade.

This is not the same as browsing that keeps dropping

If your symptom is the connection dropping and reconnecting, the page resetting to blank mid-task, or a verify you are human check that restarts forever, that is a different fault with a different cause. Read Browser control keeps dropping, resetting, or getting stuck on "verify you are human" instead.

If it still happens after all three steps

Capture a support bundle at the moment it happens, not later and not after a restart. In Settings, switch on Enable Support Logging, reproduce the run, then click Generate Support Bundle. Full steps: Generate a support bundle and turn on support logging. The bundle now carries what each connection was allowed to do and the routing decision that came out of it, not only how many connections were on, so we can read which browser your run chose instead of asking you to prove your settings with screenshots. Your keys and client messages are not in it.

Do not post it in the Facebook group. Posts there do not reach our support desk, so nobody here sees them, and the report sits waiting for a reply that is not coming. Attach the bundle to a ticket in this help center with two or three lines about what you asked for and what it did instead.

Still stuck? Submit a ticket from this help center and we will take it from there.