Odysseus AI Login Help
Last updated: June 6, 2026
If you can open Odysseus but cannot log in, do not reset data first. Find the generated admin password, confirm the install route you used, and check that you are looking at the right server.
Quick answer
The first username is usually admin. The first password is generated on first boot. For Docker installs, run:
docker compose logs odysseus | grep -i password1. Make Sure the Web App Is Actually Running
Login cannot work if you are staring at a cached page, wrong port, or a crashed container. Check the service first.
docker compose ps
docker compose logs --tail 80 odysseusIf port 7000 does not respond, use the localhost:7000 checklist before changing credentials.
2. Find the Password for Your Install Route
Docker Compose
docker compose logs odysseus | grep -i passwordRun this from the same Odysseus repository directory where you started Docker.
Native macOS or Linux
# Check the terminal where you ran setup.py, uvicorn, or start-macos.sh
# Search recent app logs if you redirected output.The generated password prints during first boot in the native terminal output.
3. Check Username Overrides
The official README says the first admin account is admin unless you set an override before first boot. Check your local environment file without sharing its values.
# Do not paste secrets into chat.
grep -n "ODYSSEUS_ADMIN_USER\|ODYSSEUS_ADMIN_PASSWORD\|AUTH_ENABLED" .env .env.local 2>/dev/nullIf the account already exists, changing the preseed variable later may not change the stored account. Change credentials inside Settings after a successful login.
4. Fix Browser Session Problems
Use the exact local URL
Docker usually opens http://localhost:7000. Native macOS currently launches at http://127.0.0.1:7860.
Clear the stale session
If you changed bind, host, or proxy settings, try a private window before resetting the app.
Check the install directory
Multiple cloned odysseus folders can point at different databases and different first passwords.
5. Do Not Reset Volumes Casually
Commands such as docker compose down -v can delete stored data. Use them only when you intentionally want a clean install and have backed up anything you care about.
Do not reset volumes just because login failed. First confirm logs, username, URL, and browser session.
6. Verify Against Official Docs
Authentication defaults and recovery paths can change. Check the official GitHub repository before deleting any data or exposing the app beyond localhost.
FAQ
What is the default Odysseus AI login username?
The default username is admin unless ODYSSEUS_ADMIN_USER was set before the first boot.
Where is the first Odysseus AI password?
Odysseus generates a temporary admin password on first setup and prints it in the terminal. For Docker installs, the same line appears in docker compose logs odysseus.
Can I set my own Odysseus admin password?
Yes, but do it before first boot by setting ODYSSEUS_ADMIN_PASSWORD. After first login, change the password inside Settings instead of deleting data files.
Why does localhost open but login still fails?
You may be using the wrong generated password, a stale browser session, a changed admin username, or a different install directory than the one that created the account.
Should I disable authentication for testing?
Only for private local development if the official docs support that path. Keep AUTH_ENABLED=true for anything reachable from another device, reverse proxy, VPN, or public network.
Installation support
Need hands-on installation support?
Setup Helper is the self-service planner. Installation Support is for users who want a human to review the route, diagnose logs, or get Odysseus running. We confirm scope and price before any payment.
Related Guides
Find the first generated password and change it safely after login.
Debug the web UI port before assuming login is broken.
Start the stack, check logs, and confirm the app container is healthy.
Verify the official source before installing or logging into any site.
Understand why Odysseus should be treated like an admin console.
Return to the main setup issue checklist.