In Gemini, we have the “Deep Research” feature. In this mode, the answer is more profound, articulate, and helps us deepen our understanding of a topic. At least for me, that is not the case in Logos today.

Let’s say we want to study the intercession of the exalted Lord Jesus for the saints in heaven. When I enter the prompt: “Help me understand the intercession of Christ as seen, for example, in Romans 8:34 and Hebrews 7:25,” the Bible Assistant returns an answer that is about four paragraphs long and quotes only four resources. However, I selected my “Systematic Theology” collection, which contains 35 books.

It is good to have quick and brief responses, but it would be even better to have a more detailed and in-depth answer.

In “Deep Research,” Gemini usually takes about five minutes to process and returns a response that can be 10–15 pages long. If something like that could be implemented in Logos, it would be absolutely amazing. The truth is that, although we want to restrict our research to our Logos resources, the responses from the Study Assistant are often too superficial, so we end up using general AI tools.

So what is the proposal? That Logos should have an AI capable of performing in-depth research within our resources, analyzing multiple books and producing an answer that truly engages with them. In the example above, it would “read” all my systematic theology books and show what each contributes to the topic, highlighting the nuances between them.

I am new to syntax search, so I am looking for help with an issue where certain results are not showing up.

I am trying to find instances similar to the end of Lev. 16:10, where there is a clause with שׁלח and an indirect object with a prepositional ל (for those unfamiliar with Hebrew, the ל would be attached to a word separate from שׁלח). While the search parameters are producing some verses, the results do not include Lev. 16:10, so I am wondering if any of you have any ideas:

Here is the BHS WIVU Constituency Tree of Leviticus 16:10 for reference:

Here is Leviticus 16:26, which does show up in the search results and has grammar parallel to 16:10:

The issue seems to be with the "phrase" branch, as deleting it and keeping around only the "word" branch results in 800+ results of שׁלח, including Lev. 16:10.

Skipping levels is, of course, enabled. As both 16:10 and 26 have the same branches (Phrase → Phrase Atom → Clause → Clause Atom → ל), it does not seem this would influence the results.

Any knowledge is appreciated.

first search produces 2 results. Searching again, produces 6 results, searching again, produces 8 results.

What's the issue with this, and how can a search produce the same results if just searching again?

Would be nice to see this in a upcoming update to the mobile app.

4.x PNLS — PROPER NOUN LOOKUP SHEET

יְהוֹשֻׁעַ; Ἰησοῦς; ܝܫܘܥ; Iosue

Afrikaans:Josua; Brazilian Portuguese:Josué; Dutch:Jozua; English:Joshua; French:Josué; German:Josua; Italian:Giosuè; Korean:여호수아 (yeohosua); Simplified Chinese:约书亚 (Yueshuya); Spanish:Josué; Swedish:Josua; Traditional Chinese:約書亞 (Yueshuya)

Hoshea; Jehoshua; Joshua ben Nun; Yehoshua; Yeshua; Osee; Jesus (Vulgate/Greek form overlap)

Judaism:Hebrew:יְהוֹשֻׁעַ; Christianity:Greek:Ἰησοῦς; Christianity:Latin:Iosue; Islam:Arabic:يوشع (Yusha)

Afrikaans
Current: Josua
Older / historical: Josuwa

Brazilian Portuguese
Current: Josué
Older / historical: Josue | Josuá

Dutch
Current: Jozua
Older / historical: Josua

English
Current: Joshua
Older / historical: Josue | Josua | Jehoshua | Yehoshua | Yeshua | Osee

French
Current: Josué
Older / historical: Josue

German
Current: Josua
Older / historical: Josua

Italian
Current: Giosuè
Older / historical: Giosuè

Korean
Current: 여호수아 (yeohosua)
Older / historical: 여호수아

Simplified Chinese
Current: 约书亚 (Yueshuya)
Older / historical: 約書亞 (Yueshuya)

Spanish
Current: Josué
Older / historical: Josue

Swedish
Current: Josua
Older / historical: Josua

Traditional Chinese
Current: 約書亞 (Yueshuya)
Older / historical: 約書亞

Verbum precise search term: (יְהוֹשֻׁעַ OR Ἰησοῦς OR ܝܫܘܥ OR Iosue OR Josua OR Josué OR Jozua OR Joshua OR Giosuè OR 여호수아 OR 约书亚 OR 約書亞 OR Josue OR Josuá OR Hoshea OR Jehoshua OR Joshua ben Nun OR Yehoshua OR Yeshua OR Osee OR Jesus OR يوشع)

The problem is that it complains about the lack of a closing paren when the closing paren is clearly in view; remove the parens and one gets an unexpected operator in front of the first OR. Net result is that I am unable to scan all my books for a proper noun leaving many interesting books hidden behind the Logos one language (well probably one writing direction) at a time invisible rule.

I purchased the Wilmington's Guide to the Bible, 30th Anniversary Edition from the Logos app quite some time ago after verifying that I could search by page number. I actually paid more for this book from Logos because other sites did not have this feature. It has worked for over a year where I could search "Page 1219" and it would take me to page 1219.

A recent update has made this no longer the case. Instead, I get hundreds to thousands of results, none of which are the page number I am looking for. I am not sure how it is for other books, but this specific book is best likened to a Thesaurus. Without this feature, the virtual book is rendered just about ineffective in use. I have to scroll for a very long time to find the page I'm looking for, even with using the search to get "close" to the page number I need.

Please revert this search function back to a working state so my purchase is once again rendered to its advertised state, and so I can use this precious resource in an effective manner once again.

Respectfully,

Ethan

The tag-based illustration guide is basically just a combined glossary for my books of illustrations. It's nice to have available, but I almost never use it. I have one or two anthologies that I really like, and I only delve into the others if I'm desperate.

The Illustrations generated by Sermon Assistant are much too vague and obvious to be useful, even if I wanted to include AI-generated content in my sermons.

What makes the search for good illustrations especially maddening is that I know my library is full of them. I have sermon collections, church history books, a library of classic literature, and the whole "Sermon Illustrator" set, but it would take years to go through and tag everything that might be useful.

When the Study Assistant was first announced, I was very excited because I thought I would finally have a way of searching for specifically themed illustrations within my library. Unfortunately, that's not something Study Assistant is capable of doing. After experimenting with several different prompts (over several agonizing weeks), I finally got it to admit the following:

"My search function doesn’t allow me to:

1. Filter by narrative form — I cannot systematically distinguish between narrative portions and didactic passages across your entire library.

2. Detect thematic patterns across diverse genres — While I can search for keywords and concepts, I cannot comprehensively scan fictional works, sermon illustrations, and church history narratives simultaneously to identify characters and events matching your specific theme.

3. Locate and extract specific passages — I cannot systematically retrieve the precise textual locations that best exemplify your theme across multiple book collections."

Would it be hypothetically possible to make the Study Assistant capable of performing the above functions?

Would it be possible to update the Sermon Assistant, allowing it to search for illustrations rather than merely generate them?

Alternatively, would it be possible to run a one-time AI-powered process to catalogue content in my library and make things easier to find?

The results are fine on screen; here are the results from NET, for example:

But when I press <Ctrl P>, there are words missing from the middle or end of the preceding context if the preceding context isn’t short. (In this example, the only verse that isn’t affected is Eph 6:18.) This is visible on the screen:

Then if I click on “Send to new document: Microsoft Word”, the same problem occurs (I've added bolding where the problem occurs):

Is this a known issue?

Quería comprar una biblioteca, pero sin ella, siento que no tiene mucho sentido, ya que es mi biblia favorita. Tengo otra cuenta donde sí la tengo disponible, pero parece que no puedo volver a comprarla para mi cuenta nueva.

I was reading through my daily email newsletters on AI, InfoSec, and Big Data, and found a different approach that may benefit Logos. In my understanding, most AI approaches train all-purpose LLMs for specific purposes and use retrieval-augmented generation (RAG) to ensure currency and applicability. The RAG and specific training data set improves accuracy but still leaves room for hallucinations because the LLM design and development include training data from across the Internet and lack the specific context of the enterprise. It's also very power and time intensive, making it expensive to operate. A new approach being explored in highly regulated industries like banking, where accuracy must be virtually perfect, uses purpose-built small language models (SLMs) trained exclusively on the target data set. The approach is domain-specific, faster, and virtually eliminates hallucinations because the SLM understands the domain language natively. Here's the link to the article: https://ragaboutit.com/the-small-language-model-awakening-why-enterprise-rag-is-abandoning-foundation-models-for-domain-specific-precision/. If done well, the SLM approach would eliminate the need to check outputs across multiple LLMs to minimize hallucinations as well, further increasing output speed and reducing licensing fees.

If the article is correct, taking an SLM approach could make Logos AI faster, more accurate, and less expensive to operate. As the article points out, it may also require change in the architecture, but my suspicion based on Mark's regular updates is that Logos' existing architecture isn't far off.

Other commands are also missing from the Smart search results, such as Save as Visual Filter" and "Save as Word List". I can see why these might be missing, but not the Save as Passage List command.

I don't know if this is a bug or a" feature," but I hope Smart searches will soon let the search results be saved to a passage list.

*Logos 40 RC2 (version 40.0.351), Windows 10.

What we need is a global setting that allows us to hide all locked resources (from everywhere).

As a bonus, throw in a setting to hide all Temporary resources as well. We don't want to invest time studying a resource that will disappear if we stop paying the subscription.

For example, an English search for "Law of Moses" brings up numerous references on a Bible search, but I cannot make "תורת משה" bring up anything. I have tried "תורה" AND "משה" but still no luck. I couldn't get it to work in a morph search either. I assumed that Logos would handle Hebrew the same way it handles English... type it in and search for it, but no luck.I've tried with and without quotation marks, etc.

I really wish I could highlight a phrase of text and have it search for all the words in the phrase at once, like a multi concordance search. Can this be done? I assumed it could, and that's one of the main reasons I bought the program.

Any help appreciated.

-John Quant

I have dozens of dictionaries that show up in the search results but sadly not one hit on any of my Bible Atlases.

I would like to request that an extra section be added to Factbook for specialized geographical resources such as Atlases and Maps.

Is the smart search feature biased to only conservative views?

Perhaps a toggle setting could be added in Preferences so the application will always display the full synopsis, without the extra step? Fewer clicks may seem a nit-picky request but little things save on frustration over the long haul (which is why I'd also love to see more keyboard commands implemented). Thanks so much for your time.

Whether I am studying a name, a pericope, or a lemma, I always have a series of questions that I ask in order to build a "lay of the land" for my study. In my mind, this is equivalent to filling in a graphic organizer, my preferred methods for insuring I don't miss elements although I may choose to omit them. I would find AI far more useful if I could "preload" it with a set of questions and step through them one at a time while being allowed to insert other queries between them. If you aren't familiär with graphic organizers, another way to visualize what I want is to preload a series of questions taken from a workflow - perhaps a question per sub-step again with the ability to add extra questions as needed.

Being able to take a series of questions that are quite repetitive i.e. repeating the passage, the scope etc. make entering them manually often more effort than is worth it. Using a list and replacing the passage, name, lemma, lectionary date, event … makes it easy to scan one's library for the most information rather than just the easiest information to find.

This seems unnecessary

Is there a particular reason for this?

1. Make the AI usage credit cost less. I have a Max subscription, and I'm going through my credits very fast, and not even over-using the features. I have noticed that simply using Factbook and Search, even if I don't expand the "Questions to ask" section or interact with the AI, I am being charged credits. This shouldn't be. The segments that use AI credits should be collapsed (disabled) by default, and only activated when the user elects to expand that section, perhaps with an alert indicating that the action will cost credits. In other words, regular use of Factbook and Search should not cost any credits by default, unless we choose to explore further.
2. Please add a filter that allows us to ask the AI questions based SOLELY on scripture. It is nice to have the wealth of commentaries available with the "All Books" filter, which also gives me an idea of what books I should buy next. That should stay as it is. But the most important filter for me, would be to sometimes ask the AI for analysis on the bible texts alone, without human bias. This would be priceless!

Yes, this is for personal use but it may be helpful to someone and I would be grateful if someone pointed out any search that is missing.

Not only would I like to see the labels expanded

but I would like the entry of labels in a search argument to be automated in the same sense that the BK tags are - enter the tag, type some letters, select from a drop-down select list.
Step 1: I enter label: and get the drop-down list from the Concordance section of the Passage Guide (plus any labels I have created in my application).

Step 2: The app returns a list of the possible attributes each with an input field and a drop down selection menu. As an example, for the Covenant label

Step 3: I hit "done" and a search is built with only the attributes I specified appearing in the search argument.

At the moment my actual workflow is:

1. remember there is (or might be) a label for that
2. open the Concordance section only of Passage guide
3. use Settings to find appropriate label
4. use Concordance tool over a range of scripture that I am sure will have an occurrence of the label
5. open the passage with the label
6. use the context menu to copy the search argument into my search screen
7. modify and delete attributes to match my actual needs.

I think it is obvious that my proposal simplifies the label search and makes it much more accessible allowing users to actually use the power that you put just out of reach of our fingertips.

So as simply as possible, how do I do something as basic as selecting a block of verses? I know the Passage List is involved, but sometimes it adds the verses, and sometimes not, and I can't tell why it behaves one way or the other.

Thank you and I will stop fighting with trying to copy this little list until I hear how to do it.

This defeats the purpose of the keyboard shortcut (Cmd+Shift+S) that opens the search pane because once the "search tab" opens you still have to use the mouse to click in the search box before you can actually perform the search.

Ideally, the cursor should be placed in the search box by default, allowing users to start typing immediately after opening the search tab. Most users perform countless searches - so yes, this BUG is bothersome.

For any programer at Logos, this would be such a simple 5 minute fix. But we have reported this bug multiple times since July 2025 and Logos will not fix it. Please help. Thank you! We LOVE Logos!!

With the recent addition of Print books being searchable through Factbook- it would be incredible to extend this feature to the Guides built within Logos. I use the exegetical and passage guides frequently for my study, and it would be handy to have print books within those search options (commentaries, grammars, systematic theologies, etc).

I've just watched an interesting YouTube video of Demis Hassabis and Josh Woodward (Google) today (Tue, 18 Nov 2025) discussing the benefits of the new Gemini 3.0 AI Engine.

Q1. Are there plans for Gemini 3.0 to be used in the LOGOS Search Function?

Q2. Will there be a noticeable performance improvement in the LOGOS Search Function?

Q3. Will there be any other feature improvements in the LOGOS Search Function?

Thanks.

We don't want subscription services; we simply want the program we purchased to work properly. Thank you.

1. Open 2 search windows.
2. In the left search window, search "left search window search 1".
3. In the right search window, search "right search window search 1"
4. Repeat several times.
5. Additionally, in a Bible right click a lemma and do a Bible Search
6. Do more "left/right search window search X"

Here is what I get. In the left search window, the search history results contain history results from the right search window. It is missing left search window search 1, 2, and 3.

For the right search window, the search history contains only the searches from the right search window. (While this seems more consistent, what happens when you close these two search windows and open a new search window? Ideally, all searches should appear in the search history for a new search window).

For fun, I restarted Logos. Surprisingly, in the left search window, the search history changed. The Hebrew lookup is gone, replaced by another search from the right search window.

The search history from the right search window stayed the same:

There seems to be a lot of issues here with search history to look into. This is an issue as when we are studying a passage of Scripture, we often want to go back to a previous search. If those searches are deleted from search history, that is confusing and disruptive. Thanks!

The Precise Search mode in Logos is a powerhouse tool designed to help you zero in on specific words and phrases with incredible accuracy. It moves beyond a simple keyword search by using special commands, or "operators," to refine your results.

For example, you can:

• Find an exact phrase by wrapping it in "quotation marks". This is perfect when you're looking for "love of God" and not just results that contain 'love' and 'God' somewhere in the same article.
• Find words near each other using proximity search. Jesus WITHIN 5 WORDS pray will find every instance where "Jesus" appears within 5 words of "pray," in any order!
• Combine or exclude terms using AND, OR, and AND NOT.

These operators can transform your study, helping you find connections and references you might have otherwise missed. But the best tips always come from the community...

How do you use Precise Search in your study?

What’s your most-used search operator? Do you have a favorite "power query" that helped you unlock a new insight in a passage?

Share your tips and tricks below!