Quester Studio

Quester Studio

A local desktop app for multi-step API journeys. You draw the path on a canvas; the same *.flow.json files run from the CLI. Secrets stay on disk.

Public preview. Desktop builds are unsigned.

Download Guide

Drop a node on the canvas — form, HTTP, extract, and the rest live in the same graph.

Where it is useful

Everyday work where a single request is not enough, and the team needs to share the same files.

  • Reproduce a failing chain locally

    Login, then the next call with the token, then an assert — on your machine, with the same environment the app uses.

  • Regression in continuous integration

    Testers add assert steps on the canvas. The CLI runs those flows or a suite in CI from the same files.

  • Follow the path without writing scripts

    The canvas shows the business order. Optional note stickies document intent and are not executed.

  • A human choice in the middle of a run

    Search, pick from the results, then call the next API. A form node pauses until you submit (or until CLI --forms supplies the values).

  • From a request collection to a shared workspace

    Import a collection, then chain what used to be separate requests into one journey the team keeps in git.

More on who it is for

What it includes

Shipped in the current public preview. This is the working set, not a promise list.

Workspace

A folder with quester.json, environments, gitignored secrets, collections, forms, and optional on-disk run logs.

Canvas nodes

HTTP, extract, template, set, if / switch, foreach / try frames (including nesting), join, subflow, assert, json / inspect, log, note, form, input, output, delay, transform, merge.

Forms

Reusable forms/*.form.json. A form node waits mid-flow. Field types include string, number, boolean, json, and select (including options from a previous response). CLI uses --forms.

Run

Environment picker, run status for each node, stop, response viewer, and a run list at the bottom of the window.

CLI

validate, run, suites, and collection import — the same files as the desktop app.

Compared with a typical HTTP client

No product names. This is how Quester is shaped, not a claim that it replaces every client.

Typical HTTP client Quester
Requests grouped in folders Journeys as a graph: branch, loop, nested try / foreach
Parameters mainly at the start of a run Mid-flow forms that wait for Submit (or CLI --forms)
Chaining often done in scripts Extract and template steps on the canvas
Cloud sync or app-only storage JSON files on disk in git; secrets stay local and gitignored
Separate tooling for CI The same flows via @quester-studio/cli

This is still a preview. Other clients are often stronger at editing a single request, or they ship signed installers. Quester is aimed at shared multi-step scenarios that live in a folder.

CLI

Prefer the terminal?

Validate workspaces and run flows or suites with @quester-studio/cli — same *.flow.json files. 

bunx @quester-studio/cli validate ./my-workspace
bunx @quester-studio/cli run login-and-profile \
  --workspace ./my-workspace --env local \
  --input '{"username":"emilys","password":"emilyspass"}'
CLI getting started Node reference

Try it on your machine

Download an unsigned build, open the sample workspace, run login-and-profile first, then search-pick-cart if you want a mid-flow form.

Download Docs