Skip to main content
BRIK64 is published as a CLI-first developer workflow. The current public beta gives developers and AI agents a local way to work with PCD files, create scoped local evidence, and emit candidate outputs for supported targets.

​
Available Today

BRIK64 CLI 0.1.0-beta.7 is the current public local beta. The official command is brik64.
SurfaceCurrent public status
Current public version0.1.0-beta.7.
Release notesGitHub Releases
Install pathcurl -fsSL https://brik64.com/cli/install.sh | bash
Release manifesthttps://brik64.com/cli/releases/0.1.0-beta.7.json
Public scopeLocal CLI workflow for PCD files, local evidence, and candidate output generation.
Agent skillAvailable through the public BRIK64 skills repository or a supported host agent environment.
Use brik64 --version and brik64 help after installation to verify the installed package. The local workflow is centered on the brik64 command: 
brik64 help
brik64 version
brik64 --version
brik64 init
brik64 certify <file.pcd>
brik64 verify <file.pcd>
brik64 emit <file.pcd>
brik64 polymerize <files.pcd...> --out polymer.pcd
brik64 migrate <file.pcd> --out migrated.pcd
brik64 doctor --json
brik64 emit <file.pcd> --target ts --out out-ts --tests
brik64 emit <file.pcd> --target rust --out out-rust --tests
brik64 emit <file.pcd> --target python --out out-python --tests
Agent instructions are installed only through explicit consent. The current public beta uses the public skills repository or the host agent environment for agent instructions. brik64 init prepares a BRIK64 workspace. It does not create or modify AGENTS.md.

​
Platform Status

PlatformStatus
macOSAvailable in beta through the portable Node.js CLI package.
LinuxAvailable in beta through the portable Node.js CLI package.
Windows x64Not published in beta.

​
Updates

There is no silent auto-update path in the public local workflow. Re-run the installer, release manifest and GitHub Release page to verify the current beta package.

​
Platform Features

Hosted collaboration, cloud execution, paid entitlements, billing-backed features, and stronger evidence workflows require dedicated platform support. Public CLI documentation must not imply that those features are active unless the page links to current release evidence.

​
Platform Support

The public docs currently target the local CLI flow and portable source-level concepts. Platform-specific binary support is documented only when a release artifact has been verified.