Roadmap / Help Wanted

Odysseus is an evolving, self-hosted AI workspace. This roadmap highlights where improvements and contributions are most useful, from reliability and maintainability to product capabilities.

Note

Direction, not a release schedule. This page is not a complete issue backlog or a promise to deliver every proposal. Implementation scope and priority are coordinated through existing issues, pull requests, and the project's feature proposal process.

At a glance

Area	Direction	Coordination
Stabilization	Reliability, CI, fresh installs, security, and integrations	Stabilization & Modularization milestone
Modularization	Clearer module ownership, safer changes, and contributor onboarding	Canonical tracker #4071
Agent runtime	Active Harness V2 development, with a narrow temporary change freeze	Coordination in #4071
Product improvements	Local models, research, frontend experience, and operations	Issues and feature proposals

Jump to: Stabilization · Modularization · AI and local models · Frontend · Backend · Contributing

Stabilization and reliability

Priority: Make Odysseus dependable across installations, platforms, providers, and supported hardware.

Workstream	What needs improvement	Tracking
CI and validation	Exact-revision validation, meaningful regression coverage, and release confidence	#5932, #7109
Test quality	Deterministic tests, isolation, focused execution, and maintainable test structure	#2523, testing standard
Fresh installations	Smoke tests for Linux, macOS, Windows, WSL, and Docker; baseline startup and graceful degradation	#3968
Email integration	Remaining Google OAuth regressions, account isolation, and cross-provider reliability	#5637
Storage integrity	Upload payload growth, indexing, and attachment/file lifecycle	#4889

Additional reliability priorities:

Cookbook: Improve model installation, dependency management, hardware detection, and model serving across operating systems, GPUs, drivers, shells, Python environments, and supported backends.
Security: Keep strengthening authorization, administrative tools, agent tool execution, prompt-injection boundaries, filesystem access, and untrusted-content handling.
Integrations and degraded states: Audit supported providers and optional services, including ChromaDB, SearXNG, email, and ntfy. Make failures observable and nonessential outages predictable.

Tip

Start with an existing, reproducible issue. The Stabilization & Modularization milestone is a curated work queue, not an invitation to implement every item in this roadmap without coordination.

Modularization and maintainability

The goal is clearer responsibility boundaries and safer development, not smaller files for their own sake. Changes should preserve behavior, compatibility, and relevant runtime contracts.

Area	Current foundation	Remaining opportunities
CSS	The former `static/style.css` has been split into ordered files under `static/css/`	Improve ownership while preserving the cascade, themes, and responsive layouts
Tools	Substantial tool-domain extraction has landed	Clarify remaining ownership and preserve compatibility through the existing tool interfaces
Frontend	Existing feature modules remain in use	Decompose large document, gallery, settings, calendar, and other UI modules around coherent behavior
Backend	Domain-specific routes and services already exist	Identify safe boundaries in Cookbook routes, persistence, and other tightly coupled modules
Tests	Taxonomy, focused execution, and structural improvements exist	Align fixtures, helpers, and regression coverage with implementation boundaries
UI infrastructure	Targeted cleanup is underway	Consolidate tour scaffolding, modal/window positioning, responsive overrides, and obsolete paths

Canonical coordination: Codebase modularization and contributor onboarding, #4071.

Important

Cohesive work is more important than a small line count. A larger PR may be appropriate for one well-defined decomposition when several smaller PRs would create avoidable conflicts or integration overhead. Coordinate the boundary, avoid unrelated work, and supply regression and runtime evidence. See CONTRIBUTING.md.

Agent runtime and Harness V2

Harness V2 is under active development.

Caution

Temporary agent-runtime freeze. Unrelated changes to src/agent_loop.py and closely related execution, orchestration, authorization, and context contracts must be coordinated with maintainers while Harness V2 is developed and validated.

This does not freeze unrelated application modules. Urgent bug reports and security issues remain welcome. No release date is implied.

AI, local models, and research

These are areas of product interest, not commitments to a specific implementation or delivery order. Follow normal issue triage and product-decision requirements.

Direction	Opportunity
Smaller-model agents	Reduce unnecessary prompt, tool-schema, skill, memory, and document context overhead; improve tool selection for constrained context windows
Cookbook and SGLang	Improve installation and serving across relevant hardware, operating systems, and deployment methods
Model discovery	Rank models by architecture, quantization, RAM/VRAM fit, backend support, multimodal requirements, and expected reliability
Deep Research presets	Explore suitable model and parameter configurations for small, medium, and large local systems
Actionable diagnostics	Expose command output, logs, and next steps for failed downloads, dependencies, preflights, and serving jobs
Speculative decoding	Investigate compatible draft-model configurations and evaluate end-to-end correctness and time to success
Provider setup	Improve endpoint discovery, capability checks, and setup for supported local and hosted providers

Frontend and user experience

Editors and files: Improve document/file editing, window behavior, save/export flows, and image-editing reliability.
Notes and Todos: Expand agent-assisted reading, updates, summarization, and turning information into tasks.
Mobile: Improve gallery/editor usability, model setup, and responsive behavior.
Accessibility: Strengthen keyboard navigation, focus states, contrast, and reduced-motion support.
First run: Improve setup, hints, empty states, error messages, and onboarding tours without duplicate guidance.
Self-hosting: Reduce unnecessary external asset dependencies where practical for offline operation.

Backend and operations

Email performance: Measure fetching, searching, body and attachment loading, caching, sending, and frontend refresh behavior before optimizing.
Provider reliability: Expand regression coverage for setup, endpoint probing, and degraded-service behavior.
Task scheduling: Improve defaults, reliability, and operational visibility.
Data recovery: Improve backup and restore guidance and workflows for persistent data.
Administrative security: Review privileged capabilities and sensitive integrations against their authorization boundaries.

Not a current priority

Additional themes without a demonstrated product need.
Broad rewrites or framework migrations without clear, measurable value.
Changes undertaken solely to reduce file counts.
Uncoordinated changes to temporarily frozen agent-runtime contracts.

Contributing

Read CONTRIBUTING.md and search existing issues and PRs.
Coordinate modularization through #4071 and active stabilization work through the milestone.
Use the repository's issue and PR templates and target dev.
Include relevant tests, runtime evidence, and screenshots or recordings for visual changes.

Note

Product-direction or difficult-to-reverse changes follow the feature proposal process. Report security vulnerabilities privately through SECURITY.md, never in a public issue.

9.4 KiB Raw Blame History