odysseus-dev/odysseus

Self-hosted AI workspace.

View on GitHub ↗Jump to charts ↓Open shareable report →

odysseus-dev/odysseus has 93k+ stars and 1.5k+ forks on GitHub, is written in Python, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on August 30th, 2026
Created on May 31st, 2026
Open Issues & Pull Requests: 1,470 (+1)
GitHub issues: Enabled
Number of forks: 1,663
Total Stargazers: 93,865 (+10)
Total Subscribers: 507 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.5 hours
Mean response time: 6.7 days
90th percentile: 12.2 days
Tracked items: 1,625

Maintainer activity

12 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 89% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "needs more info" is answered fastest, typically in under an hour, while "p1" waits about 31 hours. Almost all tracked open issues have seen activity in the last three months. Only 52% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,126
New in 7 days: 36
Closed in 7 days: 60
Avg open age: 85 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 27
Closed in 7 days: 59
Comments in 7 days: 9
Events in 7 days: 47

Top labels

  • ready for review (1,593)
  • bug (764)
  • p2 (581)
  • enhancement (463)
  • p3 (415)
  • provider (135)
  • needs-validation (123)
  • p1 (89)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Odysseus is a self-hosted AI workspace that integrates chat, agents, research, documents, email, notes, and calendar functionality with support for local and API-based models.

The tool addresses the need for a unified, privacy-preserving environment where users can run AI workflows without relying on external services. It combines multiple capabilities—chat with local or API models, multi-step web research with source reading, side-by-side model comparison, a writing-first document editor with AI assistance, email management with IMAP/SMTP, task scheduling, and calendar synchronization—into a single self-hosted application. The workspace supports Model Context Protocol (MCP), shell execution, file handling, and skill-based extensibility, allowing users to build custom agent workflows.

Odysseus suits developers and organizations prioritizing data privacy and control over their AI infrastructure. It works well for teams wanting to consolidate multiple AI tools into one interface, those experimenting with local model serving, and users who need email integration alongside AI capabilities. The project emphasizes hardware-aware model recommendations and serves as both a chat interface and a research platform. The setup guide covers native installs, GPU configuration, and deployment across Windows, macOS, and Linux, with Docker Compose as the default deployment method. The README distinguishes the tool by highlighting its writing-first document editor, deep research capabilities with multi-step workflows, and integrated email triage rather than comparing it directly to other platforms.

The project maintains two branches with different stability profiles, with the dev branch receiving changes first and main offering a more curated experience. Development activity shows responsiveness to fresh-install testing and provider setup issues, with the roadmap and contributing guide indicating ongoing refinement of mobile interfaces, editor polish, and documentation. The maintainers actively solicit help on focused areas including small refactors and setup-related bugs, suggesting a project in active iteration rather than maintenance mode.