Core app requirements
- Python 3.11+ for native installs.
- Git for cloning and Windows agent shell workflows.
- Docker Desktop or Docker Compose when using the container route.
Day 2 product-map page ยท Updated 2026-07-02
Help users decide whether their machine should run local models, API models, Docker or a remote server.
Independent guide. Unofficial. Verify commands against the official Odysseus sources before running them.
Day 2
Odysseus requirements guide for Python, Git, Docker, RAM, VRAM, GPU, Ollama, local models and API-backed fallback plans.
Last-click answers
These cards turn the common search intent into a concrete next step, so visitors do not need to bounce back to Google for the same blocker.
The workspace itself is lighter than local model serving. A weak laptop can still test Odysseus with an API provider or a tiny local model, but large local models need much more RAM, VRAM and patience.
Next: Use API fallback when hardware is the blocker.
Not for opening the workspace. GPU matters when you expect fast local inference, Cookbook model serving or larger local models.
Next: First prove login and one small response, then evaluate GPU.
Model acceleration and shell tooling differ by platform. Apple Silicon users should know Docker cannot use Metal GPU acceleration, while Windows users must watch Python Launcher and PowerShell details.
Next: Pick the OS guide that matches the machine, not the tutorial you saw first.
Editorial basis
This page is written as a setup decision aid, not a copied README, transcript dump or doorway page.
Commands, download advice and risk warnings are anchored to the official repository, the official README and visible project behavior before any community shortcut is treated as usable.
It turns the Odysseus requirements search into a specific route: source verification, one setup path, first-run evidence, safe support boundaries and the next internal guide when this page is not enough.
Use it when you need a plain-English decision path. If you are changing source code, packaging releases or reporting upstream bugs, move from this guide to the official source and issue tracker.
Update this page when the official install route, default branch, setup scripts, login behavior, model-provider instructions or public-access guidance changes.
Next action
Each page now gives a short route from search intent to a concrete setup action, so beginners can keep moving without random command changes.
Internal route
Use these links to move from discovery to setup, troubleshooting, model routing or security without restarting the search journey.
Odysseus setup triage tool for routing Windows, Mac, Linux, Docker, login, Ollama, port, mobile and security blockers to the right next step.
Command generator for Odysseus install routes with official-source reminders and safety notes.
Odysseus troubleshooting hub for ports, Docker health, Ollama, login, Python and GPU runtime failures.
Vote after you pick the next step. It helps prioritize pages that actually unblock Odysseus AI setup work.
No vote saved in this browser.
FAQ
These answers target the common follow-up questions behind the current search query.
Yes, but the route still needs Git, Python or Docker, enough disk space and a model plan such as Ollama or an API provider.
Not for the workspace itself. A GPU matters when you expect fast local model inference or larger model serving.
Yes, if you choose an OpenAI-compatible API or another supported model provider. Ollama is only one common local path.
Sources
Use these current sources to cross-check videos, community claims and official setup details before changing your machine.
Use current official notes for Python version, Docker, native OS routes, ports and model-provider expectations.
Useful after Odysseus itself works and the remaining blocker is local model serving or GPU discovery.
No purchase is required to read this guide, use the tools or verify the official source. Use the free guide and diagnostics first; paid help is only for a named blocker where saved time is worth the cost.