FAQ
Does Logos AI work offline?
Section titled “Does Logos AI work offline?”The desktop app is the main offline-friendly path. The browser reader is lighter and depends on a live data source unless you build a more custom backend around it.
Do I need AI to use Logos AI?
Section titled “Do I need AI to use Logos AI?”No. Reading and navigation are still valuable without AI. Logos Chat and the other AI tools are optional layers on top of the reader.
Can I use my own API key?
Section titled “Can I use my own API key?”Yes. That is the BYOK path. Use API_BIBLE_KEY for desktop and backend workflows, and use PUBLIC_API_BIBLE_KEY only when you intentionally want a browser-visible key in the static web build.
Why is the web reader lighter than the desktop app?
Section titled “Why is the web reader lighter than the desktop app?”Because the web reader is the easiest way to start, while the desktop app is the richer environment for offline reading, audio, local AI, and longer study sessions.
What should I install first if I am non-technical?
Section titled “What should I install first if I am non-technical?”Use the native installer from the public GitHub releases page:
.pkgon macOS.exeon Windows.debon Ubuntu-class Linux systems
What should I install first if I am technical?
Section titled “What should I install first if I am technical?”Use whichever matches your workflow:
- Homebrew tap:
jd4rider/homebrew-logos-ai - Scoop bucket:
jd4rider/scoop-logos-ai - shell bundle
- direct release asset download from
jd4rider/logos-releases
The important part is that the desktop app and the CLI still land as one install story.