The Korazos roadmap

Building the
AI-native runtime.

From individual proofs of concept to one integrated operating layer. This is where we are, and what comes next.

Private alpha in developmentUpdated October 28, 2026
01

Demonstrated

Prove the
foundations.

Working components that establish the core ideas. These are prototypes, not a released end-to-end product.

Generative interfaces

Interface

Interactive UI and layout-morphing prototypes exploring how a workspace can change with a task.

Next checkpoint

Connect the adaptive interface to persistent task context and execution.

Isolated Python execution

Compute

Python execution in disposable Docker containers with networking disabled.

Scope and boundary

This demonstrates container-based isolation. It is not a hardware-isolated microVM or a zero-risk security guarantee.

Host operations

System context

WSL-to-host operations and basic host telemetry checks explored in prototype form.

Next checkpoint

Bring the relevant host context into the runtime with explicit access boundaries.

Initial MCP schemas

Tool interfaces

Early schemas defining how tools expose context and actions to the runtime.

Scope and boundary

Initial schemas are not a production integration catalog. Broader connector coverage remains ahead.

02

Current focus

Connect the
runtime.

Turn the separate proofs of concept into a coherent experience. Integration comes before adding more features.

The desktop operating layer

In progress

Bringing the canvas, task context, connectors, and execution environment together in a Tauri/Rust desktop layer.

Next checkpoint

A developer can start a task, work in a purpose-built interface, inspect a sandbox result, and return to the same context. Windows/WSL is the initial development environment.

The intent-to-action flow

In progress

Carry the task from the composer into an adaptive interface and through bounded tool execution.

Next checkpoint

Demonstrate one complete task flow: intent, workspace assembly, isolated execution, and explicit review before any external change. Keep its boundaries and limitations visible.

This is the work happening now.
No public release date has been announced.

03

Planned

Put it to work.
Learn from it.

A focused private alpha with developers and technical founders, built around real workflows.

Developer workflow testing

Private alpha

Find where an adaptive workspace genuinely improves the work, and where familiar tools still work better.

What we will look for

Look for repeat use on real tasks. Measure completion, failures, manual corrections, and whether users choose Korazos again. A compelling demonstration is not enough.

Permissions and traceability

Trust

Visible permissions, stronger isolation, reviewable actions, audit trails, and recovery controls.

Scope and boundary

These controls need further implementation and testing. Automatic rollback and cryptographically signed execution receipts are not claimed as working today.

Connections and measurement

Evidence

Expand connectors around validated tasks, then measure reliability, performance, and workflow benefits.

What we will publish

Measured results with a clear method. No assumed latency, hours saved, or productivity multiplier.

04

Long-term direction

An operating system
organized around intent.

Context, interface, and execution as one experience. The first delivery is a desktop runtime on an existing operating system. The longer-term ambition is an AI-native OS, not another layer of disconnected apps.

The belief behind the build

This roadmap describes founder-reported progress, not a live tracker or a delivery commitment. Demonstrated means prototyped; planned work may change as we learn.

Bring us a task worth building for.

Connect

Private alpha in development

Follow our prototype and alpha progress.

© 2026 Korazos. All rights reserved.