You have downloaded the app more than once, signed out and back in, maybe even tried a second computer, and nothing changed. Every job ends with "Autopilot stopped before it could confirm it finished." or "Otto couldn't start on this computer. Restarting the app usually clears it." Meanwhile the sign-in screen every other article talks about has never once appeared. In the words of the performer whose ticket produced this page: "I have downloaded it multiple times, also signed out and back in" and "I just haven't been able to sign into Claude or have it do much of anything." That combination has one cause and one fix.
The two messages that fingerprint this
Take the Autopilot line off the table first. "Autopilot stopped before it could confirm it finished" is a symptom, not the problem. Autopilot cannot run until the assistant is signed in to Claude, so every play, task and chat message dies at the starting line and reports the only thing it can. The app puts the job's own name at the front of that sentence, so yours may name a play instead of Autopilot. The rest of the line is the same.
The one that identifies your problem is the other: "Otto couldn't start on this computer. Restarting the app usually clears it." Alone it is common and harmless. Paired with a sign-in screen that has never appeared, it means something specific, and restarting will not clear it however many times you try.
Why the sign-in screen never appears
There is a half-installed copy of Claude on your machine. Before Booked Solid decides whether to show you setup, it checks whether Claude is present. A half-installed copy passes that check, so the app concludes Claude is already here and drops you straight into the main screen. It is not functional enough to actually start. So you are never offered the sign-in, and every job fails the moment it tries to think. Performers describe it precisely: "It's like it thinks I'm connected to Claude but it doesn't seem to be" and "It never gives any kind of prompt or opportunity to even try to sign in to Claude."
This is a blind spot in the app and we will not dress it up. It should catch this state itself, and we are fixing it so it does. Until that lands, you can clear it in about two minutes.
The fix: reinstall Claude cleanly, then restart Booked Solid
Order matters. Install Claude first, then fully quit and reopen Booked Solid, so the app re-checks the machine and finds a working assistant instead of a broken one.
Windows
- Close Booked Solid.
- Click Start, type
PowerShell, and open it. The plain blue one is fine, it does not need to be Administrator. - Paste this one line exactly and press Enter:
irm https://claude.ai/install.ps1 | iex - Let it run all the way to the end. It takes a minute or two.
- Open Booked Solid again, then open any task and send a short message in chat.
Mac
- Quit Booked Solid.
- Open Terminal (press Cmd+Space, type Terminal, press Enter).
- Paste this and press Enter:
curl -fsSL https://claude.ai/install.sh | bash - Let it run to the end, then open Booked Solid again and send a short message in chat.
That last step is not padding. Reopening on its own only re-checks whether Claude is present, so it can still drop you into the main screen. What tests the sign-in is the app trying to think. With a working Claude in place, that attempt comes back with a clean "not signed in" instead of nothing, and the app finally shows the screen it was skipping: One quick sign-in, with an amber Sign in now button.
If the app's own setup already failed on Windows with something about curl (35) or CRYPT_E_NO_REVOCATION_CHECK, that same PowerShell line is the way past that too.
Where the Claude sign-in lives (it is not in Settings)
Plainly: there is no "connect my Claude account" menu in Booked Solid, and the Claude login is not in Settings. If you have opened every tab looking for it, you were never going to find it. That is not you missing something. The app sits on top of Claude, so the sign-in screen appears by itself the moment the app notices Claude is not connected. Two ways to make it notice:
- Make the app try to think. This is the reliable one. Open any task and send a short message in chat, or start a play. When Claude reports it is not signed in, the app switches you to One quick sign-in on its own.
- Fully quit Booked Solid and open it again, especially if you have just installed or repaired Claude. A fresh open re-checks whether Claude is on the machine at all, and if it is genuinely missing you get Let's get Otto ready. Reopening does not test the sign-in by itself, though, so landing back on the main screen after a restart is normal and does not mean the fix failed. Do step 1 next.
If neither one gets you a sign-in screen, you are back at the half-installed Claude above. Do the reinstall first, then try these two again.
The sign-in itself, step by step
One thing to have ready: this needs a Claude account with an active paid plan. Claude Pro, about $20 a month, covers most performers. The free tier does not cover what Otto runs on, and no paid plan is the most common reason a sign-in will not go through.
- On the Let's get Otto ready screen, click Set this up for me and let the install finish. Nothing to type. If the screen does not move on by itself, click I'm ready to re-check.
- On the One quick sign-in screen, click Sign in now. Your browser opens the Claude sign-in page. Finish there.
- Claude shows a sign-in code at the end. Copy it, come back to Booked Solid, and paste it into Paste your sign-in code. The code expires fast, so paste it right after copying.
- Click Continue, then I'm signed in so the screen can re-check.
If your browser gave you a code but the app has not asked for it, click My browser gave me a code on that screen and the paste box appears.
Four dead ends worth skipping
- Do not hunt for a button called "Sign in for me". There is not one. Support gave a customer that label once and sent him looking for words that do not exist in the app. It is Sign in now.
- The "Set this up for me" button on the Connections rows is a different button. On the Claude Code row it opens a box for an Anthropic API key, which is not the sign-in you want here. An Anthropic key sitting on the computer actually switches account connections like Gmail off.
- Signing in at claude.ai in your browser does not fix this on its own. Almost everyone tries this first, and it is a dead end. The assistant on your computer keeps its own sign-in.
- Reinstalling Booked Solid again will not help. A fresh copy does not touch Claude. It finds the same broken install and makes the same wrong decision. Fix Claude, not the app.
If Otto tells you there is no Claude login, Otto is wrong
A performer wanted to check which Claude account he was signed in with. He asked the assistant inside of Booked Solid and got this answer:
"Good question, but there is no separate 'Claude' login in Booked Solid. You do not sign in with Claude at all. If you were told to find a 'Claude' username somewhere, that is not part of Booked Solid, so I would not chase that down. If something is asking you for a Claude login, be careful, do not enter any passwords there."
That answer is wrong, and we are sorry it was ever given. Otto runs on your own Claude sign-in, and the browser sign-in you do during Let's get Otto ready is a real Claude login. Worse than wrong, that warning steered a paying customer away from the one claude.ai page he needed to approve Gmail, and cost him days. The cause: the app told Otto that Gmail rides your Claude account, but never told Otto that Otto himself runs on your Claude sign-in, so the model filled the gap with a password-safety warning. Fixed on 18 July 2026 and in every release since: Otto no longer denies the Claude account, he must attempt the Gmail tool before claiming Gmail is not connected, and the Claude Code card now warns you when an Anthropic API key on the computer is switching account connections off.
Keep the instinct that made you hesitate, though. Never type a password into a prompt you did not expect. The rule that holds both things true: the only real Claude sign-in happens on claude.ai, in your own browser, on a page the app opened for you. And the wider lesson: Otto and the in-app Help buddy can be wrong about the app itself, because they only know what the app has told them. This help center is the source of truth.
Which Claude account am I actually signed in with?
Above the message box, click Power view (it sits next to Chat). In the terminal area, type claude and press Enter, then type /status and press Enter. The account line in what comes back is your answer.
If the sign-in screen still never appears
Then it is specific to that machine, and we would rather look than guess. In the right pane, open the Settings tab, stay on General, scroll to the support section and switch on Support logging. Reproduce the failure once, then click Generate Support Bundle. Submit a ticket from this help center with that bundle attached, and tell us three things: Windows or Mac, which step above you got to, and the exact words on your screen. If you would rather not touch a command line at all, say so in the ticket and we will get on a screen with you and finish setup in one go. You bought this to get booked, not to debug an installer.
Related articles
- Get Otto ready: the one-tap assistant setup screen. One caveat: it says that screen appears automatically whenever the assistant is not installed or not signed in. The half-installed Claude on this page is the case where it does not.
- Which AI runs Booked Solid? Your own Claude account (API keys are the exception)
- Otto says 'Failed to authenticate' or a 401 error: how to sign back in
- I installed it and nothing happens: the app will not open or launch
- Generate a support bundle and turn on support logging
Other ways people describe this
- Where do I connect my Claude account?
- I can't find the Claude login in Settings.
- Booked Solid never asks me to sign in to Claude, and the One quick sign-in screen never shows up.
- I asked the assistant inside of Booked Solid and got this answer: there is no separate 'Claude' login in Booked Solid.
Still stuck? Submit a ticket from this help center and we will take it from there.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article