Actspan Docs Quickstart
DocsGetting started

Install the Actspan release CLI, get an example workspace, and set a provider credential.

On this page

Install Actspan

Install the free Actspan 0.2.0 CLI, then initialize, validate and preview a workspace locally. Hosted portal access and deployment packages are available separately for design partners.

Before you begin

The current public native download is an early-access Apple Silicon macOS (arm64) build. For an assisted evaluation, use your existing Actspan contact; mailbox verification and the branded-domain cutover remain pending.

Task Prerequisites
Public CLI installation Apple Silicon macOS; Bash, curl, jq, unzip, shasum on PATH
Example extraction tar, plus the download/checksum tools above
Small no-tool prompt CLI only; provider key for a live request
Refund ledger/checker Separate host Python 3.10+; no system Python is supplied by the CLI
Optional Python SDK/framework Separately supplied packages and pinned host environment

The CLI includes Python. Bash, curl, jq, unzip and shasum are required by the installer. In particular, jq must already be installed and available on your shell's PATH; the installer does not install it. Check before continuing:

command -v jq && jq --version

If that command fails, install jq using your operating system's package manager and retry. Do not assume it is present on every Mac or minimal Linux system.

The public executable is ad-hoc signed, rather than signed with an Apple Developer ID, and is not notarized. If macOS blocks it, use the opening instructions below. Fresh-machine Gatekeeper acceptance has not been qualified. Linux private release assets are listed below; they are separate from this public download.

No private repository account is required for the public download. The public examples archive contains the three homepage workflows and native OpenAI/Claude refund examples. The two-file first prompt in the quickstart also works without that archive.

Before using approval workflows, read the known 0.2.0 package-tool binding issue. It does not affect the no-tool prompt in the quickstart. The corrected source needs the next qualified public core release; the CDN build linked below does not include it. New private release attachments need their own qualification. The release notes collect the public build's current limits and verification scope.

You need your own provider key before a live run. The supplied research workflow also needs hosted web search. Installation, initialization, validation and preview do not call a model. Live runs and evaluations use your provider account and incur its normal charges.

Download availability

Distribution status as of October 22, 2026:

Channel Native CLI files available Access
Public HTTPS download Apple Silicon macOS (macos-arm64), with the signing and approval limits above Use the free CLI commands below; no repository account is required.
Private release assets Linux AMD64 and ARM64, with standard and musl ZIPs Supplied separately through an authorized design-partner handoff. These files are not in the current public download catalog.
macOS attachments in the private release No Mac ZIPs are attached in the reported release inventory The existing public Apple Silicon bundle remains a separate download.

Each attached Linux ZIP has a matching *_SHA256SUMS file and detached *_SHA256SUMS.asc signature. The release also provides actspan-release-public.asc. Download availability does not establish a successful installation or verification of those particular files.

The channels have independent artifact identities. See release notes for private release attachment and publication details.

Install the free CLI

The CLI files are served from a dedicated S3 origin through this public HTTPS download endpoint. Download the installer and verify its exact published hash:

(
set -eu
mkdir -p "$HOME/actspan-installer"
cd "$HOME/actspan-installer"
curl --fail --silent --show-error --location --proto '=https' --proto-redir '=https' \
  https://d3jf0s2r29lnlr.cloudfront.net/install.sh -o install.sh
echo '93be140d34b290b3d4a69486138d3cbb4c8f7d756030aa72177edd9c3ce0ae70  install.sh' | shasum -a 256 -c -
bash install.sh --version 0.2.0
)
export PATH="$HOME/.local/bin:$PATH"
actspan --version

The subshell stops before execution if download or verification fails. The installer verifies the native archive checksum and tests the command before switching a managed installation. It uses no sudo and makes no shell-profile changes. Expected: actspan --version contains 0.2.0. The product repository, Python registry packages and partner deployment artifacts remain private; this download contains the native CLI runtime and its license notices.

The intended short URL is https://actspan.com/install.sh. It still redirects to the existing Wix site and is not active for this installer. Use the verified endpoint above until the domain cutover is complete.

Try a prompt without an examples archive, or download the public examples below.

If macOS blocks the CLI

The published 0.2.0 executable has an ad-hoc code signature with no Apple Developer Team ID. That signature is different from Developer ID signing and Apple notarization. A new release needs completed signing/notary checks and qualification of its exact delivered download before this status changes.

If macOS reports an unidentified developer or says it cannot check the app, Apple's current route is System Settings → Privacy & Security → Open Anyway after an attempted launch. The exact labels can vary by macOS version. See Apple's opening instructions. Proceed only if you choose to trust this release after verifying its download. An alert identifying malware or damaged software needs investigation; these steps are for the unidentified-developer warning.

If the automated installer stops before activating the CLI, keep a verified manual extraction in a stable directory. The following Apple Silicon commands refuse an existing target and stop before extraction if verification fails:

(
set -eu
mac_install_dir="$HOME/actspan-manual/0.2.0"
if [ -e "$mac_install_dir" ] || [ -L "$mac_install_dir" ]; then
  echo "Manual install directory already exists; inspect it before retrying." >&2
  exit 1
fi
mkdir -p "$mac_install_dir"
cd "$mac_install_dir"
curl --fail --silent --show-error --location --proto '=https' --proto-redir '=https' \
  https://d3jf0s2r29lnlr.cloudfront.net/cli/releases/0.2.0/actspan-0.2.0-public1-macos-arm64.zip \
  -o actspan-0.2.0-public1-macos-arm64.zip
echo '2c88c92cf49ef7d2aedf37cf5397562ea76c1f9530f9ba6d0aafc144286e7f88  actspan-0.2.0-public1-macos-arm64.zip' | shasum -a 256 -c -
unzip -q actspan-0.2.0-public1-macos-arm64.zip
./actspan/actspan --version
)

If that launch is blocked, leave the extracted directory intact. Open System Settings → Privacy & Security, find the recent Actspan block and choose Open Anyway if you decide to allow it. Authenticate when macOS asks, then retry the same executable. The exception is for this download; do not disable Gatekeeper globally.

After the version command succeeds:

"$HOME/actspan-manual/0.2.0/actspan/actspan" --version
bash "$HOME/actspan-manual/0.2.0/actspan/INSTALL_BINARY.sh" \
  --target "$HOME/actspan-manual/0.2.0/bin"
export PATH="$HOME/actspan-manual/0.2.0/bin:$PATH"
actspan --version

Keep the complete actspan/ folder, including _internal/, in that location. The included installer creates a command symlink to the retained executable; the separate command directory preserves an existing ~/.local/bin/actspan. The helper does not notarize the executable. These instructions use Apple's documented exception flow; a fresh supported-Mac installation still needs its own qualification.

Install the supplied CLI

This is an alternative installation path for a supplied private starter bundle. Request that handoff through your existing Actspan contact; the public address is info@actspan.com, whose mailbox setup is still pending. It is not necessary for the free installation above.

Extract the starter handoff into a directory of your choice, then enter it. Use its actual directory name in place of the path below:

cd /path/to/actspan-0.2.0-starter
shasum -a 256 -c SHA256SUMS

On Linux, use sha256sum -c SHA256SUMS. Stop if a checksum does not match and request a replacement from your Actspan contact. A checksum checks that the files match the supplied manifest; the handoff's delivery channel establishes who supplied it.

Use the platform filename actually present in the supplied manifest. The reported private release inventory has Linux ZIPs and no Mac ZIP; it is not the public Mac channel. For example, an AMD64 Linux handoff can contain actspan-0.2.0-linux-amd64.zip. Select it only on that platform:

unzip actspan-0.2.0-linux-amd64.zip -d "$HOME/actspan-0.2.0-linux-amd64"
bash "$HOME/actspan-0.2.0-linux-amd64/actspan/INSTALL_BINARY.sh"
export PATH="$HOME/.local/bin:$PATH"
actspan --version

This example does not supply that private archive. Stop if the handoff's file, platform, checksum or qualified build identity differs. A separately assembled Mac starter must explicitly list its Mac archive; do not infer it exists from the private release inventory. Use the public Mac installation above otherwise.

Keep the complete extracted actspan/ folder, including _internal/; the installer's command points to that retained runtime. Review an existing installation before replacing it. The version label alone is not its build identity or qualification record.

The CLI binary includes Python. Installing a separately versioned provider plugin additionally needs a host Python 3.10 or newer with venv and pip. Use the bundled OpenAI adapter for the first workflow. If your evaluation needs an independent plugin, your handoff must also provide package-index access or a reviewed wheelhouse and its dependency closure. See provider requirements.

Download the public examples

Download the versioned examples archive and checksum from the same public download endpoint. Verify the archive before extracting it; the checksum checks file integrity and HTTPS establishes the download source.

(
set -eu
mkdir -p "$HOME/actspan"
cd "$HOME/actspan"
if [ -e actspan-examples ] || [ -L actspan-examples ]; then
  echo "actspan-examples already exists; choose a fresh directory before extracting." >&2
  exit 1
fi
curl --fail --silent --show-error --location --proto '=https' --proto-redir '=https' \
  https://d3jf0s2r29lnlr.cloudfront.net/cli/examples/0.2.0/public2/actspan-examples-0.2.0-public2.tar.gz \
  -o actspan-examples-0.2.0-public2.tar.gz
curl --fail --silent --show-error --location --proto '=https' --proto-redir '=https' \
  https://d3jf0s2r29lnlr.cloudfront.net/cli/examples/0.2.0/public2/actspan-examples-0.2.0-public2.tar.gz.sha256 \
  -o actspan-examples-0.2.0-public2.tar.gz.sha256
shasum -a 256 -c actspan-examples-0.2.0-public2.tar.gz.sha256
tar -xzf actspan-examples-0.2.0-public2.tar.gz
) && cd "$HOME/actspan/actspan-examples/openai/data_enrichment"

Extract into a fresh directory to avoid mixing versions. Keep the complete actspan-examples/ layout because the Claude refund workspace shares the sibling OpenAI sandbox service. The archive contains synthetic fixtures and no provider credentials. The separate LangChain adapter requires a design-partner Python installation; it is not part of this native examples download.

The data-enrichment directory contains workspace.yaml, policies.yaml and eval_summarize_data_enrichment.yaml. The CLI and examples are separate downloads.

Native example tools run with the CLI's bundled Python. Separate commands such as python3 refund_service.py ledger use host Python 3.10+, which is not installed by the CLI. On a Mac without a configured host Python, invoking python3 may offer to install Apple's Command Line Tools. Prepare a host Python before following the refund guide's ledger and receipt-check commands; the no-tool quickstart does not need one.

Configure a local workspace

Export your provider key in the shell and initialize the example:

export OPENAI_API_KEY="<your-openai-api-key>"
actspan init workspace.yaml
actspan validate workspace.yaml --strict-env
actspan preview workspace.yaml --format json

A new local workspace gets .actspan.env containing the portal setting:

ACTSPAN_PORTAL_DISABLED=1

The provider key stays in your shell. Do not put real keys in workspace YAML or commit them to Git. The export applies to the current shell session; export it again in a new shell before another live provider call.

Init preserves existing environment files and explicit portal settings. If it reports a parent environment file, review that file before creating a different local configuration. Shell variables take precedence over the generated portal setting. Load custom environment files into your shell before later commands.

Expected: validation accepts the workspace, and preview shows its execution plan without a provider call. These checks do not establish model access, credentials or quota. Evidence stays local in this setup. Shared reporting can be enabled later.

If your handoff supplies Python packages

Use the installation notes supplied with that handoff. Core actspan==0.2.0 requires the independently packaged Anthropic runtime even when your first workflow uses OpenAI. The handoff must therefore include that dependency or provide access to the configured private package index. A single core wheel with no dependency access is not a complete offline installer.

Create a separate virtual environment, install the exact supplied packages and run python -m pip check before actspan --version. Do not replace the supplied version with an older pilot package or assume it is available from public PyPI.

If installation fails

Symptom Next step
actspan is not found Export the installed command directory on PATH, or run ~/.local/bin/actspan --version.
Wrong CPU or operating system Request the matching archive from your Actspan contact.
Missing provider dependency Use the package access or complete wheelhouse supplied with your handoff.
Old version prints Check command -v actspan, activate the intended environment, and review your PATH.
Missing examples Extract the matching examples archive; the CLI archive is separate.

Next step

Run your first agent, then read the core concepts. Existing users migrating an older workspace can consult the migration guide.