actionrail-console

ActionRail Console

The local, single-user ActionRail control plane and web Console.

This package is currently in public beta. ActionRail v1 is planned for August 2026.

The wheel includes the compiled React application, Django API, migrations, and SQLite storage. It binds to localhost and does not require signup or a user account. Agent API keys are returned once when an agent is created and are stored only as salted hashes.

python -m pip install actionrail_console-0.1.0b9-py3-none-any.whl
actionrail-console

Data is stored in ~/.actionrail/ by default. Run actionrail-console --help to choose another port or data directory.

The Console sends one anonymous console_started event per process and one exact usage_summary snapshot per UTC day. The summary reports only totals for configured and active agents, observed and evaluated actions, and monitored, allowed, blocked, or held outcomes. It does not contain agent IDs or names, tool names, Sources, rules, arguments, individual decisions, credentials, paths, or errors. Disable it with ACTIONRAIL_TELEMETRY_DISABLED=1. DO_NOT_TRACK=1 and CI=1 are also honored.

Distribution boundary

The OSS Console stores agents and sources in one implicit local scope. Hosted distributions can set ACTIONRAIL_SCOPE_RESOLVER to a dotted callable that accepts the Django request, authenticates it, verifies access to the selected workspace, and returns a stable scope id (128 characters or fewer). All console queries and writes are filtered through that resolver.

Agent-runtime endpoints do not trust browser workspace state. The agent API key selects the owning scope for rules, source configuration, reports, and reviews. This keeps tenancy out of feature views and lets Cloud own users, organizations, memberships, and workspace selection without forking the OSS data model.