GitHub

Roadmap / Direction, not deadlines

Keep the agent you trust.
Make small work verifiable.

Our priorities are public. Dates and version promises will follow evidence—not the other way around.

/01In development

Local-first UI/UX companion

One local project. Your existing coding agent in control.

  • Keep planning, design decisions, and risky work with the main coding agent.
  • Coordinate a small Button, Input, or Select task through an explicit contract.
  • Show real progress, blockers, and requests for human input.
Current evidence

A local test-double coordination and browser status-panel prototype exists. A packaged desktop application is not available.

/02Acceptance pending

User-connected API workers

Routine UI work within a clear scope.

  • Use a provider-independent worker boundary with explicit user authorization.
  • Bound allowed files, attempts, and runtime; stop or escalate on failure.
  • Keep provider API costs separate from the free Spexop software; never silently fall back to paid usage.
Current evidence

One real Groq inference benchmark on a synthetic Input task reached partial acceptance. There is no product worker integration or external product acceptance.

/03Open

Independent verification and user acceptance

A passing internal test is one part of the evidence.

  • Keep PASS, FAIL, and UNKNOWN distinct and bind evidence to the checked revision.
  • Exercise negative paths, bounded retry, recovery, and scope enforcement.
  • Validate a versioned private build in a separate consumer UI project with a fresh coding-agent context.
Current evidence

Internal local tests and browser checks exist for the simulated prototype. A separate synthetic real-API benchmark does not establish product worker execution, usable desktop acceptance, or independent external product acceptance.

/04Existing engineering work

Preserve the design foundations

Build on the useful tools already developed.

  • Retain Theme, the Canonical Design Model, and source provenance.
  • Preserve Foundation Capture, CSS Export, Build Context, and Build Evidence.
  • Keep earlier limitations and unsuccessful user experiments visible; these tools are not prerequisites for the first companion loop.
Current evidence

The public source repository contains these tools. They do not establish a released desktop companion or general end-to-end CSS equivalence.

/05Gates open

Open-source release readiness

Public source with a separate product and package release boundary.

  • Complete source rights, security, package, and consumer checks for the selected release.
  • Publish accurate installation instructions only for a verified build.
  • Keep public launch, npm publishing, and product acceptance as separate owner decisions.
Current evidence

The current monorepo source is public under MIT. There is no public R1 installer, verified product API worker, release date, or paid feature tier. npm and product acceptance remain separate.

Follow the public source on GitHub. Desktop delivery, product API worker integration and external product acceptance remain open.

View the source ↗

Independent. Open source.

Built for independence.
Supported by people like you.

Support local-first UI/UX tooling, clear documentation, and independent checks for bounded AI-assisted development.

Sponsor Spexop UI