Known Limits
An honest list of what Vinaya genuinely doesn’t do yet. Every claim below is checked against this repo’s current state, not assumed from a roadmap.
No CLI commands exist yet
vinaya-cli-v1 is entirely undispatched — all seven tasks (init, check, doctor, upgrade, eject, waiver, pr/issue writes) are open with no code merged. There is no apps/vinaya/cli in this repo today.
Verified: milestone vinaya-cli-v1, issues #381–#387, all open, 0 closed (checked 2026-07-08).
Vinaya Studio doesn’t exist yet either
Studio has no code in this repo yet (same undispatched state as the CLI). When it ships, v1.0 is local-only — no deployed or hosted instance, and no committed date for one beyond "deferred."
Verified against D-101 (Studio deployment roadmap) — Phase 1 is local-only; Phase 3 is undated.
No Windows support
v1.0 targets macOS and Linux only. Windows support is deferred, with no committed ship date.
Verified against D-104 (v1.0 scope) — Node ≥ 20, macOS + Linux; Windows explicitly deferred.
No editor extension
The only way to use Vinaya is the CLI (once it exists). There is no VS Code, JetBrains, or other editor plugin planned for v1.0.
Verified against D-086 (Vinaya surfaces) — no editor extension in scope.
No GitHub App / org-wide install
Vinaya acts through your own git and gh credentials — it does not install as a GitHub App, and there's no one-click, org-wide rollout.
Verified against D-086 (Vinaya surfaces) — GitHub App install is deferred.