August review: Miraxa gets hands, eyes and somewhere to put things
Getting your systems to work together has always needed a specialist. Someone who knew Shopify, and knew NetSuite, and knew what to do in both. And whenever you needed something out of one of them, you waited your turn for that person's attention, however small the job was.
Introducing our new Operator mode, which makes Miraxa that specialist. You ask it directly, and it gets on with the job.
Say you want a Matrixify-shaped CSV of every product, sent over to Tony in marketing. Ask for exactly that, and it pulls the products out of Shopify, builds the file, attaches it to an email and sends it. Nobody logs into anything. Nobody exports a file into their downloads folder. Nobody writes the email.
And it checks with you before it changes anything, so handing over a real job never means losing track of what happened to it.
The person in the middle, minus the queue
When Operator mode is on, Miraxa is holding everything at once: every connection you have set up, your File Store and your knowledge base, plus a proper Linux workspace. Python, psql and mysql, curl, git and the usual command line tools are all in there, so it can query a database directly, transform a file, pull down a dataset or call an API that has no connector yet.
Holding all of it at once is the point. Getting an export out of one system and into someone's hands in a format they can actually use takes several kinds of knowledge at the same time: how that system exports, what shape the other end expects, and how to get it sent. That combination is why it was always a request to someone rather than something you did yourself.
So ask it for the awkward things. Every product with no image, as a spreadsheet. The forty SKUs whose supplier code changed, updated. A report your system does not offer, built out of what is in there. Miraxa keeps its files and anything it installs for the length of the task, so it can have a look first, try something small, check that it worked, and then get on with the rest.
It shows you before it does it
You would want to see what someone was about to do to your live data before they did it, and Miraxa works the same way. It reads whatever it needs to, but the moment it wants to change something or send something, it stops and shows you exactly what it has in mind. Say yes and it carries on. Say no and it takes your steer instead.
Which means you can hand over a real job and go and do something else, without wondering what it got up to while you were gone. And if your workspace already has governance rules, they still apply on top: anything your policy blocks stays blocked, and anything that needs a named approver still goes to them.
Everything runs in a sandbox
All that code needs somewhere safe to run, so Operator mode brings a sandbox with it. Every session gets one of its own, kept well away from your systems and from anyone else's work, and when the session is finished the whole thing is thrown away.
Your credentials never go in there. When Miraxa uses one of your connections, the key is applied outside the sandbox, so the code it runs can work with your systems without ever handling your keys.
Show it a picture. It builds the workflow.
Also new this month: Miraxa can see what you send it. Paste an image straight from the clipboard, drop a file anywhere on the chat panel, or reach for the paperclip.
Which means you can stop describing things altogether. Screenshot a workflow from the tool you are migrating off. Photograph whatever your ops lead scrawled on a whiteboard. Paste in a diagram from a spec. Then ask Miraxa to build it, and watch it wire the canvas.
Images, PDFs and small text, CSV or JSON files all work, and anything you attach can be saved straight into your File Store. No special permission either: if you can use Miraxa, you can attach.
Somewhere for it all to live
And new alongside them, the File Store. Files and folders that belong to your workspace rather than being trapped inside one workflow. Upload by hand, or let your automation fill it.
The File Store node gives workflows everything the page can do. A weekly schedule that has an agent summarise last week's orders and files the result is about three nodes, and the file is simply waiting for you on Monday morning.
File content never travels through the workflow history, so a genuinely big file moves through a run without dragging it down.
It is already there
Operator mode is there now for Editors, Admins and Owners, with nothing to sign up for. If you cannot see it in the mode selector, your role does not have the permission yet and an administrator can add it for you.
Start with a question rather than a job. Ask it something like which products have no image, or how many orders are sitting unfulfilled, and you get a feel for how it works before anything changes. It uses your monthly AI credits like anything else, and a long session costs more than a quick chat, so keep half an eye on the first couple.