Developers

The NexaFlow CLI.

Script the workspace from your terminal or from CI. Post a stand-up answer from a git hook, open a review from a pipeline, export a quarter of Decision Records to a file.

Getting started

Three commands in

  1. 01

    Install

    Available through npm, Homebrew and a single static binary for CI images that would rather not carry a runtime.

  2. 02

    Authenticate

    Device-code flow for humans, a scoped machine token for CI. Machine tokens are workspace-scoped and never carry admin rights by default.

  3. 03

    Script it

    Every command takes --json so output pipes into jq without parsing a table meant for people.

Reference

Commands that matter

`nexa standup post`
Post an answer to today’s thread, optionally reading from stdin
`nexa sprint status`
Current sprint health, drift and stuck tickets
`nexa review open`
Open an async review against a branch or a Figma frame
`nexa doc export`
Export docs and Decision Records to Markdown or JSON
`nexa webhook replay`
Replay a delivery by ID while debugging a consumer
`–json`
Machine-readable output on every command
FAQ

Questions we get asked

Can it run in CI without a browser?

Yes. Use a machine token rather than the device-code flow. Machine tokens are workspace-scoped and can be restricted per command group.

Is the CLI open source?

The CLI is closed, the SDKs it uses are open. Both are generated from the same schema as the public API.

Does it work offline?

No. Every command talks to the API. Draft your stand-up answer in a file and pipe it in when you reconnect.

Install it and post your first stand-up from a git hook.