Product Status
Current stage
Section titled “Current stage”Srijika is in public alpha. The website, documentation, and versioned npm packages are public, while the implementation repository remains private. The primary onboarding path is CLI first; Desktop Studio is an optional visual surface over the same project contract.
Available now
Section titled “Available now”| Capability | Current behavior |
|---|---|
| Public npm setup | npm create srijika@latest my-app creates and validates a pinned application without requiring Desktop Studio. |
| Project scaffolding | Creates a complete pinned React 19 workspace without overwriting an existing destination. |
| Canonical UI source | Restricted, typed source ending in the resolved UI suffix (default .ui.tsx) is the only persisted UI authority. |
| Compiler | Parses without executing arbitrary project code and emits diagnostics, source spans, quick fixes, and a derived UiDocument. |
| Project Explorer | Indexes real project files while excluding generated and vendor directories. |
| Workbench | Keeps source selection, UI Nodes, Inspector, diagnostics, and preview aligned. |
| Failure behavior | Retains a visibly stale last-good preview when current source is invalid. |
| External editing | Opens validated project, file, and node locations directly in VS Code. |
| Managed application | Synchronizes pinned dependencies and runs or builds the real Vite app. |
| Language support | Reuses the same compiler diagnostics and fixes in the Srijika VS Code extension. |
| Migration dashboard | Selects an immutable React source and bounded target, then resumes the shared migration session from VS Code. |
| Architecture graph | Shows the live configured project and migration sessions as Feature → Slot → Part modules, imports, exports, and violations. |
| Owner test evidence | Generates and verifies owner-aware Vitest and Playwright artifacts from the same architecture contract. |
| Shared CLI | Creates strict owners, checks architecture, audits toolchains, runs Vite, and optionally hands off to VS Code or Studio. |
| Software-free MCP | Generated MCP configuration supports inspection, validation, and safe scaffolding without a running desktop application. |
| Monorepo workflow | Discovers bounded Vite/Next apps, generates VS Code/MCP routing, and aggregates architecture plus owner-test verification. |
| Optional Bun mode | Runs detected Vite projects through an explicit Bun turbo path while keeping Node as the compatibility default. |
| Native safety | Uses Rust for path containment, bounded reads, optimistic hash checks, atomic saves, and managed processes. |
Deliberate limits
Section titled “Deliberate limits”- The Studio source pane is read-only; general text editing belongs to VS Code.
- Only visual operations with a lossless bounded TSX edit are active.
- Browser mode uses an in-memory workspace and has no filesystem or process authority.
- The derived preview does not execute connectors or arbitrary project imports.
- Custom component packages, signed toolchain sidecars, collaboration, and a public plugin SDK are not shipped.
- Native Windows, macOS, and Linux artifacts still require signed platform-specific release pipelines.
Published distribution
Section titled “Published distribution”The public alpha is distributed as three coordinated npm packages:
create-srijika— thenpm createlauncher;@srijika/cli— project creation, scaffolding, validation, and runtime commands; and@srijika/mcp-server— project-aware tools for Codex and other MCP clients.
The matching
Srijika Language Support
extension is published on the Visual Studio Marketplace. It exposes the shared
architecture, migration, runtime, and owner-test workflows directly in VS Code.
Releases are verified in GitHub Actions and published through npm Trusted Publishing with provenance. See the current GitHub release.
Rust: present versus planned
Section titled “Rust: present versus planned”Rust is already used in the Tauri desktop boundary and core project services. It validates filesystem access, persistence rules, process management, and stable document envelopes.
Generated Rust application backends are not implemented yet. Phase 2 introduces versioned API documents, typed payloads, Rust routes, validation, workflows, endpoint composition, and a unified deployment target.
Alpha communication rule
Section titled “Alpha communication rule”Public-facing or internal product copy must say code-first React application studio for the current release. “Full-stack application studio” becomes accurate only when the Phase 2 backend workflow is implemented and verified.