Dr. Olivia
Dr. Olivia — Release Notes What changed and when
Guide Home Back to Dr. Olivia

July 30, 2026

Dr. Olivia can now go back to your textbooks part-way through a conversation instead of only at the start, and video sessions start reliably again on machines with a webcam.

New features

  • Dr. Olivia goes back to your textbooks mid-conversation. Until now, Dr. Olivia pulled the relevant pages from your course materials once — based on the first question you asked. That works until the conversation moves, which it always does: you ask a follow-up two levels deeper, or you change subjects entirely, and she's still holding the pages from where you started.

    She can now go back and search your textbooks again, mid-answer, as many times as a conversation needs — and she writes the search herself, in the proper terminology, rather than being stuck with however you happened to phrase the question. You don't have to ask her to; it just happens.

    Three things this changes in practice:

    This search is deliberately limited to your textbooks — not lecture captions or video summaries. Those are someone's interpretation of the material; the textbook is the material. When the point is to confirm a fact, she checks the source.

    If the answer genuinely isn't in your curriculum, she'll tell you that plainly rather than filling the gap from general knowledge and leaving you to wonder which is which.

    • Follow-ups go deeper. "Walk me through the actual mechanism" now sends her back for the mechanism, instead of re-explaining the overview she already had on hand.
    • Changing subjects works. Switching from renal to cardiology halfway through a session no longer leaves her teaching from the wrong chapter.
    • She checks herself against your material. Before stating something your materials don't clearly support, she goes and reads what they actually say.

Bug fixes

  • Video sessions start again on computers with a webcam. Starting a video session could fail immediately — Dr. Olivia never appeared and the session simply didn't connect. It affected computers that have a working camera, which is most of them; oddly, machines with no camera at all were unaffected.

    The cause was in how we set up the video connection. When we meant "use the normal camera settings," we were passing along an empty value instead of leaving the setting alone, and the video service rejected the whole request before the session could open. We now leave the setting untouched, which is what was intended. Nothing changed about how the camera behaves once you're in a session, and machines without a camera keep working exactly as before.