Public release repository for the Picadabra CLI.
This repository hosts:
- GitHub Releases for the executable
picaJavaScript bundle - Release checksums and the machine-readable update manifest
- The public installer script at the repository root
- Public issue tracking for distribution concerns
The source code lives in a private monorepo. Releases in this repository are published automatically from the upstream build pipeline.
curl -fsSL https://raw.githubusercontent.com/AIGC-Hackers/pica-cli/main/install.sh | bashTo install a specific version:
curl -fsSL https://raw.githubusercontent.com/AIGC-Hackers/pica-cli/main/install.sh | bash -s 0.2.10Default install path is ~/.local/bin. Override with PICA_INSTALL_DIR:
PICA_INSTALL_DIR=/usr/local/bin curl -fsSL https://raw.githubusercontent.com/AIGC-Hackers/pica-cli/main/install.sh | bashThe installer downloads pica-manifest.json for the chosen release, verifies
pica-bundle.tar.gz, installs Bun when it is missing or below the required
minimum version, and installs pica as a thin wrapper over the managed bundle
layout under ~/.local/share/pica/cli.
Download pica-bundle.tar.gz and pica-manifest.json from the
Releases page, extract the
bundle, and place pica.js in your preferred managed layout if you do not want
to use the installer script.
Each release also includes a checksums.txt file with SHA-256 digests.
After installing pica, complete the initial setup before using CLI features
that talk to Picadabra services.
- Visit https://picadabra.ai/ and sign in.
- Open the dashboard.
- Go to
API Keys. - Click
Create new keyand copy the generated key to a secure place.
If you cannot load the API key page, make sure you have completed sign-in first.
Install the official Picadabra skill in the working directory where your agent runs:
pica skill install picadabra/picaThis installs the Picadabra skill locally so your agent can discover and use Picadabra capabilities from the current workspace.
Use the API key you created above with the relevant pica authentication or
configuration flow in your environment, then verify the active setup with:
pica statusffmpegandffprobeare not bundled yet.- Commands that rely on local media probing may require system tooling until the managed toolchain work lands.
- Release issues: open an issue in this repository
- Product and source work: handled in the private upstream repository