Getting started
Argos ships as a desktop app and a single-binary CLI. Both read the same workspace folder, so you can hack in the UI and re-run the same requests in CI without exporting anything.
Install the desktop app
Pre-built bundles are attached to every GitHub release.
- macOS:
Argos_<version>_aarch64.dmg(Apple Silicon). Intel builds ship on demand via therelease-darwin-x86_64workflow. - Windows:
Argos_<version>_x64-setup.exe(or the.msi). - Linux:
.deb/.rpm/.AppImagefor x86_64. Arch users can installargos-binfrom the AUR.
The desktop app bundles the CLI binary so the two can’t drift. On first launch the welcome screen offers Open workspace folder or Create new workspace.
Linux — verify the download
Every .deb, .rpm, and .AppImage ships with a detached GPG
signature next to it (.asc). Import the release key once and verify
before installing:
# Import the Argos release-signing key.curl -fsSL https://argos.thothlab.tech/argos-gpg.pub | gpg --import
# Download the artifact + its signature.V=0.1.3curl -fsSLO "https://github.com/thothlab/argos-app/releases/download/v${V}/Argos_${V}_amd64.AppImage"curl -fsSLO "https://github.com/thothlab/argos-app/releases/download/v${V}/Argos_${V}_amd64.AppImage.asc"
# Verify — expect "Good signature from Argos Releases <releases@thothlab.tech>".gpg --verify "Argos_${V}_amd64.AppImage.asc" "Argos_${V}_amd64.AppImage"The same .asc pattern works for .deb and .rpm. We use detached
GPG signatures across all three formats rather than the distro-native
mechanisms (debsig-verify / rpm --import) so one workflow covers
every Linux user.
The .sig files Tauri produces alongside the artifacts are minisign
signatures consumed by the in-app updater — separate chain, ignore
them for download verification.
Install the CLI on a CI runner
The CLI ships with every desktop bundle; on Linux runners you can
extract it from the .deb directly:
V=0.1.3curl -fsSLO "https://github.com/thothlab/argos-app/releases/download/v${V}/Argos_${V}_amd64.deb"dpkg-deb -x "Argos_${V}_amd64.deb" out./out/usr/bin/argos --helpSee CI integration for ready-made GitHub Actions and GitLab CI workflows.
Create your first request
In the desktop app:
- Open workspace folder → pick an empty folder.
- Click + in the sidebar header → New REST request.
- Enter
https://httpbin.org/getin the URL bar. - Press ⌘+Enter (or click Send).
The response pane shows status, headers, body, and timing. Argos auto-saves
the request to <workspace>/collections/<slug>.argos.yaml — open it in your
editor of choice if you want to see the on-disk shape.
Add a test
In the Scripts tab of the request editor:
bru.test('status 200', () => { bru.expect(bru.res.status).toBe(200);});Send the request again. The Tests sub-tab in the response pane shows
✓ status 200. The same script runs in CI when you use argos run.
Run a collection from the command line
From the workspace root:
argos run ./collectionsArgos walks the tree, runs every request in order, prints a Mocha-like summary, and exits non-zero if anything failed. Add a reporter to capture a structured artifact for CI:
argos run ./collections \ --reporter junit=report.xml \ --reporter json=report.jsonNext steps
- Import an existing collection — Postman, Insomnia, OpenAPI.
- Environments —
{{baseUrl}}and secret values. - Scripting overview —
bru.*test helpers and Postman parity viapm.*.