How the OpenWiz repositories fit together, and what each one does today. Older release notes stay on GitHub’s releases.
Cloudroom and GitHub, dashed, are where your agents and your work live.
What exists today
Written from the merged code in each public repository. Nothing here is a plan.
OpenWiz openwizdev/OpenWiz
OpenWiz is the factory’s command and kernel. It reads and drives your coding agents’ threads in Cloudroom, and reads your fleets’ specs and tickets on GitHub. It pins a WizSkills release and reads WizLoops’ loop files.
openwiz ls and openwiz show list and open your Cloudroom threads, and only read.
openwiz send sends one message to a thread, queued or as a steer. openwiz new starts one new thread, and only with --yes. Both can attach files.
openwiz fleets and openwiz fleet show your fleets and each spec’s progress, read from GitHub.
openwiz loop checks loop files, shows what would change, creates or updates one Cloudroom loop, and writes your live loops back to files.
openwiz help --agent lists every command for scripts and agents, and most commands give one clean result with --json.
openwiz-server serves a web view on your own computer: your threads, fleets, the plan, decisions waiting on you, and loops.
openwiz-service keeps that web view running on a PC and runs its registered jobs on a schedule.
Prebuilt pre-releases for macOS and Linux are on OpenWiz’s GitHub releases, and trail main. Most of this is tested on synthetic fixtures only.
WizSkills openwizdev/WizSkills
WizSkills holds the skills: plain instructions, with their scripts and tests, that a coding agent follows. With them, agents grill an idea, plan it into tickets, then build, review and merge each ticket as a fleet.
One Claude Code plugin, openwiz, installed pinned to a release; install.sh installs the same release for Codex or any other agent.
grill, build-ticket, review-ticket and launch-fleet: question an idea, build one ticket, review its pull request, and run the fleet.
Helpers for the work around it: wayfind, research, diagnose, where-are-we, handoff and triage.
WizLoops keeps an agent’s loops as files: one Markdown file per loop, saying when it wakes, what it checks first and what the agent is told. It holds the format, a starter catalog and the rules for Cloudroom, and no code. OpenWiz’s openwiz loop commands read these files.
The loop file format, with its JSON schema and fixtures.
Five starter loops: fleet-check, hourly-status, morning-digest, stall-sweep and workflow-kick.
The Cloudroom adapter rules: what maps to a Cloudroom loop, and what is refused rather than faked.
CI checks every catalog loop and fixture with openwiz loop validate.
Cloudroom is the only adapter so far.
WizPlugins openwizdev/WizPlugins
WizPlugins holds plugins that show the factory inside Cloudroom. Its one plugin so far, WizBar, is a sidebar of your agents’ threads with their issues, pull requests and child threads.
WizBar’s cards link each thread’s issue or pull request and count its child threads; hover to list them.
A running count with a stats panel, and drag to pin.
Every WizBar action is also a room-cli wizbar command with JSON.
Not in the plugin marketplace yet: install it from source. Fixture tests prove it; its check on a real Cloudroom is still open.
WizSite openwizdev/WizSite
WizSite is openwiz.dev: the landing page, this changelog and the app. It is a static site on Cloudflare Pages with one small sign-in helper, and the app reads GitHub from your browser.
The landing page walks through a sample to-do build and the agents OpenWiz works with. Its Install button says coming soon.
openwiz.dev/app: sign in with GitHub through the read-only OpenWiz Viewer app, pick a repository, and put the app on your phone’s home screen.
You shows what needs you: counts of work needing you, building, in review and merged, then the specs to confirm, plans to approve and tickets waiting on you, each linked to GitHub.
Specs shows each open spec’s progress, and each spec’s page draws its ticket graph.
The Agents page is a placeholder for now.
Releases
Generated when this page is built, from each release’s own published notes. Every release from 0.1.0 on, patches included, newest first.
OpenWiz openwizdev/OpenWiz
No release yet.
WizSkills openwizdev/WizSkills
WizSkills 0.1.2
Released
install: no longer chooses or activates an engine; after setup it checks CloudRoom, explains the product in a few lines and hands over to onboard, and every step reuses what an earlier one recorded.
launch-fleet: fleet.sh overload can read the war room collector's queue at the time of each new-work call through an OpenWiz checkout's own supplier (LAUNCH_FLEET_OVERLOAD_SUPPLY), and refuses new work as unknown when that supplier fails; the limit-recovery notes name the war room's renamed files.
onboard: starts from a fresh install with a new Connect step for the one chosen repository (GitHub sign-in, the user's own App or an explicit skip, the prepared project and its private brain), reuses the recorded harness, model and effort, and launches the first fleet as one launch-fleet fleet thread instead of the engine's tick.
setup: the person may explicitly skip the App, so their verified personal GitHub login acts on the selected repository and the App stays missing.
contracts/cli.v1.md (carried contract): records the removal of the terminal app and ui, the retirement of the executing fleet tick, --expect-plan and the engine commands, and the shipped loop validate, loop export, loop plan and loop apply reports.
WizSkills 0.1.1
Released
build-ticket: builders rule on choices inside the ticket and log each ruling in the pull request, follow a project's standing supporting-edit rule, and answer the review loop's v2 states, including one fresh round.
diagnose: the orchestrator's diagnosis now comes only inside a decision that relays the owner's answer to a parked finding.
launch-fleet: routes each review's v2 Next: line, starts at most one fresh round per pull request and parks findings for the owner; its GitHub App is private and checks the App's owner and installation before minting a token.
review-ticket: marks every ruling upheld or overturned, logs a re-check's remaining user-path blockers as follow-up issues, and sends risk blockers to one fresh round before parking them for the owner.
contracts/cli.v1.md (carried contract): adds four planned loop commands, validate, export, plan and apply, each reported as not built yet.
WizSkills 0.1.0
Released
First public release of OpenWiz's skills, one line per skill below.