@holaxis/aslite

Aslite has been renamed to Superbee. Future updates are published as the superbee npm package. Install and verify the maintained successor:

npm install --global superbee
superbee version --json

@holaxis/aslite is the final migration bridge. Its existing aslite and agentstate-lite commands remain functional so current users can migrate without interrupting their work, but this package will not receive ongoing product updates. Superbee is the maintained package going forward. For setup, current commands, and examples, use the Superbee package documentation.

Legacy bridge details

This package is an OKF-native, CLI-first, agent-facing knowledge store: context notes, docs, cross-links, and live bundle Views in a plain folder of user-owned files that works offline, with an optional wire backend when a separate service hosts the bundle.

The npm artifact ships one self-contained executable file with zero runtime dependencies, plus a generated migration Skill (SKILL.md and its references/ folder) that directs agents to the maintained superbee command. npm is the sole executable distribution channel; the installed Skill contains guidance and references, not a second CLI copy. Maintainers can reproduce the complete package proof from the repository root with npm run verify:npm-package; it builds, packs, installs into an isolated prefix, resolves both command names from PATH, and exercises an offline bundle workflow. This developer proof deliberately stamps local-dev, so it works on an in-progress/dirty checkout; prepublishOnly runs the same journey in strict npm-package mode and refuses unless Git proves an exact clean source commit.

What it is

A knowledge bundle is a directory of markdown that conforms to the Open Knowledge Format (OKF) — so it survives the tool: open it in any editor, render it on GitHub, diff it in git, hand it to someone else. On top of that portable format, aslite adds an agent-facing CLI (TOON output, a capped exit-code taxonomy, structured errors) and a local UI for live bundle Views.

• Local-first. Everything works with the network off; the filesystem is the source of truth.
• Agent-native. The primary interface is a small, predictable CLI designed to be driven by AI agents, with a SessionStart hook installer for Claude Code / Codex / OpenCode.
• Human-visible. aslite ui --open opens a local browser window over the bundle: read its docs as rendered pages (cross-links you can follow, derived backlinks), see a live activity feed and the bundle's sharing status, and launch its registered Views — which present live data through the read-only v0 bridge or propose one human-confirmed local scalar action through v1. (Page is the retired legacy name for the View kind — legacy-named content no longer registers; aslite status flags it and the repo's migration script renames it in place.)

Optional: a shared remote bundle

Run the reference server over a local bundle, then point any command at it with --remote:

aslite serve --dir ./my-bundle      # loopback, keyless reference server
aslite list --remote http://127.0.0.1:4818

The public package intentionally stops at this generic wire boundary. It does not ship a hosted deployment, identity system, account-administration commands, or cloud-provider recipe. A separate service can implement the same versioned storage and HTTP contracts without changing the local engine or CLI.

Documentation

Run aslite --help (or any subcommand with --help) for the full command reference. Design and format docs live in the repository.

License

MIT © Holaxis