Scripts for your team, your software and your agents
Publish a script once. Your team gets a form, your software an API, your agents a tool, and you decide which runs wait for approval.
Publish a script once. Your team, your software and your agents can all run it.
Start free Read the quickstart
npm install -g @reminix/cli
Refund a customer v2
Run
Order A-10423
Amount (USD) (optional) 40
Reason (optional) Charged twice for the same order
Recent runs
| 9:44 AM | App | |
| 9:41 AM | Awaiting approval | Agent · token Claude |
| 9:38 AM | Running | API · key billing |
| 9:12 AM | Succeeded | App |
Python, shell or Node, as it is. One command publishes the folder, and the parts in braces become inputs. Each run gets its own machine, which Reminix removes when the run ends. Files the script writes come back as downloads.
$ ls refund.py requirements.txt $ python refund.py A-10423 # works, but only here, and only for you $ reminix login $ reminix publish \ --command "python refund.py {orderId} [--amount {amount}] [--reason {reason}]"
Paste this prompt into Claude Code or Codex. It reads Reminix's agent skill and lists your scripts. Pick one, and it prepares it, tests a draft, and publishes only when you say so.
Read https://reminix.com/docs/skill/SKILL.md and follow it. List the scripts in this project that people run by hand, one line each, and wait for me to pick one to publish to Reminix.
Each way checks the same inputs and shows up in the same list of runs. Share a script with your whole workspace or only with certain teams. Other members don't see it at all, not even through the API.
Run
Order A-10423
await reminix.run("refund-customer", { orderId: order.number, amount: 40, reason: "Charged twice for the same order", });
$ reminix run refund-customer --log \ --input \ '{"orderId":"A-10423","amount":40}' → GET api.stripe.com/v1/payment_intents/search 200 (231 ms) → POST api.stripe.com/v1/refunds 200 (412 ms) { "order": "A-10423", "amount": "$40.00", "refund": "re_3Q8xM02eZvKY" }
Support gets a form. Your billing app calls the API. Each one checks the same inputs and shows up in the same list of runs.
Share a script with your whole workspace or only with certain teams. Other members don't see it at all, not even through the API.
Run
Order A-10423
await reminix.run("refund-customer", { orderId: order.number, amount: 40, reason: "Charged twice for the same order", });
$ reminix run refund-customer --log \ --input \ '{"orderId":"A-10423","amount":40}' → GET api.stripe.com/v1/payment_intents/search 200 (231 ms) → POST api.stripe.com/v1/refunds 200 (412 ms) { "order": "A-10423", "amount": "$40.00", "refund": "re_3Q8xM02eZvKY" }
On a timetable, or when something happens in your workspace. Each run shows up in the same list of runs.
Schedules
A schedule runs this script at set times, with the inputs you choose.
Every night
Every day at 2:00 (Europe/London) · next run tomorrow at 2:00 AM
Enabled
Triggers
A trigger runs this script when something happens in the workspace, such as another script's run failing.
Nightly sync failed
On run.failed script.slug = nightly-sync
Enabled
Support, operations and finance ask Claude, ChatGPT or the agent they already use. Every script you publish is an MCP tool their agent can call by name.
Refund $40 on order A-10423. The customer paid twice.
Used Reminix refund_customer
The $40.00 refund for A-10423 is waiting for approval. It goes out as soon as someone approves it.
Waiting for approval: refund-customer, order A-10423, $40.00
Refund a customer v2 Succeeded
Output
{
"order": "A-10423",
"amount": "$40.00",
"refund": "re_3Q8xM02eZvKY"
} Log
→ GET api.stripe.com/v1/payment_intents/search 200 (231 ms) → POST api.stripe.com/v1/refunds 200 (412 ms)
How Reminix handles security Set up approvals Versions and rolling back
Each of these has a guide in the docs. Using something else today? See how Reminix compares.
refund-customer An agent asks to refund an order, a person approves it, and the run is on record. Guide unlock-account Support unlocks a customer's account from a form. Guide monthly-report Finance gets last month's revenue as a CSV file on the 1st. Guide nightly-sync A script copies the day's orders from the shop to the warehouse every night. Guide alert-on-failure When nightly-sync fails, Slack gets the error. Guide Free has room for 1 publisher and 5 people who only run scripts. You get 500 runs a month, and you don't need a card. Pro is $29 a month for the whole workspace.