What's New in Orbittest Client 1.2.0

Orbittest Client v1.2.0 (2026-06-26) turns the app into something you can watch as well as work in. A brand-new Performance monitor gives you a live, Task-Manager-style view of CPU, memory, network latency, and processes — without a single byte leaving your machine. Pulsar monitors are now fully manageable from one menu, the workspace gets a cleaner icon-only activity bar, and every chart finally tells you when. And because it rolls up everything shipped since v1.0.1, upgrading lands Beacon, Source Control, and more in one step.

Auto-update

Existing installs update themselves in the background — Orbittest Client checks GitHub Releases and installs new versions automatically, so you don’t need to do anything. Prefer a manual install? Grab the signed Windows installer from the v1.2.0 release page.

At a glance

Performance monitor

A live CPU / Memory / Network / Processes dashboard, updated once a second. Everything stays on your machine.

Pulsar monitor management

A per-monitor ⋮ menu — Edit, Pause/Enable, and Delete — with confirm-on-delete.

Icon-only activity bar

A cleaner left rail; hover any icon to reveal its name.

Date/time chart axes

Pulsar, Beacon, and Performance time-series charts now label the time axis.

---

Performance monitor New

Open the Performance icon in the left rail for a live, read-only diagnostics dashboard that updates once a second. It works like Windows Task Manager, but scoped to Orbittest Client — and nothing leaves your machine.

A category rail on the left switches between four live views.

CPU

The app’s combined processor usage over time, alongside host details: CPU model, number of logical processors, base clock speed, and how long the app has been running (uptime).

Memory

The app’s memory footprint over time, shown next to your system’s total and available memory.

Network (latency / ping)

Measures the round-trip time from your computer to a server — how long a message takes to get there and back. Lower is better.

1. Pick a server with the one-click Cloudflare or Google presets, or type your own (for example api.example.com or 1.1.1.1).

2. Read the rating badge, which grades the connection in plain English:

   Rating	Round-trip time
   Excellent	< 80 ms
   Good	< 150 ms
   Fair	< 300 ms
   Poor	≥ 300 ms
   Offline	server doesn’t respond

3. Track the connection over time with Average, Best, and Worst, plus the percentage of dropped checks — great for spotting a flaky link.

How latency is measured

Latency is measured with a TCP connection test — a privilege-free stand-in for traditional ICMP ping. Numbers run slightly higher than a raw OS ping because a full connection handshake is completed, but they track connection health the same way.

Network throughput (MB/s) is intentionally not included: reading per-interface byte counters requires a native module. The Network view is a latency/ping monitor, not a full bandwidth graph.

Processes

A live list of every process the app runs — name, PID, CPU %, and memory — sorted by memory use.

Tip

The Performance monitor is read-only. It surfaces diagnostics so you can spot a runaway process or a flaky connection; it never changes anything on your system.

---

Pulsar monitor management New

Pulsar runs your scheduled monitors while Orbittest Client is open. In v1.2.0, every monitor gains a ⋮ menu so you can manage it without leaving the list.

• Edit — change the monitor’s request, schedule, or assertions.
• Pause / Enable — stop a monitor from running, or turn it back on.
• Delete — remove the monitor. Deleting always asks for confirmation, and its run history is cleared along with it.

New monitors are now created with the name “New Pulsar.”

---

Improvements

• Cleaner icon-only activity bar. The left rail no longer shows text labels — hover any icon to see its name. This gives the workspace more room and a calmer first impression.
• Date/time axes on every chart. Time-series charts in Pulsar, Beacon, and the new Performance monitor now label the time axis, so you can read when something happened at a glance.

Fixed

• Chart tooltips no longer clip at the edges of a graph — they stay fully visible near the left and right borders.
• Import / Export was removed from the activity bar. The same tools still live in the Collections ”+” menu, the Tools grid, and Settings → Data (see the note below).

Importing & exporting

There is no longer an Import / Export icon in the left rail. To import a cURL command, a Postman collection, or another source — or to export your workspace — use the ”+” menu in Collections, the Tools grid, or Settings → Data.

---

Also included since v1.0.1

The v1.2.0 installer rolls up every feature shipped after v1.0.1. If you’re upgrading from v1.0.1, you also get the following.

Beacon

A live HTTP proxy that captures and decrypts traffic, with a Traffic view and a metrics Dashboard (throughput, error rate, p95 latency, Apdex) — and it flags exposed secrets such as JWTs and bearer tokens.

Pulsar

Scheduled monitors that run while Orbittest Client is open, tracking uptime, error rate, and p95 latency over time, with a shareable status page.

Source Control

Stage, commit, and push your collections and environments to a GitHub repo, with a history and per-file diff view.

Multi-source import

Bring in requests from cURL, Postman, and other sources.

Secret & dynamic variables

Mask sensitive values and generate values at send time.

Beacon — capture, measure, and audit traffic

Beacon proxies your HTTP traffic so you can watch every request live, then switch to a metrics Dashboard to see throughput, error rate, p95 latency, and Apdex for the whole session. It also scans payloads and headers for exposed secrets — JWTs, bearer tokens, and password-like values — and lists exactly where each finding occurred.

Source Control — version your workspace

Commit your collections and environments to a GitHub repository straight from the app. Stage changes, write a commit message, and Commit & Push in one place, with a full history and per-file diffs.

Note

For the complete, version-by-version history — including everything between v1.0.1 and v1.2.0 — see the release notes on GitHub.

---

Upgrading

Orbittest Client updates automatically in the background, so most users are already on v1.2.0. To install or reinstall manually, download the signed Windows installer from the release page.

Download v1.2.0 Signed Windows installer on the GitHub releases page.

What is Orbittest Client? The overview — what it is, the full feature list, and how licensing works.

User Guide The full walkthrough — requests, environments, scripts, Ghost, and Insights.

Data-Driven Testing Drive a collection from a CSV or JSON file, one iteration per row.

---

V1.0.1

Orbittest Client v1.0.1 (2026-06-17) brought four new capabilities to the local-first API testing workstation: OAuth 2.0 authentication, a real code editor for scripts and bodies, live variable autocomplete, and a command-line runner for CI pipelines.

OAuth 2.0 authentication

Request, store, and attach access tokens from the auth editor — no more hand-pasted bearer tokens.

Syntax-highlighted editor

JavaScript highlighting for pre-request scripts, test scripts, and request bodies.

Variable autocomplete

Live {{variable}} scanning with inline autocomplete across the request builder.

Command-line runner

Run collections from the terminal with JSON / JUnit output — built for CI.

OAuth 2.0 authentication

Until now, calling a protected API meant generating a token somewhere else and pasting it into a header by hand — then doing it again every time the token expired. In v1.0.1, Orbittest Client can request, store, and attach OAuth 2.0 access tokens for you, directly from the request’s Auth tab.

1. Open a request and select the Auth tab.

2. Choose OAuth 2.0 as the authorization type.

3. Fill in the token details for your provider — typically the token endpoint URL, client ID, client secret, scope, and the grant type (for example Authorization Code or Client Credentials). Any field accepts {{variables}}, so you can keep secrets in an environment instead of the request.

4. Click Request Token. Orbittest Client performs the token exchange and stores the resulting access token with the request.

5. Send the request. The stored token is attached automatically as an Authorization: Bearer … header — you never copy or paste it.

Note

Tokens are kept locally with the rest of your workspace. When a token is no longer valid, just press Request Token again to fetch a fresh one. Because every field supports {{variables}}, the same OAuth configuration works across dev, staging, and prod simply by switching the active environment.

Pair it with the PKCE flow

If your provider uses the Authorization Code flow, see our explainer on the Authorization Code flow with PKCE to understand what the token exchange is doing under the hood.

Syntax-highlighted code editor

Scripts and bodies open in a real code editor with JavaScript syntax highlighting instead of a plain text box. Highlighting applies in three places:

• Pre-request scripts — run before the request is sent.
• Test scripts — run after the response arrives, to assert on it.
• Request bodies — for raw JSON and JavaScript payloads.

This makes it far easier to spot a missing bracket, an unterminated string, or a typo before you run anything.

Pre-request script

// Compute a timestamp and stash it for the request to use.
const now = Date.now();
ot.variables.set('requestedAt', String(now));

Test script

// Assert on the response after it arrives.
ot.test('status is 200', () => {
  ot.expect(ot.response.status).toBe(200);
});

ot.test('body has an id', () => {
  const body = ot.response.json();
  ot.expect(body.id).toBeDefined();
});

Note

Scripts execute in a network-isolated sandbox worker — no DOM, no bridge, and a hard timeout. The editor only changes how you write them, not how they run.

Variable autocomplete

Orbittest Client scans your variables live — from the active environment, the collection, and any data-driven row — and offers inline autocomplete as you type. Start typing {{ in almost any field and a dropdown of matching variable names appears; pick one and it’s inserted complete.

Autocomplete is available across the request builder, including:

• the URL and query params
• headers and the OAuth fields
• the request body
• pre-request and test scripts

Variables resolve everywhere

GET {{baseUrl}}/users/{{userId}}
Authorization: Bearer {{accessToken}}

This removes the two most common variable bugs: misremembering a name, and referencing a variable that doesn’t exist in the current scope.

Command-line runner

A CLI runs your saved collections and requests straight from the terminal — no UI required. It’s scriptable, returns proper exit codes, and emits JSON and JUnit reports, which makes it a natural fit for CI pipelines.

Run a collection

orbittest-client run "My Collection" --env staging

Option	What it does
--env <name>	Run with a named environment’s variables.
--data <file>	Drive the run from a CSV / JSON data file (one iteration per row).
--reporter <list>	Output format(s): json, junit, or both (comma-separated).
--out <dir>	Directory to write report files into.
--bail	Stop on the first failing request.

Emit CI-friendly reports

orbittest-client run "My Collection" \
  --env ci \
  --reporter json,junit \
  --out ./reports

The JUnit report drops straight into most CI test dashboards, and the JSON report carries full request/response detail for custom processing. The runner exits with code 0 when every request and test passes and a non-zero code otherwise, so a failing run fails the build.

.github/workflows/api-tests.yml

name: API tests
on: [push]
jobs:
  api-tests:
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run Orbittest Client collection
        run: orbittest-client run "My Collection" --env ci --reporter junit --out reports
      - name: Publish results
        if: always()
        uses: actions/upload-artifact@v4
        with:
          name: api-test-reports
          path: reports

Note

Command and flag names above reflect v1.0.1. Run orbittest-client --help to see the authoritative list of commands and options for your installed version.