npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@basis-theory-labs/cli

v4.3.0

Published

Basis Theory CLI tool

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

armsteadj1armsteadj1davi.basistheorydavi.basistheorybt-platformbt-platformjleon15jleon15

Keywords

basistheoryclilogs

Readme

Basis Theory CLI

Version Release

Basis Theory CLI tool

Make sure to either have a BT_MANAGEMENT_KEY env var exported or pass a management-key flag to the commands.

Usage

$ npm install -g @basis-theory-labs/cli
$ bt COMMAND
running command...
$ bt (--version)
@basis-theory-labs/cli/4.3.0 linux-x64 node-v22.23.3
$ bt --help [COMMAND]
USAGE
  $ bt COMMAND
...

Commands

bt applications

List Applications. Requires application:read Management Application permission

USAGE
  $ bt applications -x <value> [-p <value>]

FLAGS
  -p, --page=<value>            [default: 1] Applications list page to fetch
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy

DESCRIPTION
  List Applications. Requires `application:read` Management Application permission

EXAMPLES
  $ bt applications

See code: dist/commands/applications/index.ts

bt applications create

Creates a new Application. Requires application:create Management Application permission

USAGE
  $ bt applications create -x <value> [-n <value>] [-p <value>] [-t private|public|management] [-z <value>]

FLAGS
  -n, --name=<value>            name of the Application
  -p, --permission=<value>...   permission(s) to use in the Application
  -t, --type=<option>           type of the Application
                                <options: private|public|management>
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy
  -z, --template=<value>        template ID to create the application with

DESCRIPTION
  Creates a new Application. Requires `application:create` Management Application permission

EXAMPLES
  $ bt applications create

bt applications delete ID

Deletes a Application. Requires application:delete Management Application permissions

USAGE
  $ bt applications delete ID -x <value> [-y]

ARGUMENTS
  ID  Application id to delete

FLAGS
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy
  -y, --yes                     auto confirm the operation

DESCRIPTION
  Deletes a Application. Requires `application:delete` Management Application permissions

EXAMPLES
  $ bt applications delete 03858bf5-32d3-4a2e-b74b-daeea0883bca

bt applications update ID

Updates a new Application. Requires application:update Management Application permission

USAGE
  $ bt applications update ID -x <value> [-n <value>] [-p <value>]

ARGUMENTS
  ID  Application id to update

FLAGS
  -n, --name=<value>            name of the Application
  -p, --permission=<value>...   permission(s) to use in the Application
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy

DESCRIPTION
  Updates a new Application. Requires `application:update` Management Application permission

EXAMPLES
  $ bt applications update

bt proxies

List Proxies. Requires proxy:read Management Application permission

USAGE
  $ bt proxies -x <value> [-p <value>]

FLAGS
  -p, --page=<value>            [default: 1] Proxies list page to fetch
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy

DESCRIPTION
  List Proxies. Requires `proxy:read` Management Application permission

EXAMPLES
  $ bt proxies

See code: dist/commands/proxies/index.ts

bt proxies create

Creates a new Pre-Configured Proxy. Requires proxy:create Management Application permission

USAGE
  $ bt proxies create -x <value> [-n <value>] [-u <value>] [-q <value>] [-s <value>] [-i <value>] [-c <value>] [-a]
    [--request-transform-image node-bt|node22|node24] [--request-transform-package-json <value>]
    [--request-transform-timeout <value>] [--request-transform-warm-concurrency <value>] [--request-transform-resources
    standard|large|xlarge] [--request-transform-permissions <value>] [--response-transform-image node-bt|node22|node24]
    [--response-transform-package-json <value>] [--response-transform-timeout <value>]
    [--response-transform-warm-concurrency <value>] [--response-transform-resources standard|large|xlarge]
    [--response-transform-permissions <value>] [--no-wait]

FLAGS
  -a, --[no-]require-auth                        whether the Proxy requires Basis Theory authentication to be invoked.
                                                 Default: true
  -c, --configuration=<value>                    path to configuration file (.env format) to use in the Proxy
  -i, --application-id=<value>                   application ID to use in the Proxy
  -n, --name=<value>                             name of the Proxy
  -q, --request-transform-code=<value>           path to JavaScript file containing a Request Transform code
  -s, --response-transform-code=<value>          path to JavaScript file containing a Response Transform code
  -u, --destination-url=<value>                  URL to which requests will be proxied
  -x, --management-key=<value>                   (required) management key used for connecting with the reactor / proxy
  --no-wait                                      do not wait for proxy to be ready (requires at least one transform with
                                                 node22 | node24)
  --request-transform-image=<option>             request-transform runtime image (node-bt|node22|node24)
                                                 <options: node-bt|node22|node24>
  --request-transform-package-json=<value>       path to runtime package.json JSON file (top-level dependencies
                                                 required; supports resolutions or overrides fallback; pinned versions
                                                 required) (node22 | node24 only)
  --request-transform-permissions=<value>...     request-transform permission to grant, repeatable (node22 | node24
                                                 only)
  --request-transform-resources=<option>         request-transform resource tier (node22 | node24 only)
                                                 <options: standard|large|xlarge>
  --request-transform-timeout=<value>            request-transform timeout in seconds, 10-30 (node22 | node24 only)
  --request-transform-warm-concurrency=<value>   request-transform warm concurrency, 0-1 (node22 | node24 only)
  --response-transform-image=<option>            response-transform runtime image (node-bt|node22|node24)
                                                 <options: node-bt|node22|node24>
  --response-transform-package-json=<value>      path to runtime package.json JSON file (top-level dependencies
                                                 required; supports resolutions or overrides fallback; pinned versions
                                                 required) (node22 | node24 only)
  --response-transform-permissions=<value>...    response-transform permission to grant, repeatable (node22 | node24
                                                 only)
  --response-transform-resources=<option>        response-transform resource tier (node22 | node24 only)
                                                 <options: standard|large|xlarge>
  --response-transform-timeout=<value>           response-transform timeout in seconds, 10-30 (node22 | node24 only)
  --response-transform-warm-concurrency=<value>  response-transform warm concurrency, 0-1 (node22 | node24 only)

DESCRIPTION
  Creates a new Pre-Configured Proxy. Requires `proxy:create` Management Application permission

EXAMPLES
  Create a proxy without transforms

    $ bt proxies create --name "My Proxy" --destination-url https://api.example.com

  Create a proxy with legacy runtime transforms

    $ bt proxies create --name "My Proxy" --destination-url https://api.example.com --request-transform-code \
      ./request.js --request-transform-image node-bt --application-id <application-id>

  Create a proxy with node22 transforms

    $ bt proxies create --name "My Proxy" --destination-url https://api.example.com --request-transform-code \
      ./request.js --request-transform-image node22 --response-transform-code ./response.js --response-transform-image \
      node22

  Create a proxy with node22 transforms and all runtime options

    $ bt proxies create --name "My Proxy" --destination-url https://api.example.com --configuration ./config.env \
      --require-auth --request-transform-code ./request.js --request-transform-image node22 \
      --request-transform-timeout 10 --request-transform-warm-concurrency 0 --request-transform-resources standard \
      --request-transform-package-json ./request/package.json --request-transform-permissions token:read \
      --response-transform-code ./response.js --response-transform-image node22 --response-transform-timeout 10 \
      --response-transform-warm-concurrency 0 --response-transform-resources standard \
      --response-transform-package-json ./response/package.json --response-transform-permissions token:read

bt proxies delete ID

Deletes a Proxy. Requires proxy:delete Management Application permissions

USAGE
  $ bt proxies delete ID -x <value> [-y]

ARGUMENTS
  ID  Proxy id to delete

FLAGS
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy
  -y, --yes                     auto confirm the operation

DESCRIPTION
  Deletes a Proxy. Requires `proxy:delete` Management Application permissions

EXAMPLES
  $ bt proxies delete 03858bf5-32d3-4a2e-b74b-daeea0883bca

bt proxies logs [ID]

Legacy tunnel-based Proxy Transform logs. Opens a local tunnel and updates logging configuration. For v2/runtime debugging, use bt proxies logs tail <id> or bt proxies logs read <id>. Requires proxy:update Management Application permissions

USAGE
  $ bt proxies logs [ID] -x <value> [-p <value>]

ARGUMENTS
  ID  Proxy id to connect to

FLAGS
  -p, --port=<value>            [default: 8220] port to listen for incoming logs
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy

DESCRIPTION
  Legacy tunnel-based Proxy Transform logs. Opens a local tunnel and updates logging configuration. For v2/runtime
  debugging, use `bt proxies logs tail <id>` or `bt proxies logs read <id>`. Requires `proxy:update` Management
  Application permissions

EXAMPLES
  $ bt proxies logs

  $ bt proxies logs 03858bf5-32d3-4a2e-b74b-daeea0883bca

  $ bt proxies logs 03858bf5-32d3-4a2e-b74b-daeea0883bca -p 3000

bt proxies logs read ID

Read a fixed window of Proxy runtime logs through Events and exit. Requires event:read and runtime logging already enabled.

USAGE
  $ bt proxies logs read ID -x <value> [--since <value>] [--until <value>] [--format pretty|json|json-pretty]

ARGUMENTS
  ID  Proxy id

FLAGS
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy
  --format=<option>             [default: pretty] pretty: readable logs; json: compact objects; json-pretty: indented
                                objects. Entries are separated by blank lines; colors are enabled in terminals
                                <options: pretty|json|json-pretty>
  --since=<value>               window start: positive duration (30s, 5m, 2h, 1d, 1w) or ISO timestamp with timezone;
                                defaults to five minutes before the end
  --until=<value>               window end (exclusive): positive duration or ISO timestamp with timezone; defaults to
                                command start

DESCRIPTION
  Read a fixed window of Proxy runtime logs through Events and exit. Requires `event:read` and runtime logging already
  enabled.

  Defaults to the five minutes preceding --until, or command start when --until is omitted. Explicit relative values use
  command-start time. Both request and response transforms are included and distinguished. Windows include their start
  and exclude their end, filtering event batch timestamps rather than individual record occurrence times. Each matching
  batch is expanded in record sequence; flattened output has no global chronological ordering. History is tenant-limited
  (24 hours by default, at most 30 days); the API clamps unavailable history. Indexing is asynchronous and pagination is
  not a snapshot, so empty or exhausted results do not prove complete coverage. Large windows may hit bounded work
  limits and fail with partial output. Application logs come from the injected `logger`, not arbitrary stdout or
  `console.log`; collection requires resource opt-in and the platform runtime-log gate. Does not enable logging or open
  a tunnel.

EXAMPLES
  $ bt proxies logs read 03858bf5-32d3-4a2e-b74b-daeea0883bca --since 1h --until 30m

  $ bt proxies logs read 03858bf5-32d3-4a2e-b74b-daeea0883bca --since 2026-10-01T10:00:00Z --until 2026-10-01T10:15:00Z --format json

bt proxies logs tail ID

Tail Proxy runtime logs through Events. Requires event:read and runtime logging already enabled.

USAGE
  $ bt proxies logs tail ID -x <value> [--since <value>] [--format pretty|json|json-pretty]

ARGUMENTS
  ID  Proxy id

FLAGS
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy
  --format=<option>             [default: pretty] pretty: readable logs; json: compact objects; json-pretty: indented
                                objects. Entries are separated by blank lines; colors are enabled in terminals
                                <options: pretty|json|json-pretty>
  --since=<value>               include initial history from a positive duration (30s, 5m, 2h, 1d, 1w) or ISO timestamp
                                with timezone; omitted means watch from command start

DESCRIPTION
  Tail Proxy runtime logs through Events. Requires `event:read` and runtime logging already enabled.

  Starts watching from command time. Supply --since to retrieve initial history before following new logs. Polls every
  five seconds with a rolling five-minute overlap that never reaches before the requested start. Both request and
  response transforms are included and distinguished. Time windows filter event batches, not individual record
  occurrence times; a newly arriving batch can contain records that occurred before command start. History is
  tenant-limited (24 hours by default, at most 30 days); the API clamps unavailable history. Large initial windows may
  hit bounded work limits and fail with partial output. Visibility is delayed and best-effort; output has no durable
  resume or global chronological ordering. Application logs come from the injected `logger`, not arbitrary stdout or
  `console.log`; collection requires resource opt-in and the platform runtime-log gate. Silence does not distinguish an
  idle resource, a wrong ID, disabled collection, or delayed indexing. Runs until interrupted, output closes, or an
  error occurs.

EXAMPLES
  $ bt proxies logs tail 03858bf5-32d3-4a2e-b74b-daeea0883bca

  $ bt proxies logs tail 03858bf5-32d3-4a2e-b74b-daeea0883bca --since 30m --format json

bt proxies update ID

Updates an existing Pre-Configured Proxy. Requires proxy:update Management Application permission

USAGE
  $ bt proxies update ID -x <value> [-n <value>] [-u <value>] [-q <value>] [-s <value>] [-i <value>] [-c <value>]
    [-a] [--request-transform-image node-bt|node22|node24] [--request-transform-package-json <value>]
    [--request-transform-timeout <value>] [--request-transform-warm-concurrency <value>] [--request-transform-resources
    standard|large|xlarge] [--request-transform-permissions <value>] [--response-transform-image node-bt|node22|node24]
    [--response-transform-package-json <value>] [--response-transform-timeout <value>]
    [--response-transform-warm-concurrency <value>] [--response-transform-resources standard|large|xlarge]
    [--response-transform-permissions <value>] [--no-wait] [-w] [-l]

ARGUMENTS
  ID  Proxy id to update

FLAGS
  -a, --[no-]require-auth                        whether the Proxy requires Basis Theory authentication to be invoked.
                                                 Default: true
  -c, --configuration=<value>                    path to configuration file (.env format) to use in the Proxy
  -i, --application-id=<value>                   application ID to use in the Proxy
  -l, --logs                                     Start logs server after update
  -n, --name=<value>                             name of the Proxy
  -q, --request-transform-code=<value>           path to JavaScript file containing a Request Transform code
  -s, --response-transform-code=<value>          path to JavaScript file containing a Response Transform code
  -u, --destination-url=<value>                  URL to which requests will be proxied
  -w, --watch                                    Watch for changes in informed files
  -x, --management-key=<value>                   (required) management key used for connecting with the reactor / proxy
  --no-wait                                      do not wait for proxy to be ready (requires at least one transform with
                                                 node22 | node24)
  --request-transform-image=<option>             request-transform runtime image (node-bt|node22|node24)
                                                 <options: node-bt|node22|node24>
  --request-transform-package-json=<value>       path to runtime package.json JSON file (top-level dependencies
                                                 required; supports resolutions or overrides fallback; pinned versions
                                                 required) (node22 | node24 only)
  --request-transform-permissions=<value>...     request-transform permission to grant, repeatable (node22 | node24
                                                 only)
  --request-transform-resources=<option>         request-transform resource tier (node22 | node24 only)
                                                 <options: standard|large|xlarge>
  --request-transform-timeout=<value>            request-transform timeout in seconds, 10-30 (node22 | node24 only)
  --request-transform-warm-concurrency=<value>   request-transform warm concurrency, 0-1 (node22 | node24 only)
  --response-transform-image=<option>            response-transform runtime image (node-bt|node22|node24)
                                                 <options: node-bt|node22|node24>
  --response-transform-package-json=<value>      path to runtime package.json JSON file (top-level dependencies
                                                 required; supports resolutions or overrides fallback; pinned versions
                                                 required) (node22 | node24 only)
  --response-transform-permissions=<value>...    response-transform permission to grant, repeatable (node22 | node24
                                                 only)
  --response-transform-resources=<option>        response-transform resource tier (node22 | node24 only)
                                                 <options: standard|large|xlarge>
  --response-transform-timeout=<value>           response-transform timeout in seconds, 10-30 (node22 | node24 only)
  --response-transform-warm-concurrency=<value>  response-transform warm concurrency, 0-1 (node22 | node24 only)

DESCRIPTION
  Updates an existing Pre-Configured Proxy. Requires `proxy:update` Management Application permission

EXAMPLES
  Update a proxy destination URL

    $ bt proxies update <proxy-id> --destination-url https://api.example.com

  Update a proxy with legacy runtime transforms

    $ bt proxies update <proxy-id> --request-transform-code ./request.js --request-transform-image node-bt \
      --application-id <application-id>

  Update a proxy with node22 transforms

    $ bt proxies update <proxy-id> --request-transform-code ./request.js --request-transform-image node22 \
      --response-transform-code ./response.js --response-transform-image node22

  Update a proxy with node22 transforms and all runtime options

    $ bt proxies update <proxy-id> --name "My Proxy" --destination-url https://api.example.com --configuration \
      ./config.env --require-auth --request-transform-code ./request.js --request-transform-image node22 \
      --request-transform-timeout 10 --request-transform-warm-concurrency 0 --request-transform-resources standard \
      --request-transform-package-json ./request/package.json --request-transform-permissions token:read \
      --response-transform-code ./response.js --response-transform-image node22 --response-transform-timeout 10 \
      --response-transform-warm-concurrency 0 --response-transform-resources standard \
      --response-transform-package-json ./response/package.json --response-transform-permissions token:read

bt reactors

List Reactors. Requires reactor:read Management Application permission

USAGE
  $ bt reactors -x <value> [-p <value>]

FLAGS
  -p, --page=<value>            [default: 1] Reactors list page to fetch
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy

DESCRIPTION
  List Reactors. Requires `reactor:read` Management Application permission

EXAMPLES
  $ bt reactors

See code: dist/commands/reactors/index.ts

bt reactors create

Creates a new Reactor. Requires reactor:create Management Application permission

USAGE
  $ bt reactors create -x <value> [-n <value>] [-c <value>] [-i <value>] [-r <value>] [--image node-bt|node22|node24]
    [--package-json <value>] [--timeout <value>] [--warm-concurrency <value>] [--resources standard|large|xlarge]
    [--permissions <value>] [--no-wait] [--async]

FLAGS
  -c, --configuration=<value>   path to configuration file (.env format) to use in the Reactor
  -i, --application-id=<value>  application ID to use in the Reactor
  -n, --name=<value>            name of the Reactor
  -r, --code=<value>            path to JavaScript file containing the Reactor code
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy
  --[no-]async                  execute Reactor invocations asynchronously (node22 | node24 only)
  --image=<option>              runtime image (node-bt|node22|node24)
                                <options: node-bt|node22|node24>
  --no-wait                     do not wait for resource provisioning to complete
  --package-json=<value>        path to runtime package.json JSON file (top-level dependencies required; supports
                                resolutions or overrides fallback; pinned versions required) (node22 | node24 only)
  --permissions=<value>...      permission to grant, repeatable (node22 | node24 only)
  --resources=<option>          resource tier (node22 | node24 only, default: standard)
                                <options: standard|large|xlarge>
  --timeout=<value>             timeout in seconds, 10-900 (node22 | node24 only; maximum 30 when runtime async is
                                disabled; default: 10)
  --warm-concurrency=<value>    number of warm instances, 0-1 (node22 | node24 only, default: 0)

DESCRIPTION
  Creates a new Reactor. Requires `reactor:create` Management Application permission

EXAMPLES
  Create a reactor with legacy runtime

    $ bt reactors create --name "My Reactor" --code ./reactor.js --image node-bt --application-id <application-id>

  Create a reactor with node22 runtime

    $ bt reactors create --name "My Reactor" --code ./reactor.js --image node22

  Create a reactor with node22 and all runtime options

    $ bt reactors create --name "My Reactor" --code ./reactor.js --configuration ./config.env --image node22 --async \
      --timeout 10 --warm-concurrency 0 --resources standard --package-json ./package.json --permissions token:read \
      --permissions token:create

bt reactors delete ID

Deletes a Reactor. Requires reactor:delete Management Application permissions

USAGE
  $ bt reactors delete ID -x <value> [-y]

ARGUMENTS
  ID  Reactor id to delete

FLAGS
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy
  -y, --yes                     auto confirm the operation

DESCRIPTION
  Deletes a Reactor. Requires `reactor:delete` Management Application permissions

EXAMPLES
  $ bt reactors delete 03858bf5-32d3-4a2e-b74b-daeea0883bca

bt reactors logs [ID]

Legacy tunnel-based Reactor logs. Opens a local tunnel and updates logging configuration. For v2/runtime debugging, use bt reactors logs tail <id> or bt reactors logs read <id>. Requires reactor:update Management Application permissions

USAGE
  $ bt reactors logs [ID] -x <value> [-p <value>]

ARGUMENTS
  ID  Reactor id to connect to

FLAGS
  -p, --port=<value>            [default: 8220] port to listen for incoming logs
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy

DESCRIPTION
  Legacy tunnel-based Reactor logs. Opens a local tunnel and updates logging configuration. For v2/runtime debugging,
  use `bt reactors logs tail <id>` or `bt reactors logs read <id>`. Requires `reactor:update` Management Application
  permissions

EXAMPLES
  $ bt reactors logs

  $ bt reactors logs 03858bf5-32d3-4a2e-b74b-daeea0883bca

  $ bt reactors logs 03858bf5-32d3-4a2e-b74b-daeea0883bca -p 3000

bt reactors logs read ID

Read a fixed window of Reactor runtime logs through Events and exit. Requires event:read and runtime logging already enabled.

USAGE
  $ bt reactors logs read ID -x <value> [--since <value>] [--until <value>] [--format pretty|json|json-pretty]

ARGUMENTS
  ID  Reactor id

FLAGS
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy
  --format=<option>             [default: pretty] pretty: readable logs; json: compact objects; json-pretty: indented
                                objects. Entries are separated by blank lines; colors are enabled in terminals
                                <options: pretty|json|json-pretty>
  --since=<value>               window start: positive duration (30s, 5m, 2h, 1d, 1w) or ISO timestamp with timezone;
                                defaults to five minutes before the end
  --until=<value>               window end (exclusive): positive duration or ISO timestamp with timezone; defaults to
                                command start

DESCRIPTION
  Read a fixed window of Reactor runtime logs through Events and exit. Requires `event:read` and runtime logging already
  enabled.

  Defaults to the five minutes preceding --until, or command start when --until is omitted. Explicit relative values use
  command-start time. Windows include their start and exclude their end, filtering event batch timestamps rather than
  individual record occurrence times. Each matching batch is expanded in record sequence; flattened output has no global
  chronological ordering. History is tenant-limited (24 hours by default, at most 30 days); the API clamps unavailable
  history. Indexing is asynchronous and pagination is not a snapshot, so empty or exhausted results do not prove
  complete coverage. Large windows may hit bounded work limits and fail with partial output. Application logs come from
  the injected `logger`, not arbitrary stdout or `console.log`; collection requires resource opt-in and the platform
  runtime-log gate. Does not enable logging or open a tunnel.

EXAMPLES
  $ bt reactors logs read 03858bf5-32d3-4a2e-b74b-daeea0883bca --since 1h --until 30m

  $ bt reactors logs read 03858bf5-32d3-4a2e-b74b-daeea0883bca --since 2026-10-01T10:00:00Z --until 2026-10-01T10:15:00Z --format json

bt reactors logs tail ID

Tail Reactor runtime logs through Events. Requires event:read and runtime logging already enabled.

USAGE
  $ bt reactors logs tail ID -x <value> [--since <value>] [--format pretty|json|json-pretty]

ARGUMENTS
  ID  Reactor id

FLAGS
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy
  --format=<option>             [default: pretty] pretty: readable logs; json: compact objects; json-pretty: indented
                                objects. Entries are separated by blank lines; colors are enabled in terminals
                                <options: pretty|json|json-pretty>
  --since=<value>               include initial history from a positive duration (30s, 5m, 2h, 1d, 1w) or ISO timestamp
                                with timezone; omitted means watch from command start

DESCRIPTION
  Tail Reactor runtime logs through Events. Requires `event:read` and runtime logging already enabled.

  Starts watching from command time. Supply --since to retrieve initial history before following new logs. Polls every
  five seconds with a rolling five-minute overlap that never reaches before the requested start. Time windows filter
  event batches, not individual record occurrence times; a newly arriving batch can contain records that occurred before
  command start. History is tenant-limited (24 hours by default, at most 30 days); the API clamps unavailable history.
  Large initial windows may hit bounded work limits and fail with partial output. Visibility is delayed and best-effort;
  output has no durable resume or global chronological ordering. Application logs come from the injected `logger`, not
  arbitrary stdout or `console.log`; collection requires resource opt-in and the platform runtime-log gate. Silence does
  not distinguish an idle resource, a wrong ID, disabled collection, or delayed indexing. Runs until interrupted, output
  closes, or an error occurs.

EXAMPLES
  $ bt reactors logs tail 03858bf5-32d3-4a2e-b74b-daeea0883bca

  $ bt reactors logs tail 03858bf5-32d3-4a2e-b74b-daeea0883bca --since 30m --format json

bt reactors update ID

Updates an existing Reactor. Requires reactor:update Management Application permission

USAGE
  $ bt reactors update ID -x <value> [-n <value>] [-c <value>] [-i <value>] [-r <value>] [--image
    node-bt|node22|node24] [--package-json <value>] [--timeout <value>] [--warm-concurrency <value>] [--resources
    standard|large|xlarge] [--permissions <value>] [--no-wait] [--async] [-w] [-l]

ARGUMENTS
  ID  Reactor id to update

FLAGS
  -c, --configuration=<value>   path to configuration file (.env format) to use in the Reactor
  -i, --application-id=<value>  application ID to use in the Reactor
  -l, --logs                    Start logs server after update
  -n, --name=<value>            name of the Reactor
  -r, --code=<value>            path to JavaScript file containing the Reactor code
  -w, --watch                   Watch for changes in supplied code, configuration, and runtime package files
  -x, --management-key=<value>  (required) management key used for connecting with the reactor / proxy
  --[no-]async                  execute Reactor invocations asynchronously (node22 | node24 only)
  --image=<option>              runtime image (node-bt|node22|node24)
                                <options: node-bt|node22|node24>
  --no-wait                     do not wait for resource provisioning to complete
  --package-json=<value>        path to runtime package.json JSON file (top-level dependencies required; supports
                                resolutions or overrides fallback; pinned versions required) (node22 | node24 only)
  --permissions=<value>...      permission to grant, repeatable (node22 | node24 only)
  --resources=<option>          resource tier (node22 | node24 only, default: standard)
                                <options: standard|large|xlarge>
  --timeout=<value>             timeout in seconds, 10-900 (node22 | node24 only; maximum 30 when runtime async is
                                disabled; default: 10)
  --warm-concurrency=<value>    number of warm instances, 0-1 (node22 | node24 only, default: 0)

DESCRIPTION
  Updates an existing Reactor. Requires `reactor:update` Management Application permission

EXAMPLES
  Update a reactor with legacy runtime

    $ bt reactors update <reactor-id> --code ./reactor.js --image node-bt --application-id <application-id>

  Update a reactor with node22 runtime

    $ bt reactors update <reactor-id> --code ./reactor.js --image node22

  Watch a node22 reactor for code, configuration, and dependency changes

    $ bt reactors update <reactor-id> --code ./reactor.js --configuration ./config.env --package-json ./package.json \
      --image node22 --watch

  Update a reactor with node22 and all runtime options

    $ bt reactors update <reactor-id> --name "My Reactor" --code ./reactor.js --configuration ./config.env --image \
      node22 --async --timeout 10 --warm-concurrency 0 --resources standard --package-json ./package.json \
      --permissions token:read --permissions token:create