Skip to content

flow CLI v0.1.0

Choose a tag to compare

View all tags
@askmeidentity askmeidentity released this 01 Aug 17:41
cli-v0.1.0
043fc60

Send API requests from your terminal, and run the collections you already have in Arythmatic Flow.

No runtime required. These are standalone binaries — download, make executable, run. Nothing else to install.

Download

Platform File
macOS (Apple Silicon) flow-0.1.0-darwin-arm64
macOS (Intel) flow-0.1.0-darwin-x64
Linux (x64) flow-0.1.0-linux-x64
Linux (arm64) flow-0.1.0-linux-arm64
Windows (x64) flow-0.1.0-windows-x64.exe 
chmod +x flow-0.1.0-darwin-arm64
sudo mv flow-0.1.0-darwin-arm64 /usr/local/bin/flow
flow --version

Verify a download with shasum -a 256 -c SHA256SUMS.

Why use it

It reaches your machine. The web app sends requests through a server, so http://localhost:3000 has always meant the server's localhost. The CLI opens the connection from your own terminal — localhost means your localhost, hosts on your VPN are reachable, and nothing about the request leaves your machine.

flow get localhost:3000/health
flow post api.example.com/users --json '{"name":"Ada"}'
flow get localhost:8080/x -n 20          # min / median / p95 / max
flow get api.example.com/x --dry-run     # exactly what would be sent

curl's spellings work where curl has one — -H, -d, -i, -k, -o, and --fail exiting 22.

It knows your workspace. Get an API key from Workspace → Team → API Keys:

flow login                    # just the key; nothing else to look up
flow ls                       # your collections
flow run "Smoke tests"        # runs them from this machine

flow run exits non-zero if any request returns 4xx or 5xx, so it drops into CI with FLOW_API_KEY as the only secret.

Known limitations

  • flow run does not yet execute assertions or pre/post-request scripts. Requests are sent and their status reported, but it is not yet a substitute for a server-side collection run. Ad-hoc requests are unaffected.
  • Runs from the CLI are not recorded in history or collection-run reports.
  • The Windows binary is unsigned and will show a SmartScreen warning. macOS binaries are signed with a Developer ID and notarized by Apple, so they run without a Gatekeeper prompt.
  • The darwin-x64 build needs a CPU with AVX — every Intel Mac running macOS 11+ has it. On Apple Silicon use the arm64 build.
Assets 8
Loading