Coming soon · early access open

Just ask.

Open OpenClaw on your own machine, or talk to Claude, and say what the store needs. A size chart on every product page. A bundle before the holiday rush. An app installed and wired up. Pasilobus is the layer underneath that lets your agent actually touch the store — and stops it doing anything you have not approved.

Join the waitlist Read the docs draft
Your machine
where it runs
Your approval
before anything ships
Full
audit log
your agent · your machine
add a size chart to every product page
Installing Size Chart… added the theme block to product.json and mapped it to your specs.size metafield.
✓ app installed · ✓ block added · 214 products matched
waiting for your approval — nothing published
ship it
2 messages
1 feature shipped

Works with

The agent you already use

We are not asking you to adopt another chat window. Whatever you already drive your work with, point it at your store.

OC
OpenClaw
Runs on your own machine, in your own shell, with your own keys.
C
Claude
Talk to your store from Claude Code or the desktop app.
⋮
Or your own
Anything that can call an API and hold a token.

What you can ask for

Features, in a sentence

Merchandising
"Add a size chart to every product page"
Finds the app, installs it, adds the theme block, maps it to your size data.
Bundles
"Bundle these three before the holiday rush"
Builds the bundle, prices it, and puts it on the product pages that matter.
Catalog
"Clean up last season’s tags"
Walks the catalogue, proposes the changes, waits for you to approve them.
Inventory
"Tell me when the navy hoodie runs out"
Wires back-in-stock alerts and drafts the campaign when the shelf empties.
Reporting
"What moved slowly this month?"
Reads your orders and comes back with a list, not a dashboard to go hunting in.
Anything
If an app can do it, you can ask for it
Every Pasilobus app exposes the same surface. Your agent gets all of it.

Guardrails

Nothing moves without your say-so

Every request compiles to a reviewable rule. Version it in git, scope it per store, gate any action behind approval, and read back exactly what happened. The same surface our own apps use.

YAML rules, git-versionable
Approval gates on any action
Webhooks in, typed actions out
Full audit log, exportable
rules/restock-nudge.yml
when: inventory.zero
if:
  - subscribers > 50
  - product.tag != "discontinued"
then:
  - draft: back_in_stock.campaign
  - notify: "#store-ops"
approval: required

Or drive it yourself

The same thing, from a terminal

Install once, point it at a store, and talk to it in plain language — or wire the same binary into CI and let it run unattended. Nothing is sent until a rule clears its approval gate, and every action lands in the audit log.

One binary, macOS / Linux / CI
Plain language in, YAML rules out
--dry runs by default
Scriptable: exit codes and JSON
zsh · your machine
$ npm i -g @pasilobus/cli
$ pasilo login --store acme.myshopify.com
✓ authorised — 3 apps detected
$ pasilo rules add ./rules/restock-nudge.yml
✓ rule saved — watching 214 products
$ pasilo run --dry
  12 chores matched · 0 actions sent
  2 need approval — nothing left the store
runs in CI
--dry by default

Delegate the boring parts.

Early access rolls out store by store. Developers first.

Join the waitlist