Repository navigation
Odysseus Development Update: Stabilization, Modularization & Harness V2 #7189
Replies: 2 comments
Notes rework: please avoid overlapping Notes changes for nowFollowing up on the stabilization work above, a heads-up on Notes. I'm rebuilding the Notes feature on current
It will land as a series of focused PRs. A tracker issue with the full plan will follow once the rework is fully tested, and I'll link it here. Important Notes is under a soft freeze for overlapping changes while the rework is prepared for review. Please hold off on new features, refactors and file moves in the areas below. Bug fixes and security fixes are still welcome as usual. This is not a freeze on Notes contributions. It ends when the rework has landed, and I'll update this thread at each step.
Existing Notes PRs are not affected. They'll still be reviewed on their own merits. I'll review the open ones myself, and anything still relevant once the rework lands I'll rebase onto it, crediting the original author, so nobody has to redo their work. If your PR overlaps and you'd rather I take it over sooner, say so on the PR. If you're about to start something in Notes, ping me here first. It saves both of us a painful rebase. |
Document Editor: Decomposition in ProgressImportant The modernization of Following an architectural review of the existing ~17,650-line module, I've started a coordinated effort to simplify its implementation, establish clearer responsibility boundaries, and improve correctness and performance. The work will be consolidated into one PR targeting What we're working on
The goal is not simply to split a large file into smaller ones. We want to reduce actual complexity, improve maintainability, and make future contributions easier to develop, test, and review. Validation & integrationThe modernization is being developed incrementally, with regression coverage and integration checks at each stage. Before opening the PR, we'll complete automated and browser validation, review the integrated implementation, and perform manual functional testing. Note Coordination and scope
If you're working on changes that overlap with the Document Editor, please coordinate here to avoid conflicting implementations. Status: In progress | PR: Not yet opened | Target: I'll update this discussion with the tracking issue and PR once they're available. |
Uh oh!
There was an error while loading. Please reload this page.
The October pre-Ajax migration is complete, and we've been working behind the scenes to make Odysseus more stable, maintainable, and easier to contribute to.
Our focus now is on reducing architectural complexity, improving the review process, and preparing the next generation of the agent runtime.
Important
Harness V2 is underway, with a release targeted in the next few days.
The agent runtime, including
src/agent_loop.pyand closely related execution contracts, is temporarily frozen for unrelated changes while we complete integration and validation.This is not a repository-wide freeze. All other areas remain open for contributions. Urgent runtime bugs and security issues can still be raised and coordinated with maintainers.
Progress so far
Since the migration landed in
devthrough #6503, several improvements have already been integrated:tool_implementations.pymonolith has been split into dedicated tool-domain modules, leaving a small compatibility layer.static/css/.We've also begun reviewing the existing issue and PR backlog to identify overlapping work, outdated reports, and changes that still need attention.
Modularization: what remains
Several large modules still combine responsibilities that would be easier to maintain, test, and review independently.
The following reflects the current state of public
devand identified decomposition PRs as of November 11, 2026.src/agent_loop.pydevstatic/js/document.jsstatic/js/galleryEditor.jscookbookServe.js,cookbookRunning.js,cookbook_routes.pystatic/js/settings.jsstatic/js/calendar.jscore/database.pyroutes/auth_routes.py,routes/session_routes.pyThe PR column identifies relevant decomposition work, not every open bug fix or feature affecting these modules. Existing PRs still require review and may need updates against current
dev.The objective is not simply to reduce file sizes. We want clearer responsibilities, fewer merge conflicts, better test isolation, and code that's easier for contributors and maintainers to work with.
See #4071 for the broader maintainability effort.
A practical exception for larger PRs
We normally prefer small, focused contributions. However, we're explicitly open to larger PRs when they address a well-scoped monolith decomposition.
Some architectural changes are difficult to split into many small PRs without introducing temporary complexity, repeated conflicts, or additional review overhead.
Tip
A larger PR is welcome when the scope justifies it.
For monolith decomposition, we're looking for:
Larger scope does not reduce the review requirements. It makes clear boundaries and validation even more important.
We want to remove unnecessary barriers to improving the architecture, not encourage broad, unreviewable rewrites.
Documentation and backlog cleanup
Some of our documentation and trackers no longer accurately reflect the current implementation.
We'll be reviewing and updating:
ROADMAP.md: Remove completed or outdated targets and reflect current priorities.CONTRIBUTING.md: Clarify the expectations for coordinated, larger decomposition PRs.This will happen alongside the ongoing backlog review, with the goal of making it easier to find useful work and understand what's already being developed.
Our priority over the coming weeks is to make issue triage, PR reviews, and integration more consistent and effective, while providing contributors with a clearer and more maintainable codebase.
To our contributors
A special thank you to everyone who has submitted PRs, reported bugs, tested changes, reviewed code, or helped improve Odysseus.
We know that large, tightly coupled modules, overlapping work, and a growing review backlog can make contributing more difficult than it should be.
A significant part of our current effort is about addressing those problems, so we can provide a better platform for your contributions and tackle issues and PRs more effectively in the weeks ahead.
There's still plenty of work to do, and your contributions remain an essential part of moving Odysseus forward.
Thank you for helping build it.
All reactions