QUBE is a small package family for agent-assisted software work. The packages cover planning, issue execution, quality gates, and continuation policy. Each tool can be installed and used on its own; @tjalve/qube provides one composer CLI for discovering and dispatching to the installed tools.

The public-ready QUBE landing page lives at docs/index.html and is designed for GitHub Pages at https://zark.github.io/ai-qube/. Preview it locally with:

pnpm run site:preview

Use exact versions for automation and keep dependency lifecycle scripts disabled where your package manager supports it.

Use the guided installer to select the install scope, package manager, agent harness, and provider configuration:

qube install
qube install --yes --dry-run --json
qube install --apply --yes
qube install --scope global --package-manager npm --yes

The installer prints a plan and copyable commands by default. --apply executes the remaining pinned install delta after confirmation, or immediately with --yes. --json without --yes stays plan-only.

pnpm add -D --save-exact --ignore-scripts @tjalve/qube@0.1.1
pnpm exec qube components

Global installs are useful for manual command-line use, but project-local installs are easier to audit and reproduce:

npm install -g @tjalve/qube@0.1.1 --ignore-scripts
qube components

Install a single component when you intentionally only need that package:

pnpm add -D --save-exact --ignore-scripts @tjalve/aib@0.1.1
pnpm exec aib --help

qube dispatches to the component versions installed with the composer package. Use the composer entry point for automation, agent instructions, hooks, and durable examples. In a source checkout, qube can dispatch to matching workspace packages.

qube components
qube autoresearch init ./scratch "improve notes summary quality" --json
qube oneshot "Ship a local notes CLI" --kind code --json
qube make-it-so "Ship a local notes CLI" --dry-run --json
qube aib init . --idea "Ship a local notes CLI" --json
qube aie queue --json
qube aiq doctor --format json
qube aiu status --json

qube make-it-so is the cardinal work command. It does not invent a hidden workflow. By default, free-form text maps to the planned flow through qube aib init, while --flow issue next or --flow issue <number> maps to the AIE issue lifecycle. The direct-local flow is blocked until QUBE has a real oneshot workflow; it reports the missing setup instead of creating placeholder work. Use --dry-run --json to inspect the mapped command and boundaries before running it.

qube autoresearch creates a safety-bounded local arena under .qube/autoresearch/. The first supported target type is a local directory: init writes a fixed evaluator and arena plan, baseline records immutable baseline evidence, run creates a sandboxed candidate, status and dashboard report structured state, and promote is the only step that copies the selected candidate back to the target or requested output path.

qube oneshot creates a bounded local artifact without entering the normal GitHub issue, pull request, or review-gate workflow. The first supported path is a scratch doc or code artifact under .qube/oneshot/<run-id>/: it records inputs, assumptions, plan, actions, checks, local review, risks, summary, and final output. The summary explicitly states that no GitHub issue, branch, pull request, review request, merge, or approval was created by default.

The composer first resolves component binaries from its npm install scope. In a source checkout, it then checks the current workspace install.

packages/
  qube-cli/       shared public CLI library
  qube-core/      private shared workspace contracts
products/
  aib/            planning CLI
  aie/            execution CLI
  aiq/            quality CLI and adapters
  aiu/            continuation policy CLI
  qube/           composer CLI
adapters/
  github/         GitHub provider capability adapter
  opencode/       OpenCode host capability adapter
docs/

Public package READMEs live beside the package that npm publishes. They contain the package install instructions. Product docs under docs/ explain command boundaries and agent harness surfaces. docs/release-controls.md and docs/version-audit.json describe release controls and package versions.

Publishing is package-specific. A tag selects exactly one package:

publish-qube-cli-v<version>
publish-aib-v<version>
publish-aie-v<version>
publish-aiu-v<version>
publish-aiq-v<version>
publish-qube-v<version>

The shared publish workflow runs on publish-* tags, uses the GitHub Actions environment npm-publish, verifies the selected package, and publishes to npm with trusted publishing and provenance. See docs/release-controls.md for the trusted-publishing setup, staged approval flow, and first publish exception for brand-new package names.

corepack enable
pnpm install --frozen-lockfile --ignore-scripts
pnpm run verify

Use root workspace filters for package work:

pnpm --filter @tjalve/aie run verify
pnpm --filter @tjalve/qube run verify

Useful public docs:

• docs/index.html
• docs/qube-command-surfaces.md
• docs/qube-claude-code-host-support.md
• docs/qube-codex-host-support.md
• docs/qube-gitlab-provider-support.md
• docs/qube-host-surfaces.md
• docs/qube-jenkins-provider-support.md
• docs/qube-jira-provider-support.md
• docs/qube-linear-provider-support.md
• docs/qube-paths-and-artifacts.md
• docs/release-controls.md
• docs/version-audit.json