Now: inspect the working foundation

Open-source project roadmap / September 2026

What works now, and what we want to build together

OpenMake is an MIT-licensed AI workspace that people can run and improve together. This page separates the current release from work under discussion and longer-term direction. GitHub issues and real use help shape the order; a roadmap entry is not a release promise.

Now: inspect the working foundation

The current release connects models, agent tasks, research, tools, and saved outputs. What runs in a particular installation depends on its models, add-ons, permissions, and configuration. Use the manual for the workflow and release notes for version-specific changes.

Model and tool paths

Connect local or compatible external models and choose which configured tools a task may use.

Visible work

Follow agent tasks and research progress, review approvals, sources, and saved artifacts.

Open source

Inspect the MIT-licensed code.

NextNext: make longer work easier to trust

Next: make longer work easier to trust

These are areas for continued design and testing, not features already available in every installation. The order may change as contributors bring failures, examples, and proposals to the repository.

  1. 01

    Recovery and review

    Test restart, retry, approval, and side-effect boundaries in real agent work; make failures and recovery clearer to operators.

  2. 02

    Execution Graph

    Explore plans with explicit dependencies, outputs, permissions, and completion checks instead of relying only on a linear list of steps.

  3. 03

    Knowledge and reusable workflows

    Continue improving source-backed knowledge spaces and explore user-reviewed workflows that can be reused safely.

Proposed direction, September 2026: record → review → approve → reuse. Solid outlines identify available foundations; dashed outlines identify planned extensions. The recorder and the complete workflow are roadmap work. AI-generated conceptual illustration; select to enlarge.
NextLonger term: control across an organization

Longer term: control across an organization

A wider Agent Runtime and organizational Control Plane remain a direction, not a description of today's default install or a promised commercial edition. The open-source workspace is the foundation; policies, budgets, audit, and deployment controls need their own evidence and design.

Organization boundaries

Define how projects, roles, data access, and external connections should be governed across teams.

Operational evidence

Make costs, approvals, execution history, and failures inspectable without claiming controls that have not been verified.

NextHelp decide what moves forward

Help decide what moves forward

An issue with a reproducible case or a proposed workflow is more useful than a feature name alone. Describe the task, the environment, what happened, and what a successful result would look like. We review scope in public before large changes.