pickfit

BrowseDeveloper CLIs

atago

Tests real CLI behavior from YAML specs checking exit codes, output, files and terminals.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • Runtimes: Go 1.26.10 or later
  1. install atago via brew cask nao1215/tap/atago

    brew install --cask nao1215/tap/atago

Check that it works

atago --version

The output should contain “atago v0.25.2”.

First thing to try

cat > f1.atago.yaml <<'YAML'
version: "1"
suite:
  name: example
scenarios:
  - name: echo greets the world
    steps:
      - run:
          shell: true
          command: echo "hello atago"
      - assert:
          exit_code: 0
          stdout:
            contains: atago
          stderr:
            empty: true
YAML
cat > f2.atago.yaml <<'YAML'
version: "1"
suite:
  name: files
scenarios:
  - name: the generator writes the expected files
    steps:
      - run:
          shell: true
          command: mkdir -p site && echo "<html>hello</html>" > site/index.html
      - assert:
          file:
            path: site/index.html
            contains:
              - "<html"
YAML
cat > f3.atago.yaml <<'YAML'
version: "1"
suite:
  name: pty-test
scenarios:
  - name: the init wizard completes
    steps:
      - pty:
          command: sh -c 'printf "Project name: "; read name; echo "created $name/"'
          session:
            - expect: "Project name:"
            - send: "demo\n"
            - expect: "created demo/"
      - assert:
          exit_code: 0
YAML
cat > /tmp/prompt.sh <<'SH'
#!/bin/sh
printf "Project name: "
read name
echo "created $name/"
SH
chmod +x /tmp/prompt.sh
echo "setup done" && ls -lh *.atago.yaml
atago run f1.atago.yaml

Write a YAML spec file, then run it with atago run <spec>.atago.yaml.

Linux x86_64

You need first

  • Runtimes: Go 1.26.10 or later
  1. Download prebuilt linux_amd64 tarball from releases and install atago to ~/.local/bin

    mkdir -p ~/.local/bin /tmp/atago-dl && curl -fsSL -o /tmp/atago-dl/atago.tar.gz https://github.com/nao1215/atago/releases/download/v0.25.2/atago_0.25.2_linux_amd64.tar.gz && tar -xzf /tmp/atago-dl/atago.tar.gz -C /tmp/atago-dl && install -m 0755 /tmp/atago-dl/atago ~/.local/bin/atago && ~/.local/bin/atago --version

Check that it works

atago --version

The output should contain “atago v0.25.2”.

First thing to try

mkdir -p specs && cat > specs/f1.atago.yaml <<'YAML'
version: "1"
suite:
  name: example
scenarios:
  - name: echo greets the world
    steps:
      - run:
          shell: true
          command: echo "hello atago"
      - assert:
          exit_code: 0
          stdout:
            contains: atago
          stderr:
            empty: true
YAML
cat > specs/f2.atago.yaml <<'YAML'
version: "1"
suite:
  name: files-example
scenarios:
  - name: the generator writes the expected files
    steps:
      - run:
          shell: true
          command: mkdir -p site && echo "<html>hello</html>" > site/index.html && cat site/index.html
      - assert:
          file:
            path: site/index.html
            contains:
              - "<html"
YAML
cat > specs/f3.atago.yaml <<'YAML'
version: "1"
suite:
  name: pty-example
scenarios:
  - name: the init wizard completes
    steps:
      - pty:
          command: sh -c 'printf "Project name: "; read name; echo "created $name/"'
          session:
            - expect: "Project name:"
            - send: "demo\n"
            - expect: "created demo/"
      - assert:
          exit_code: 0
YAML
ls -la specs/ && cat specs/f1.atago.yaml
atago run specs/f1.atago.yaml

Write a YAML spec file, then run it with atago run <spec>.atago.yaml.

What it does

  • Drive interactive prompts and terminal UIs
    How to use it
    1. In a spec file, add a pty step with the command to run and a session list of expect and send entries.
    2. Add an assert step, for example exit_code: 0.
    3. Run the spec with atago run <spec>.atago.yaml.
    Tested
  • Record a real command run as a test spec
    How to use it
    1. Record a command with atago record --out <spec>.atago.yaml -- <command>.
    2. Replay the recorded spec with atago run <spec>.atago.yaml.
    Tested
  • Check a command's exit code, stdout and stderr
    Not shown working
  • Check generated files and compare snapshots
    Not shown working

How far pickfit got

macOS arm64

  1. Installs
  2. Starts
  3. 2 of 4 features work
  4. Works offline

Linux x86_64

  1. Installs
  2. Starts
  3. 1 of 4 features work
  4. Works offline

Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • Check exit code, stdout and stderr of a command
  • Check generated files and compare snapshots
  • Drive interactive prompts and TUIs via PTY
  • Record a real run into a test spec
  • Test CLI against a background server

An alternative to runn, venom, ShellSpec and Bats.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version v0.25.2

Differences the test machine hit

  • README: brew install --cask nao1215/tap/atago
    In the test: brew warns 'Calling `postflight` is deprecated! Use `postflight_steps` instead' but install still succeeds and binary is linked to /opt/homebrew/bin/atago

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version v0.25.2

Differences the test machine hit

  • README: go install github.com/nao1215/atago@latest (requires Go 1.26.10+); yay -S atago-bin; aqua g -i nao1215/atago; mise use -g aqua:nao1215/atago
    In the test: downloaded atago_0.25.2_linux_amd64.tar.gz from GitHub releases page (documented in README) and installed atago binary to ~/.local/bin
  • README: README wizard example uses a bare command without ': ' so needs no quoting
    In the test: quote a pty/run command value containing ': ' in double quotes or it fails to load with ATG2003

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.