What changed—and why it matters.

A month-by-month view of Oduflow's evolution, distilled from the release notes into the value delivered to Odoo development teams.

View full release notes on GitHub

Product timeline

Newest first. Every linked version opens its complete technical release notes on GitHub.

  1. 8 releases

    Teams, agents, and secure production routing

    Oduflow grew from an environment manager into a secure, multi-team development platform that can host coding agents alongside the infrastructure they operate.

    • Run an isolated coding agent for each team, with persistent workspaces and both terminal and browser chat interfaces.
    • Give agents scoped MCP credentials for one environment instead of exposing team-wide access or long-lived secrets.
    • Serve multiple teams safely with per-host OAuth, authenticated dashboards, hardened proxy trust, and stronger tenant boundaries.
    • Move real Odoo.sh projects more reliably with resumable uploads, Enterprise and extra-addons support, native database neutralization, and flexible template imports.
    • Expose only the service routes you intend, while dependency changes and long-lived MCP sessions now synchronize and restart predictably.

    Releases

  2. 6 releases

    Public release and a sharper daily workflow

    The public release made local development faster, operations safer, and the dashboard more comfortable for long working sessions.

    • Edit live-mounted projects directly—including non-Git folders—while Oduflow detects and applies only the changes that matter.
    • Let environments stop when idle, wake on demand, and clean themselves up without touching protected work.
    • Manage service volumes, networking, environment variables, and lifecycle operations from the same agent-native workflow.
    • Start from safer defaults with unique database credentials, host-aware PostgreSQL tuning, and clearer agent guidance.
    • Work in a redesigned, accessible dashboard with light mode, larger type, clearer status, and more useful logs.

    Releases

  3. 2 releases

    Faster setup and deeper agent control

    Getting started became nearly automatic, while agents and operators gained a broader, more dependable set of tools inside each environment.

    • Start in MCP-friendly stdio mode and let Oduflow initialize itself on first run instead of following a separate bootstrap sequence.
    • Use a larger, refined MCP toolkit with cached long-running results and clearer commands for common Odoo development work.
    • Apply configuration changes during upgrades and rebuild environments from the dashboard with current container images.
    • Operate with safer sanitization, more reliable team-aware actions, and clearer search results when diagnosing an environment.

    Releases

  4. 3 releases

    The platform foundation

    The first releases established the core promise: production-shaped Odoo environments that are fast to create, isolated by default, and controllable by people or agents.

    • Import reusable templates from running Odoo systems and create development environments without repeatedly copying full databases and filestores.
    • Keep environments separated with dedicated PostgreSQL credentials and layered database sanitization for safer production-derived data.
    • Give agents purpose-built access to files, SQL, admin recovery, repositories, and environment lifecycle operations through MCP.
    • Debug from the dashboard with interactive SQL and Odoo consoles, structured sync results, and readable colored logs.
    • Handle large dumps without memory spikes, deploy with Docker, and follow structured documentation and version-specific Odoo guides.

    Releases

Browse every release on GitHub