What’s new - Beta Testing

On mobile, verse previews now stay open while you scroll or copy text—closing only when you tap Close or press Esc/back. Desktop behavior is unchanged.

• Desktop: hover to preview, click to pin, press Esc or scroll away to close (unchanged).
• Mobile: bottom-sheet pop-up persists during scrolling; tapping outside no longer dismisses it—use the Close button to exit.
• Fixes accidental closures when reading long passages or copying text on mobile.
• Where: Chat & team conversations.
• Why: aligns with mobile UX guidelines and prevents unexpected pop-up disappearance.
• Tip: if you still see old behavior, perform a hard refresh.

• Mobile: the Chats / Folders drawer now slides smoothly in and out. You can swipe left on the drawer or the dark backdrop to close it.
• Desktop: click the hamburger icon to toggle the drawer (unchanged).
• The dark overlay no longer blocks taps when the drawer is closed, so you can interact with the rest of the page without accidental tap traps.
• The drawer reliably reopens after you close it—no more stuck states when swiping away.
• Where: Chat → left sidebar.
• Why: improves the user experience on phones and tablets by matching common mobile navigation patterns.
• Tip: try swiping the drawer closed or tapping outside to hide it. If you still see the old behavior, do a hard refresh.

• All replies now appear gradually with a smooth typing effect; no more sudden walls of text.
• Both standard chat and team conversations use the same streaming API, ensuring a unified experience across all modes.
• Improved reliability for long replies and faster feedback when the assistant is processing your question.
• Where: Chat → all modes (Standard, Study, Q&A, Review, Debate, Kids) and Team Studio conversations.
• Why: creates a more polished, professional feel and reduces cognitive load while reading.
• Tip: if you still see replies appear all at once, try a hard refresh or clear your cache. Let us know if the issue persists.

• When Boost is on, a small blue banner labeled “Boost mode powered on” now appears directly above the prompt box.
• Toggling Boost on or off updates the banner instantly—no more refreshing the page to see whether Boost is active.
• The banner uses the same 119 blue as the Send button and prompt outline, so the status is clear without adding visual noise.
• Where: Chat → message composer, when Boost (GPT-5) is enabled.
• Why: gives a persistent, easy-to-spot reminder when a Boosted reply will cost credits and keeps the UI in sync with the toggle.
• Tip: if the banner doesn’t appear/disappear when you toggle Boost, try a hard refresh and confirm you’re on Build v1.25.

• While a reply is running, the rotating status phrases (for example, “Sending…”, “Unrolling the scrolls…”, “Testing everything…”) now appear inside the prompt box as the placeholder instead of “Ask the 119 Assistant…”.
• The composer becomes read-only while the assistant is working, clearly signaling that you can’t submit another question until the reply finishes.
• Once the response is complete, the placeholder switches back to “Ask the 119 Assistant…” and the box is editable again.
• Where: Chat → message composer.
• Why: avoids confusion during longer replies and keeps the live status message right where you’re looking—next to the disabled Send button.
• Tip: if you still see “Ask the 119 Assistant…” while a reply is generating, do a hard refresh and try again.

• If you start a long reply, move to another chat, and then come back before it finishes, the Generating response… card now reappears and stays visible until the answer is complete.
• The Send button remains disabled and shows the spinning progress icon while the assistant is still working, so it’s clear the reply is still in progress.
• Behind the scenes, the assistant keeps generating in the background and the conversation picks up where it left off when you return.
• Where: Chat → any conversation with a long-running reply.
• Why: prevents confusion when jumping between chats and makes it obvious when a reply is still being prepared.
• Tip: if you return to a chat and don’t see the Generating response… card while you know a reply should still be running, try a hard refresh.

• Old Testament quotes replace all-caps “LORD” with “YHWH” for the divine name.
• The assistant’s own prose avoids “Lord”/“LORD” for the Father, preferring “YHWH” except when clearly referring to Yeshua or a human.
• Where: Chat → all assistant replies.
• Why: aligns with 119 Ministries’ preference for using the tetragrammaton.
• Tip: if a verse still shows “LORD,” start a new chat or quote it again.

Short, standalone lines are now automatically promoted to bold section headings and styled with a larger font when using several chat modes. This makes sections easier to spot and mirrors the style previously exclusive to Debate mode.

• Where: Standard, Review, ELI12, Family Study & Debate.
• Not in: Response, Kids, Study & Q&A.
• Why: improves readability and consistency across article-style replies while keeping conversational modes (Q&A, Kids) unchanged.