---
title: Roadmap
description: Implemented milestones and deliberately deferred Omarchy Forge work.
---

# Roadmap



## Implemented [#implemented]

1. Private repository foundation and upstream contract notes.
2. Bar-widget scaffolder with deterministic golden tests.
3. Shared check engine, machine reports, and local doctor.
4. Checksum-verifying GitHub Action and release pipeline infrastructure.
5. Documentation website source with complete initial navigation.
6. Private Handoff reference-plugin MVP with reviewed local persistence and
   Omarchy 4 live verification.
7. Public Forge `v0.1.0` release with checksum-verified Linux `amd64` and
   `arm64` archives.
8. First Milestone 6 increment: a trusted, one-shot `omaforge dev` entry point
   for the generated isolated Quickshell harness.
9. Isolated fictional ready, empty, and error state simulation through
   `omaforge dev --state`.
10. Deterministic plugin-only PNG capture without desktop screen copying.
11. Isolated file-watching development sessions with clean cancellation.
12. Public Forge `v0.2.0` release with the completed trusted local visual
    development workflow.
13. Public Forge `v0.3.0` release with provider-neutral
    `omaforge init --agent-ready` scaffolding, a structured specification,
    human-controlled readiness gate, and project-scoped agent safety contract.

## Handoff status [#handoff-status]

Handoff can pin a Git project, save one next-step note, show branch and commit
context, and open the project in a terminal. It lives in a separate private
repository. Its private `v0.1.0` source release passed an exact-tag Omarchy
installation and cleanup check. It remains unannounced, absent from
marketplaces, and not installed for ongoing use.

## Later [#later]

* A service-plus-widget template only after Omarchy documents a stable
  third-party service-access contract or a second independent plugin proves a
  reusable shape.
* Any Handoff marketplace submission, public announcement, visibility change,
  or ongoing local installation, each only with separate explicit approval.
* Production deployment and custom-domain connection are complete at
  `www.omarchyforge.com`.
* Additional templates only after the first template is proven.
* Compatibility matrices and editor integration after real demand.

Accounts, authentication, databases, hosted plugin execution, telemetry, and a
cloud marketplace are not planned MVP scope.


---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)