Vivary

The experience we are building

• Open a project and work with an agent that can read files, edit them, and run tools.
• Return to project conversations, search past sessions, and keep useful memory in files.
• Use supported installed coding harnesses and their tools, with workspace guidance in files.
• Preview the site or dashboard you are building and let the agent inspect and debug it.
• Connect a phone browser to your self-hosted instance when you choose to enable remote access.

Local desktop use needs no Vivary account. Remote access requires explicit setup and authentication. Provider accounts are separate.

Release status

In development. The tested Windows candidate is not a public release.

Verified in the private Windows candidate	Still required for release
Explorer launch/extraction, bundled runtimes, second-instance reuse, restart persistence, and owned-process cleanup	Clean-profile first run, upgrade/removal behavior, remaining desktop/web acceptance, and release approval
Managed project creation, project files, clear validation/refusal, retained Code history, and a real approved Claude Code file turn	Existing-folder adoption, search, scoped memory, and complete original-operation GUI flows
CLI runtime readiness and read-only Claude Code · sonnet identity	Selectable Codex execution, harness-owned model catalog/switching, and real Native-provider turns
Private authenticated web preview and basic isolated page preview	Responsive self-hosted phone access and integrated preview/debugging acceptance

The desktop acceptance register separates verified behavior from known gaps. The desktop package record describes the tested artifact. The GitHub milestone owns remaining work and acceptance. Mac distribution is optional later work.

Start here

This is the private development repository for the app. Development and hosted preview run on Zo. Zo is not a product dependency.

You want to…	Start with
Build or run the GUI from source	Workbench setup
Run or package the desktop shell	Desktop setup
Pick up an issue and contribute	Contributor guide
Understand current desktop acceptance and gaps	Acceptance register
Understand the product and implementation	Interactive guide, release target, and source map
Enable agent-session recording	Entire setup
Use the original published command tools	Original CLI reference

Agent-Native owns conversations, runs, actions, and connectors. Vivary connects those capabilities to project workspaces and the original Vivary tools. The engineering policy keeps implementation focused on completed user workflows.

GitHub issues own task scope, acceptance, dependencies, and status. Contributors use topic branches from dev, reviewed PRs into dev, and accepted promotions to main. Follow the contributor workflow.

Original Vivary

The original CLI, package history, and release tables are preserved in the original CLI reference. Those published packages do not constitute a release of the desktop app.

MIT. See LICENSE.