jawb
Join Discord

download

Download jawb

Install the jawb CLI and its daemon with one command. Add the desktop console to approve, review and unblock what your agent does.

[01] cli

The CLI and jawbd

One command installs jawb and the jawbd daemon it is pinned to. The first jawb command starts the daemon for you.

Version 0.1.1 · Windows x86_64, macOS Apple silicon, macOS Intel, Linux x86_64

macOS and Linux

In Terminal:

$ curl -fsSL https://get.jawb.app/install.sh | sh

Installs into ~/.jawb/bin. It never edits your shell profile: it prints the PATH line to add.

Windows

In PowerShell:

$ irm https://get.jawb.app/install.ps1 | iex

Installs into %LOCALAPPDATA%\Programs\jawb\bin. It adds that folder to your user PATH.

What the installer checks

  • It reads the latest release from https://get.jawb.app/cli/latest.json and checks the archive’s SHA-256 before installing anything. Set JAWB_VERSION to pin a version.
  • With minisign on your PATH, it also checks the release signature (key 911E98C297EA8E7B). Without it, it says it skipped that check; the SHA-256 check always runs.
  • Then run jawb status to see the daemon answer.

The full install guide, including building from source

[02] desktop

The desktop console

A supervision console, not a browser. Your agent browses; you approve what it holds for you, review what it did, and unblock it. The app reads when you open a view, focus the window or click Refresh, and sends nothing while it sits idle.

Version 0.1.0In development

The first desktop release is not published yet. These links work once it is.

Choose your platform

  • Approvals

    Every action jawbd holds for a person, such as a purchase, on a card with the site, the amount and who asked. You approve or deny it there.

  • Activity

    The trace of what your agent did, step by step, so you can review a run after the fact.

  • Extensions

    What is installed, where it came from, and what each extension may do.

  • Status

    Whether jawbd is running and which version. When none is running, the app starts the jawbd it ships with.

More about the desktop app

[03] first-launch

Opening it the first time

The desktop builds are not code-signed yet, so macOS and Windows ask you to confirm the first launch.

macOS

Open the .dmg and drag jawb to Applications. Gatekeeper blocks the first launch: open System Settings → Privacy & Security, and click Open Anyway next to the message about jawb.

Windows

Run the setup .exe. SmartScreen says “Windows protected your PC”: click More info, then Run anyway.

Linux

Make the AppImage executable, then run it:

$ chmod +x jawb_0.1.0_amd64.AppImage

[04] requirements

What else you need

  • Chrome or Chromium, for Act and See

    Clicking, filling forms, screenshots and --js reads use a locally installed Chrome or Chromium. jawb never downloads one. Read, status, profiles and navigation work without it.

  • Nothing else for the desktop console

    It ships with its own jawbd and connects to the one the CLI started when it is already running.

Free for personal developers. Business and team use will need a paid licence. Everyone will sign in with a jawb account.