Release
Superbee 0.1.3
What Superbee 0.1.3 enabled, who could use it, and the shortest safe setup path.
Superbee 0.1.3
Superbee 0.1.3 established the first supported path from a global CLI install to a durable local workspace that agents and humans can inspect together.
What you can do
Install one self-contained
superbeecommand from npm.Let
superbee setupinspect Codex, Claude Code, Claude Desktop, or OpenCode and propose one host-specific setup action at a time.Create a local OKF 0.2 workspace with
superbee init.Preserve typed Markdown documents, links, reusable conventions, and recipes.
Open a document in Superbee's Markdown reader.
Who should act
At publication, new macOS and Linux users could install this release. Existing 0.1.3 users did not need to take any action.
Windows was not supported by the 0.1.3 npm package. Do not work around the platform restriction or
interpret unreleased Windows work on main as stable support.
Install or verify
npm install -g superbee@0.1.3
superbee setupFollow only the exact next action returned by setup, restart the selected host when instructed, and rerun setup to verify the result.
Compatibility and recovery
Node.js 20 or newer is required.
Setup is a read-only conductor; it does not silently edit host configuration.
If host integration is incomplete, rerun
superbee setupand follow its next action. Reinstall or repair the npm prefix only when setup explicitly requires it. Do not initialize another workspace as a repair step.Pin
superbee@0.1.3when a reproducible environment must not follow a later stable release.
The exact package identities, source commit, integrity hashes, verification journey, and evidence limits remain available in the 0.1.3 release evidence.