Generative interfaces
InterfaceInteractive 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.
The Korazos roadmap
From individual proofs of concept to one integrated operating layer. This is where we are, and what comes next.
Demonstrated
Working components that establish the core ideas. These are prototypes, not a released end-to-end product.
Interactive UI and layout-morphing prototypes exploring how a workspace can change with a task.
Connect the adaptive interface to persistent task context and execution.
Python execution in disposable Docker containers with networking disabled.
This demonstrates container-based isolation. It is not a hardware-isolated microVM or a zero-risk security guarantee.
WSL-to-host operations and basic host telemetry checks explored in prototype form.
Bring the relevant host context into the runtime with explicit access boundaries.
Early schemas defining how tools expose context and actions to the runtime.
Initial schemas are not a production integration catalog. Broader connector coverage remains ahead.
Current focus
Turn the separate proofs of concept into a coherent experience. Integration comes before adding more features.
Bringing the canvas, task context, connectors, and execution environment together in a Tauri/Rust desktop layer.
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.
Carry the task from the composer into an adaptive interface and through bounded tool execution.
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.
Planned
A focused private alpha with developers and technical founders, built around real workflows.
Find where an adaptive workspace genuinely improves the work, and where familiar tools still work better.
Look for repeat use on real tasks. Measure completion, failures, manual corrections, and whether users choose Korazos again. A compelling demonstration is not enough.
Visible permissions, stronger isolation, reviewable actions, audit trails, and recovery controls.
These controls need further implementation and testing. Automatic rollback and cryptographically signed execution receipts are not claimed as working today.
Expand connectors around validated tasks, then measure reliability, performance, and workflow benefits.
Measured results with a clear method. No assumed latency, hours saved, or productivity multiplier.
Long-term direction
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 buildThis roadmap describes founder-reported progress, not a live tracker or a delivery commitment. Demonstrated means prototyped; planned work may change as we learn.