BRIK64 CLI is the public beta command-line surface for local BRIK64 project
workflows. It helps developers initialize .brik metadata, work with PCD files,
create local candidate evidence, emit supported language targets, and prepare
artifacts for managed platform workflows.
Current public beta: 0.1.0-beta.8
The public CLI install path is curl-only:
curl -fsSL https://brik64.com/cli/install.sh | bashAfter installation:
brik64 --version
brik64 helpThe npm package namespace is reserved for SDK libraries, not CLI installation.
0.1.0-beta.8 focuses on making PCD emission executable for the supported
beta syntax while keeping local/managed workflow boundaries intact.
brik64 initcreates.brik/manifest.jsonand does not createAGENTS.md.brik64 doctorprints a human-readable workspace summary.brik64 doctor --jsonemitsbrik64.cli_doctor_report.v1for CI.brik64 account statusshows whether the CLI is using local default routing or a managed session.brik64 login --token-env <VAR>records a managed-session token hash without printing the token.brik64 logoutreturns routing to local default.brik64 certify <file.pcd>writes a local candidate certificate.brik64 verify <file.pcd>checks local certificate and AST/hash coherence.brik64 emit <file.pcd> --target <ts|rust|python> --out <dir> --testsemits executable target files and generated tests for supported beta PCD expressions and branches.brik64 polymerize <files.pcd...> --out polymer.pcdcombines compatible PCD files into a deterministic local polymer candidate.brik64 migrate <file.pcd>converts supported legacy PCD syntax into the current strict syntax.
Managed --cloud paths are entitlement-gated in this beta. Without a managed
session, those paths fail closed and keep local artifacts unchanged.
| Platform | Status | Notes |
|---|---|---|
| macOS | Available in current beta candidate | Portable Node.js CLI package; requires Node.js 20 or newer. |
| Linux | Available in current beta candidate | Portable Node.js CLI package; requires Node.js 20 or newer. |
| Windows x64 native | Not available in current public beta | No Windows executable is published. |
The public installer verifies the package SHA-256 before activation. The
authoritative checksum is published with release assets in package.manifest.json
and SHA256SUMS.
SDKs are distributed separately from the CLI. Current beta SDK package coordinates:
npm install @brik64/core@0.1.0-beta.8
pip install brik64==0.1.0b8
cargo add brik64-core@0.1.0-beta.8SDK packages are language libraries. They do not install the CLI, issue managed claims, or replace the CLI workspace workflow.
This beta provides local candidate evidence and managed-workflow routing boundaries. It does not by itself establish formal certification for arbitrary user code, universal correctness, independent toolchain closure, or native Windows compatibility.
Use the CLI for local project actions and the official brik64 skill for agent
behavior, claim-safe reporting, .brik traceability, PCD workflow, and
consent-based AGENTS.md handling.
brik64 init prepares local BRIK64 metadata. It does not create or modify
AGENTS.md.
| Path | What it contains |
|---|---|
src/brik.js |
Node.js entry point for current public beta command behavior. |
tests/smoke.sh |
Local smoke test for current beta command behavior. |
pcd/ |
Candidate PCD seed material for command structure. |
evidence/ |
Public beta evidence notes and generated-review placeholders. |
packaging/ |
Platform packaging notes and release-lane material. |
docs/ |
Release, distribution, governance, platform, and testing docs. |
.brik/manifest.json |
Local traceability metadata. It is not a certificate. |
Use GitHub Release assets, release manifest, and SHA256SUMS to review the
latest published package.
https://github.com/brik64/brik64-cli/releases
Copyright (c) 2026 BRIK64 INC. All rights reserved.
See LICENSE and NOTICE. BRIK64 CLI public beta is proprietary evaluation software from BRIK64 INC.