Hosted CLI workflows

Use tachyonic sandbox for a Linux job and tachyonic runtime for a security test of an authorized agent endpoint. Both use the same platform account and workspace credentials. Sandbox commands require CLI 0.18.0 or later.

Login

tachyonic login
tachyonic whoami

Approve the device flow in the browser. The CLI stores a workspace-bound device key locally. To supply an existing key use the hidden prompt:

tachyonic login --with-key

For CI, supply TACHYONIC_API_KEY as a secret environment variable. Do not put the key in a command argument or URL. See Authentication.

Run a sandbox job

tachyonic sandbox create --budget 30m
tachyonic sandbox exec sb_example -- python3 --version
tachyonic sandbox rm sb_example

Replace sb_example with the returned ID. See Sandbox quickstart.

Test an agent endpoint

tachyonic runtime start --target https://your-agent.example.com
tachyonic runtime watch <runtime-id>
tachyonic runtime artifacts <runtime-id>

Inspect findings and artifacts in the console. The default runtime path supports signed evidence; regional availability does not establish signing or retention for that path. Verify the exact bundle you will use in review. See Runtimes.

Logout

tachyonic logout

Logout revokes a device-created key and removes local login. Use tachyonic logout --keep-key to clear local login without revoking it. Console-created keys keep their configured scopes and must be revoked in the console when no longer needed.

Existing scan callers

Older local-scanning and upload commands remain compatibility surfaces. They are hidden from top-level help. Use the public sandbox and runtime workflows for new hosted integrations. See CLI reference.