spectackl
Command-line interface to the Spectackl Public REST API — built for AI agents and operators who need programmatic access to artifacts, scenes and task executions without going through the web UI.
pipx install spectackl # isolated venv, binary on PATH
# or
pip install spectackl
Upgrading
pipx install --force spectackl
--force rather than pipx upgrade, and rather than a bare pipx install. A bare
install leaves an existing app untouched (pip inside its venv reports "Requirement
already satisfied"), and pipx upgrade re-resolves whatever spec the app was first
installed from — so an app installed once from a local path or a pin will keep
reinstalling that, however many releases have been published since. --force
discards the venv and resolves the latest release from PyPI. Under pip, the
equivalent is pip install --upgrade spectackl.
Check what landed with spectackl --version. If it still reports the old number,
pip's index cache is stale — add --pip-args="--no-cache-dir".
Quick start
spectackl init --api-key spc_… --backend-url https://api.spectackl.ai --project my-project
spectackl artifact list --json
API keys are managed in the Spectackl Admin Console. init writes
.spectackl/settings.yaml in the current directory and a user-global
~/.config/spectackl/settings.yaml; both are created 0600 and neither should be
committed.
What it does
| Command | Purpose |
|---|---|
spectackl search <query> |
Hybrid full-text + semantic search across a project's content |
spectackl artifact |
Get, list, create and update artifacts |
spectackl relation |
Manage the artifact graph (INCLUDES, DOCUMENTS, DEPENDS_ON, …) |
spectackl context |
Inspect scenes (work contexts) and the artifacts they scope |
spectackl task |
Claim, progress and complete task executions |
spectackl assets sync |
Materialize the project's agents and skills into ./.claude/ |
spectackl rsync |
Reconcile artifact content with local files, in both directions |
spectackl daemon |
Run agent sessions on this machine |
Every command accepts --json for machine-readable output, and every command returns a
documented exit code — 0 success, 10 auth required, 20 validation, 30 not found,
40 upstream unavailable, and so on — so scripts can branch on failures precisely
rather than parsing text.
Designed for agents
Output is stable and parseable, errors are structured, and the exit-code scheme is part
of the public contract. spectackl assets sync writes agent and skill definitions in the
exact layout Claude Code reads, built from the same artifacts the platform provisions
into a sandbox — so an agent invoked on a workstation is the one that runs in production.
Requirements
- Python 3.10+
- A Spectackl tenant and an API key (
spc_prefix)
Documentation
Full guide: https://docs.spectackl.ai
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for spectackl 1.5.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| spectackl-1.5.13.tar.gz | 240.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| spectackl-1.5.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 426.1 kB
Release files / spectackl-1.5.13.tar.gz
| Download URL | spectackl-1.5.13.tar.gz |
|---|---|
| Size | 240.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
06f6fffc8875ac1fa8681ff6a1a981fab428e9d9db670f8bbfaaeeab79113f22
|
|
BLAKE2b-256 checksum How to use checksums |
ff5d4a43f50508e4f9ca093dbcbed0563e0b6f119c2e06ca0bde5161b613c341
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / spectackl-1.5.13-py3-none-any.whl
| Download URL | spectackl-1.5.13-py3-none-any.whl |
|---|---|
| Size | 185.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a5cba38928bfb0b87ab1532c74b9a57da9ecc57075be18b12d953439629497ae
|
|
BLAKE2b-256 checksum How to use checksums |
de0a72a09ac3a017aa078202476196a31adb7bf3b5a0eb403cdb6dd0367bf1b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for spectackl 1.5.13
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
