OpenVCS GitHub

OpenVCS Roadmap

Roadmap

What OpenVCS is tightening now, what comes next, and what waits until the foundation earns it.

OpenVCS is taking the disciplined route: stabilize the Git workflow, settle the extension layer, then validate broader backend support.

01 Now Current focus

Make daily Git work dependable

OpenVCS already covers real Git workflows. The immediate job is making those workflows feel solid every day.

Goals

  • Tighten commits, branches, stash, sync, and conflict handling.
  • Keep repo state, progress, and logs clear when operations get messy.
  • Continue polishing keyboard paths, responsiveness, and core desktop flow.
02 Next Platform foundation

Settle the extension layer

Plugins and themes are part of the product direction, but they need a cleaner foundation before they can carry more weight.

Goals

  • Stabilize plugin sync, runtime behavior, and packaging expectations.
  • Make themes and plugin settings feel native inside the client.
  • Keep customization flexible without bloating the core app.
03 Later Future validation

Prove the multi-VCS model

More backends are the long-term point, but they only matter if the client is ready for them.

Goals

  • Validate the backend abstraction with at least one additional VCS.
  • Expand carefully without weakening the Git workflow that ships first.
  • Use real implementation experience to decide what should generalize.

How priorities move

The order is deliberate.

Priorities can move with feedback and implementation reality, but the direction stays the same: stabilize first, extend second, expand third.

View open issues Project repository