primitive
Table of Contents
Installation
pip install primitive
Configuration
Authenticate
primitive config
Register your Hardware
primitive hardware register
License
primitive is distributed under the terms of the MIT license.
Development Setup
For Primitive engineers, you may have these steps completed.
Python Setup
# install required libs for macos
xcode-select --install
# install brew
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
# install fish
brew install fish
echo /usr/local/bin/fish | sudo tee -a /etc/shells
chsh -s /usr/local/bin/fish
# install fisher
brew install fisher
fisher install jorgebucaran/nvm.fish
# install git
brew install git
# set global info
git config --global user.email "<user@email.com>"
git config --global user.name “<firstName lastName>”
# install make
brew install make
fish_add_path /opt/homebrew/opt/make/libexec/gnubin
# install uv
curl -LsSf https://astral.sh/uv/install.sh | sh
uv python install
fish_add_path "$(uv python dir)/bin"
Repository Setup
Clone and run setup.
cd ~/Development/primitivecorp/
git clone git@github.com:primitivecorp/platform.git
cd platform/cli
make install
With the kind cluster running (make up from the repo root), configure the CLI for local use.
# bash or zsh
source .venv/bin/activate
# fish
source .venv/bin/activate.fish
primitive --host localhost:8000 config --transport http
You can find or create a Primitive API token at http://localhost:3000/account/tokens
Please enter your Primitive API token: # create a token and copy the value here
Config created at '/Users/<user>/.config/primitive/credentials.json' on host 'localhost:8000'
# verify the configuration worked via
primitive --host localhost:8000 whoami
Logged in as <username>
Release Process
Version is defined in src/primitive/__about__.py. Bump it, merge to main, and CI handles the rest.
# From the cli/ directory:
make release # patch bump (0.2.x → 0.2.x+1)
make release BUMP=minor # minor bump (0.x.y → 0.x+1.0)
make release BUMP=major # major bump (x.y.z → x+1.0.0)
# Or from the monorepo root:
make cli-release # patch bump
make cli-release BUMP=minor # minor bump
make cli-release BUMP=major # major bump
After merging to main, the CLI: Publish workflow automatically:
- Detects the version change in
src/primitive/__about__.py - Creates a git tag (
v0.2.x) - Creates a GitHub Release with auto-generated notes
- Builds and publishes to PyPI via trusted publishing (OIDC)
Release files for primitive 0.4.56
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 | |
|---|---|---|---|---|
| primitive-0.4.56.tar.gz | 639.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| primitive-0.4.56-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / primitive-0.4.56.tar.gz
| Download URL | primitive-0.4.56.tar.gz |
|---|---|
| Size | 639.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fac2d5f38329ce7c0e14248c5d5336f05ceef46801749fecebee643dab26a0b0
|
|
BLAKE2b-256 checksum How to use checksums |
08ef1b0e3de5b21973c6abb0d7dd9f76064a70b70fe99a31f9769fd64677ce20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / primitive-0.4.56-py3-none-any.whl
| Download URL | primitive-0.4.56-py3-none-any.whl |
|---|---|
| Size | 432.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
79bd4f64c74ab5ec1fe282e0e40c284da6c61623a54ab31dd47845b135d8ac8f
|
|
BLAKE2b-256 checksum How to use checksums |
c7c583d504b9766219b9035478034101ffdf434d369811ed3ced62b431d02c84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for primitive 0.4.56
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for primitive-0.4.56.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA 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.
