Skip to main content

acsetra — the Runner CLI

A thin client for building and running hosted Runner apps from your terminal. It holds no framework logic: every authoring command serializes to {op, args} and is POSTed to the hosted API, where validation, reserved-code guards, and doctor compiles all run server-side. You get the grammar of the framework, not its implementation.

Install

pipx install acsetra        # recommended (isolated)
# or: pip install acsetra
runner signin

Exposes three console scripts — runner (primary), acsetra (brand alias), and r (continuity with ./r).

Quick start

runner signin                              # device-flow sign-in; caches a token
runner whoami                              # you + every org you can reach, with access (owner/edit/view)
runner app create <org>.crm --label "CRM"  # create an app scope in THAT org (any org you can edit)
runner set put <org>.crm contacts ada --json '{"role":"eng"}'
runner read contacts -S <org>.crm
runner doctor <org>.crm && runner compile <org>.crm
runner auth <org>.crm                      # gate the app behind home.acsetra.com sign-in
runner dev <org>.crm                       # open the app's hosted surface in your browser
runner open <org>.crm                      # reuse/create its paired Chrome tab
runner notify <org>.crm --title Ready
runner tabs

Every command names its target by full scope path <org>.<app> — the first segment is the org, and that is what routes the command. Nothing is pinned per project: you may read every org you belong to and author in any org where your share access is edit (granted in Runner Command → Share). A bare leaf (crm) only resolves against the token's home org — runner use <slug> changes that default, but full paths never need it.

How it fits together

  • runner signin runs the OAuth device flow: it prints a URL + code, you approve in the browser, and the CLI caches a token at ~/.config/acsetra/credentials (0600).
  • runner docs pull writes CLAUDE.md + .runner/docs/* — concise doctrine and a framework model for Claude Code. Exact grammar always comes from runner <group> <subverb> --help, so it cannot drift from the installed client.
  • runner open, focus, notify, and tabs use the paired Runner Chrome extension. CLI and ChatGPT MCP write the same short-lived browser intents.
  • The hosted DB is the source of truth. Local files are instructions and mirrors, never runtime source. runner checkout produces disposable working copies under .tmp/ for grep and inspection; runner dev <app> just opens the live hosted surface in your browser.

Environment overrides

Var Meaning
ACSETRA_API_BASE hosted API origin (default https://home.acsetra.com)
ACSETRA_TOKEN bearer token (skips the cached credential)
ACSETRA_WORKSPACE home org slug for bare-leaf scopes (full <org>.<app> paths route themselves)
ACSETRA_SCOPE default app scope for -S-less commands

Run runner help for the full verb list.

Metadata

Release files for acsetra 0.2.13

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for acsetra 0.2.13
File Size Uploaded Provenance Actions
acsetra-0.2.13.tar.gz 32.3 kB Without provenance Details for acsetra-0.2.13.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for acsetra 0.2.13
File Interpreter ABI Platform Actions
acsetra-0.2.13-py3-none-any.whl Python 3 none any Details for acsetra-0.2.13-py3-none-any.whl

Total release size: 70.1 kB

Release files / acsetra-0.2.13.tar.gz

Download URL acsetra-0.2.13.tar.gz
Size 32.3 kB
Tags Source
SHA-256 checksum
How to use checksums
b313a9e05199218559388804565ed2286609033cc62f09b2c5ea399b3e62ac00
BLAKE2b-256 checksum
How to use checksums
ae7bae65ed16290d774b3f3b2a73756f8ba316d26d82900327db62947889ec24
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.7

Release files / acsetra-0.2.13-py3-none-any.whl

Download URL acsetra-0.2.13-py3-none-any.whl
Size 37.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cb49b240eb22b4b342b7f83cafc959a54d59f4e09cc31b8101a83c40ea4f49ca
BLAKE2b-256 checksum
How to use checksums
7a2e6a328e8aeba34dcb7ac2b985007244df49c816aaa2c7d3b47fe333fe48ce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.7

Security for acsetra 0.2.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.

Release history Release notifications | RSS feed

This release

0.2.13 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page