It starts as a script on your laptop
Python, shell or Node, as it is. One command publishes the folder, and the parts in braces become the inputs people fill in.
The five-minute quickstart Or have your coding agent publish it
Scripts for your team, your software and your agents
Give every script a Run button.
Publish a script once, and stop being the only one who can run it. 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, and stop being the only one who can run it.
Start free Read the quickstart
Free for 500 runs a month. No card needed.
npm install -g @reminix/cli
Refund a customer v2
Run
Order A-10423
Amount (USD) (optional) 40
Reason (optional) Charged twice
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 |
$ 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}]" Published refund-customer version 1.
Your team runs it without you
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.
Form for your team
Run
Order A-10423
API for your software
await reminix.run("refund-customer", { orderId: order.number, amount: 40, reason: "Charged twice", });
CLI from any laptop
$ reminix run refund-customer \ --input \ '{"orderId":"A-10423","amount":40}' { "order": "A-10423", "amount": "$40.00", "refund": "re_3Q8xM02eZvKY" }
Your team runs it without you
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", });
$ reminix run refund-customer \ --input \ '{"orderId":"A-10423","amount":40}' { "order": "A-10423", "amount": "$40.00", "refund": "re_3Q8xM02eZvKY" }
It runs by itself
Put it on a timetable, or have it run when something happens in your workspace.
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
Claude or ChatGPT runs it when your team asks
Support, operations and finance ask the agent they already use, in their own words. 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
Message your AI agent…
Safe to hand to anyone
Refund a customer v2 Succeeded
- Started
- Today, 9:12 AM
- Via
- Agent · token Claude
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)
- Keys added on the way out You save the Stripe key in Reminix once. When the script calls api.stripe.com, Reminix adds the key to that request. The script can read a key only if you turn that on for it.
- The script stays fenced in Each run gets its own machine, which Reminix removes when the run ends. It can reach only the hosts you list, and every request lands in the run's log.
- Approval where you want it Set a script so runs started by an AI agent wait for an owner or admin. The person sees exactly what the agent asked for, then approves or denies it. On Business, every run can wait for approval.
- Every run on record Reminix records who ran it, from where, with which inputs, what it printed and any files it wrote. If a run prints a key it had access to, the log shows [secret] instead.
How Reminix handles security Set up approvals Versions and rolling back
Why not just use cron, GitHub Actions or a workflow tool?
Each one does part of the job. None of them runs the script you already have for anyone you allow, with its keys never in the code. Reminix does.
One script, from your laptop to your team
- Your script As it is, in Python, shell or Node
Other tools change it here Rewrite it as blocks or around main(), or wrap it in a handler
- Reminix Adds the keys on the way out. Approval, if you want it.
The keys stay out of the code Elsewhere the code reads them, from files or environment variables
- Your team runs it From a form, the API or their AI agent
Others limit who runs it Only you, or people with write access to the repository
- Every run on record Who ran it, the inputs and what it printed
What to publish first
Each of these has a guide in the docs.
-
refund-customerAn agent asks to refund an order, a person approves it, and the run is on record. Guide -
unlock-accountSupport unlocks a customer's account from a form. Guide -
monthly-reportFinance gets last month's revenue as a CSV file on the 1st. Guide -
nightly-syncA script copies the day's orders from the shop to the warehouse every night. Guide -
alert-on-failureWhen nightly-sync fails, Slack gets the error. Guide
Your coding agent can publish yours
Paste this prompt into Claude Code or Codex. It reads Reminix's agent skill and lists the scripts in your project that people run by hand. 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.
Give your first script a Run button
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. Have a question first? Talk to us.