extensions
An extension is a package that gives your agent new tools: tools for the sites you use, connectors to your apps, and workflows that write a report. Its tools will appear in jawb tools beside the ones a page declares, and what it does goes through the same checks as a command you run yourself.
[01] shapes
Each shape runs in a different place, so each has its own rules.
Tools for the sites you name, implemented by a script in the matching tab.
The script runs in its own isolated world, apart from the page’s scripts. It returns data, or proposes an action that jawb then runs through its normal checks.
Planned examples: app.jawb.extract, app.jawb.a11y
Tools that call an app or an API with your own credentials.
jawb adds the stored secret to the request at the network layer, and only for domains the secret is bound to. The extension never sees the value.
Planned examples: app.jawb.notion
A flat list of jawb steps that produces something, such as a report.
No code: each step is a command you could run yourself, with the same checks. Workflows are the first shape open to community authors, on jawb Hub.
Planned examples: app.jawb.uat, app.jawb.screens, app.jawb.clip
Two more shapes are reserved for later: policy packs, rules that can only make jawb’s checks stricter, and readers, which turn what jawb sees on a page into structured data.
[02] safety
The rules every extension will follow. They are the planned design; none of it is built yet.
Planned designjawb’s own extensions ship inside jawb, in each signed release. An extension from anyone else is pinned to its exact bytes when you install it and labelled with where it came from; any change asks you again, code is never fetched later, and a revoked version is switched off.
The manifest declares the sites, domains, secrets, sessions and files an extension may use, with a reason for each. You approve them at install, through the same confirmation flow as a purchase. An update that asks for more waits for you to approve it again.
jawb adds a stored secret to a request at the network layer, and only when the destination is allowed for both the extension and the secret. The extension never sees the value.
A cheaper route is never a weaker one. Every action an extension causes goes through the same per-action policy as a command you run, and its manifest cannot lower that. Classified purchase-like actions use a human-confirmation flow; an extension never confirms anything.
A safeguard for honest checkout flows, not a guarantee against a hostile page. Until an OS-mediated approval exists, a program running as you can still approve.
Until jawb’s WebAssembly host can enforce a manifest, code that runs inside jawb comes from jawb only, and listings say their permissions are declared, not sandbox-enforced.
[03] planned
The first extensions jawb builds itself, across all three shapes. They ship inside jawb, with app.jawb.* ids.
app.jawb.uat
Runs acceptance criteria against your site and writes a PASS, FAIL, UNCERTAIN or BLOCKED report with screenshots and trace ids.
app.jawb.screens
Screenshots a set of pages at phone and desktop sizes, in light and dark, in one call.
app.jawb.clip
Saves a page, or a list of URLs, as clean Markdown with the source URL and date.
app.jawb.extract
Turns tables, lists and repeated cards on a page into rows, as JSON or CSV.
app.jawb.notion
Reads and updates your Notion pages through Notion’s own MCP server, signed in with your Notion account. Your Notion plan’s limits apply.
app.jawb.a11y
Audits a page for accessibility issues from an isolated script and returns the findings as JSON, or into an app.jawb.uat report.
None is in a release yet. When they ship, this list shows what each release includes.
[04] community
Publishers list their own extensions on jawb Hub, a public repository. Every listing passes automated checks before it appears here; nobody at jawb reviews the code.
Listed means these exact bytes passed jawb Hub’s automated checks. It is not a review, a signature or a warranty: jawb does not vouch for the code. Listing terms
Install a listed extension with jawb extension install <id>. jawb labels it listed and asks you to approve what it may do.
Loading listings from jawb Hub…
[05] build
Workflows come first: a manifest over the runners jawb ships. You host your extension and keep your code. To list it, open a pull request on jawb Hub; automated checks decide, and nobody reviews your code.
Free and paid extensions are planned.
[06] never-list
Some extensions would work against the sites they touch or the people they act for. jawb will not build or list them.
LinkedIn data extraction or outreach
LinkedIn’s terms name browser add-ons.
Coupon auto-appliers at checkout
They act inside purchase flows and carry retailer terms risk.
CAPTCHA solvers, or anything that evades rate limits or bot defences
A site’s protections are not jawb’s to get around.
Generators that pass a second factor unattended
They defeat the point of the second factor.
AI sidebar clones
Your agent’s own model does that job.