- Developers who want a self-hosted all-in-one AI workspace with full data privacy
- Users who run local models and need a polished UI for chat, agents, and tools
- Teams evaluating self-hosted alternatives to cloud AI workspaces like ChatGPT or Claude
Agents
Odysseus
Self-hosted AI workspace for chat, autonomous agents, deep research, email, documents, and more — local-first, privacy-first, no telemetry.
36K Stars
4.3K Forks
MIT License
pewdiepie-archdaemon Maintainer
2026-06-03 Verified
Overview
What is Odysseus?
Odysseus is a self-hosted AI workspace that unifies chat, autonomous agents, deep research, email triage, document editing, calendar, notes, memory, and model serving into a single local-first interface. It runs on your own hardware against your own endpoints — no telemetry, no cloud dependency, and full data privacy.
All-in-one self-hosted workspace
Odysseus combines chat, autonomous agents, deep research, email triage, document editing, calendar, notes, memory, model serving, and more in a single application.
Most AI tools require stitching together multiple services. Odysseus gives you everything in one local-first package without sending data to the cloud.Local-first with privacy by default
Runs entirely on your hardware against your own model endpoints. No telemetry, no cloud dependency, and no third-party access to your conversations or data.
Privacy is the default architecture, not an afterthought or a premium feature.Agent loop built on opencode with MCP
Odysseus's agent system is built on opencode, with full MCP tool support, web browsing, file access, shell commands, and persistent memory.
The agent isn't just a chat wrapper — it can take real actions, use tools, and evolve its own skills over time. Use cases
What Odysseus is built for
01
All-in-one local AI workspace
Run chat, agents, email, documents, and calendar from a single self-hosted dashboard connected to your own models.
02
Autonomous agent workflows
Give the agent tools (MCP, shell, files, web) and let it plan and execute multi-step tasks autonomously.
03
Local model management and serving
Use the Cookbook to scan your hardware, discover suitable models, download them, and serve them — all from the UI.
04
Privacy-preserving email assistant
Connect your IMAP/SMTP accounts for AI-powered email triage, summaries, and draft replies — without sending email data to third-party services.
Quick start
Get started in seconds
$
git clone https://github.com/pewdiepie-archdaemon/odysseus.git && cd odysseus && docker compose up -d --build $
git clone https://github.com/pewdiepie-archdaemon/odysseus.git && cd odysseus && python3 -m venv venv && source venv/bin/activate && pip install -r requirements.txt && python setup.py && python -m uvicorn app:app --host 127.0.0.1 --port 7000 $
git clone https://github.com/pewdiepie-archdaemon/odysseus.git && cd odysseus && ./start-macos.sh Comparison
How it stacks up
Choose Odysseus for a complete self-hosted workspace
vs cloud AI workspacesChatGPT and Claude offer polished hosted experiences. Odysseus gives you the same breadth of features — chat, agents, research, tools — but runs entirely on your own hardware with no telemetry.
Choose Odysseus for breadth over specialization
vs single-purpose toolsDedicated coding agents like Aider or OpenHands go deeper on code tasks. Odysseus is broader — it handles email, calendar, documents, and model management alongside agent capabilities.
FAQ
Frequently asked questions
What should I check before using Odysseus?
Start with one safe workflow for Odysseus. Inspect official setup instructions, required credentials, execution logs, approval points, and failure recovery before expanding from a sandbox task into production automation.
Is Odysseus open source?
Odysseus is listed with MIT based on the official source links in this profile. Re-check the repository, model card, or docs before production use.
Who should evaluate Odysseus?
Odysseus is most worth evaluating for developers who want a self-hosted all-in-one AI workspace with full data privacy.
Does Odysseus require a GPU?
No. Odysseus connects to any LLM endpoint — local or remote. The Cookbook model serving is optional and GPU-dependent. You can use it with API providers like OpenAI, Anthropic, or OpenRouter without any local GPU.
How does Odysseus compare to running separate tools?
Odysseus combines chat, agents, deep research, email, documents, calendar, and model management into one application. The tradeoff is breadth over specialization — dedicated tools may go deeper on specific tasks.
Decision brief
JSON
Should you use Odysseus?
- Users who prefer managed cloud services with no self-hosting overhead
- Non-technical users unwilling to manage Docker or Python runtimes
- Verified 2026-06-03
- License: MIT
- Repo: pewdiepie-archdaemon/odysseus
- Open-source signal
Deployment
self hosted, cloud
Permission surface
memory, external services
Decision signals
Self-hostable, MCP
Agent packet
Structured decision data for Odysseus
This packet is the compact machine-readable view agents should use before following source links or taking action.
Capabilities
mcp, workflow orchestration
Constraints
open source, self hosted, mcp compatible
Deployment
self hosted, cloud
Permission surface
memory, external services
Recommended workflows
Coding agent workflow, Local or private AI stack
Overview
What Odysseus does
What it is
Odysseus is an open agent resource to evaluate by action surface: what software it can operate, which tools or browser steps it touches, and how much supervision it needs before it can run real work.
Why it matters
The self-hosted AI space has many single-purpose tools — a chat UI here, an agent framework there, a model server somewhere else. Odysseus combines them into a cohesive workspace, making it practical to run your entire AI stack locally without stitching together disparate services.
How to evaluate it
Start with one safe workflow for Odysseus. Inspect official setup instructions, required credentials, execution logs, approval points, and failure recovery before expanding from a sandbox task into production automation.
Facts
Known metadata and operating surface
These fields are separated from editorial interpretation so agents can reason over facts and missing checks.
Resource type agent
Category Agents
Maturity active
Difficulty Unknown
License MIT
Pricing open source
Verified 2026-06-03
Source confidence high
Risk level moderate
Fit matrix
Where Odysseus fits in an agent stack
strong
Coding agent workflow
Odysseus has multiple signals for coding agent workflow, including matching tags, capabilities, category, or positioning.
- Run a small repository change and inspect the diff, tests, and rollback path.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
strong
Local or private AI stack
Odysseus has multiple signals for local or private ai stack, including matching tags, capabilities, category, or positioning.
- Verify hardware requirements, data path, storage, and whether all calls stay in your environment.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
partial
Connector or protocol layer
Odysseus has at least one signal for connector or protocol layer, but should be checked against a real task before adoption.
- Connect one low-risk service, then inspect schemas, auth scope, errors, and logs.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
partial
Evaluation and observability
Odysseus has at least one signal for evaluation and observability, but should be checked against a real task before adoption.
- Add one repeatable test case and confirm results can run again in review or CI.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
partial
Memory or RAG workflow
Odysseus has at least one signal for memory or rag workflow, but should be checked against a real task before adoption.
- Create, update, retrieve, correct, and delete memory or retrieval objects with real data.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
partial
Reusable skill workflow
Odysseus has at least one signal for reusable skill workflow, but should be checked against a real task before adoption.
- Run one skill end to end and check whether it produces evidence or structured output.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
Inputs and outputs
What an agent should inspect
Likely inputs
- Repositories, files, issues, terminal output, and test results
- Documents, user facts, entities, context, or retrieval queries
- Tool schemas, API requests, service resources, and auth scopes
- Prompts, messages, documents, images, or model inputs
- Official setup instructions and a small real workflow
Likely outputs
- Diffs, commits, explanations, test results, or review notes
- Retrieved context, memory updates, graph relations, or citations
- Scores, traces, regression results, dashboards, or failure cases
- A decision on whether this resource fits the target workflow
Evidence
Sources, claims, and missing checks
Claims are marked separately from source links so future crawlers and reviewers can update them without rewriting the page.
GitHub github
Repository source for code, license, issues, releases, and implementation details.
Homepage homepageOfficial or project-controlled source for this resource profile.
Odysseus is listed as open source.
License metadata: MITOdysseus has a recorded GitHub repository: pewdiepie-archdaemon/odysseus.
Resource facts and GitHub source link.Odysseus supports these recorded deployment modes: self hosted, cloud.
OpenAgent decision signal metadata.Odysseus is tagged with mcp, workflow orchestration capabilities.
OpenAgent capability taxonomy.- Dedicated docs link is missing.
- Repository freshness has not been recorded.
Next action
How to start evaluating Odysseus
Inspect repository
Check license, recent activity, issues, examples, and security-sensitive code paths.
Open sourceOpen Homepage
Start from the official source before adopting third-party instructions.
Open sourceInstall with Docker (recommended)
Clone the repository and start Odysseus with Docker. Open http://localhost:7000 when containers are healthy.
git clone https://github.com/pewdiepie-archdaemon/odysseus.git && cd odysseus && docker compose up -d --buildInstall natively on Linux/macOS
Native install requires Python 3.11+. The Cookbook feature also needs tmux for background model operations.
git clone https://github.com/pewdiepie-archdaemon/odysseus.git && cd odysseus && python3 -m venv venv && source venv/bin/activate && pip install -r requirements.txt && python setup.py && python -m uvicorn app:app --host 127.0.0.1 --port 7000 Compare
Alternatives and nearby resources
Use related resources to compare category fit, license, deployment model, and first-workflow behavior.
FAQ
Common questions about Odysseus
What should I check before using Odysseus?
Start with one safe workflow for Odysseus. Inspect official setup instructions, required credentials, execution logs, approval points, and failure recovery before expanding from a sandbox task into production automation.
Is Odysseus open source?
Odysseus is listed with MIT based on the official source links in this profile. Re-check the repository, model card, or docs before production use.
Who should evaluate Odysseus?
Odysseus is most worth evaluating for developers who want a self-hosted all-in-one AI workspace with full data privacy.
Does Odysseus require a GPU?
No. Odysseus connects to any LLM endpoint — local or remote. The Cookbook model serving is optional and GPU-dependent. You can use it with API providers like OpenAI, Anthropic, or OpenRouter without any local GPU.
How does Odysseus compare to running separate tools?
Odysseus combines chat, agents, deep research, email, documents, calendar, and model management into one application. The tradeoff is breadth over specialization — dedicated tools may go deeper on specific tasks.