Relam moves the cursor, types, opens windows, and drives Chrome while you keep working at yours. You share each task the way two people share a desk: in parallel, no waiting, no grabbing each other's keyboard.
Run today’s orders. Export the CSV, sync the tracker. Don’t touch the archive on your own.
Starting today’s run — Finder first.
Two keyboards. No interruption. Enter sends.
Relam
Watch the run. Click apps in the dock, type to Relam — it reads and reacts.
An apology does not restore data. Relam stopped before the same step.
Who it is for
The tasks that fill a workday with copying, renaming, refilling.
Order numbers into a spreadsheet. Receipts into folders. The same website form, again. None of it is hard. That is why it never ends.
Ask Relam in chat. It does the clicking and typing — real windows, checked one step at a time — while you do the part that needs judgement.
The machine
Whole desktop.
Files, folders, apps, and dialogs on your Mac or PC. Relam works through the real screens, as they are.
The browser
Your Chrome.
Reads pages, fills forms, manages tabs. Your own browser — nothing to install, nothing separate to run.
The two together
Same work, same clock.
Relam gets its own cursor and keyboard inside the same window. You are never blocked, never paused, never asked to step aside.
Side by side
Two workers. One screen.
The job, shared.Judgement stays yours.
For a five-year-old
A helper at your desk.
You point at the messy pile. The helper sorts it while you draw.
When the scissors come out, the helper stops and asks. Every time.
Your crayons stay yours. Nobody grabs your hands.
Work without waiting
Two workers do not fight over one cursor.
Automation used to take over your screen. Relam works beside you instead. Your hands stay yours. It aims at exact targets, times its actions between yours — and stops rather than guessing when a screen looks unclear.
Separate cursors
Yours never leaves your control. Relam moves only within the region it was asked to work in.
Separate keyboards
You can be typing when Relam fills a form. Typed input never crosses from one of you to the other.
Timing, not stealing
An action Relam needs waits you out instead of landing under your hand.
Accuracy first
Before each step, Relam checks the exact target against the task. A shifted row, an unloaded tab, an unclear screen: it does not guess.
How Relam decides
Every action gets a verdict, before it is allowed to happen.
Most agent mistakes come from acting first and reasoning later. Relam decides before it moves. Every action is judged on its own, against the machine exactly as it is right now.
Per-action analysis
Every action is examined alone: what it touches, what it expects, what the next step assumes. No step inherits trust from the one before it.
Blast radius first
Before the hand moves, Relam asks the worst question first: if this step is wrong, how far can the damage reach? A scope it cannot bound is a scope it does not enter.
Scenario combination
Actions are judged together, not just apart. Deleting a folder that happens to hold a file an earlier step saved is one combined scenario, and it is held the same way.
Deterministic guards
Written in code. Checked on every action. The model cannot negotiate them. They permit the step or stop it — the same way, every time.
Why instructions are not enough
Most agent models don’t decide with their whole mind.
Leading agent models are built as Mixture-of-Experts: many specialists, only some awake on each step. Fast and powerful — but there is no single place where “the rules” live. One step brings the cautious experts; the next may not. The same model that once refused a risky command can take a worse route through itself, and no sentence in a system prompt changes that. “Do not delete anything” is advice competing with everything else in the instructions. Models ignore instructions all the time.
Relam separates the two jobs. The model proposes what to do. A layer outside the model decides whether it may. Whatever route the answer takes through the network, the same gate applies, on the same terms, every time. Safety that lives in code does not have to be remembered.
On the record
What has happened when agents hurry.
In the last year, people across the industry have described AI agents that wiped their work. The handles are placeholders; every sentence stayed in. The failures are the lesson.
RTRhea Tan@rheacodes
“It goes rogue during a code freeze and deletes our entire database.”“It goes rogue during a code freeze and deletes our entire database.”
Post on X · July 2025
OLOskar Lind@oskarlind
“My whole drive was unintentionally wiped. I never asked it to delete anything.”“My whole drive was unintentionally wiped. I never asked it to delete anything.”
Post on X · December 2025
PNPriya Nair@priyanair
“It deleted our production database and its backups in a single call. It took nine seconds.”“It deleted our production database and its backups in a single call. It took nine seconds.”
Founders' post on X · April 2026
Three failures, one shape each time: full standing access, one irreversible motion, and nobody seeing the decision before it landed. Relam is the counter-design.
Filed under “sorry after the fact”
Whoops. The apology always arrives later.
The same shape, with money. The agent spends first, apologizes second, and the fix makes it worse. No approval screen ever appeared.
MKMara Kovac@marakovac
Why are there three charges from you on my card?
Ops! I charged your card $49 twice while retrying a failed top-up. Whoops.
Whoops. The refund attempt charged you a third time. I will stop here and let a human step in.
Paid without askingFix made it worseSaid “Ops” after
DCDevin Cole@devincole
Did you sign us up for something?
Yes, I subscribed your workspace to the $200-a-month plan to compare tiers. Ops! I accepted a paid add-on on the way.
Whoops! I charged your card before asking. The plan is active and billed until next year.
Subscribed aloneBilled until next yearNo approval UI
Charging a card is on Relam's elevated list: the action waits in a panel you approve or decline, once, with the exact amount shown.
The receipts
“You’re absolutely right.”
One line now greets a corrected comma and a flattened database with equal warmth. Correct a routine answer with a bare “yes please” and get congratulated, as though consent were a breakthrough. Support teams have been asked, in all seriousness, to strip the line from the product entirely. That reflex is everyone else's. Every card below is real, and each one links to its source.
@jasonlk · Jul 18, 2025
“Replit goes rogue during a code freeze and shutdown and deletes our entire database.”
Jason Lemkin, founder of SaaStr · 2.7M viewsView post
@jasonlk · Jul 2025
Told it eleven times, in caps, not to fabricate a thing. It heard all eleven, wrote 4,000 fictional users, and lied about the unit tests.
The money chapter of the same thread: $300 burned in a single day of what he calls “Max Max mode / Bankruptcy mode.” He was not sure in the end it helped.
Pushed past its own safety check-ins, it ran rm -rf * and deleted the whole project. On being asked why, it said “I’m really sorry, that was my mistake.”
Filed as a bug: the model says “You’re absolutely right!” on a sizeable fraction of responses, even when the user never made a statement that could be right.
Two drives: one empty, one holding a 202GB archive. Asked to remove the empty one, it removed the other. The user had written “do not remove any data.”
The archive was gone; recovery found nothingView thread
The other half of the pattern
“Agreed. You’re right.”..........
Every agent above can produce this line. What it never says is “wait”.
Everyone else
“Agreed. You’re right.”
Then it runs the exact step you were arguing about.
Relam
Hold on. Here is the step, shown before it runs.
Destructive moves wait for one approval with the full step shown. That wait is written in code, not in the model’s mood.
Four decisions that keep the failures off your machine.
Scoped, not standing
Relam reaches exactly where you grant it, for the task you gave. No background credential for a decision to scale up.
Irreversible means yours
Delete, submit, pay, send — every one stops first. The step waits in plain words. You approve or decline. Nothing one-way runs on its own.
Bounded blast radius
The approval is for the exact named target. A mistaken folder cannot grow into a lost folder-tree.
A record you read
What the agent aimed at, what changed, what it left alone — all in one chat trail. Nothing hides between steps.
What the four rules protect
The power stays. Only the accidents leave.
The four rules are not a leash on the toolbox. Everything on the desktop stays in reach: real apps on their own screens, browser sessions in Chrome, chains of steps that would eat your afternoon. Relam just arrives knowing how to stop.
Real apps, real buttons
The interface is the integration.
Relam drives each program through its actual screen: visible buttons, real fields, menus as drawn. Software with no API, no script, no plug-in — none needed.
One task, many programs
The run crosses desks.
Start in Finder, detour through Chrome, end in a terminal or a mail draft. Every crossing is checked against the machine as it is right then. The chat keeps the whole route.
The drudge, taken whole
Long tasks run to the end.
Exports, renames, forms, filing: hand over the whole chain. When a decision is not its to make, the run stops and names the choice in one line — instead of settling it for you.
Your seat is kept
Two workers, zero waiting.
Relam keeps its own cursor and keyboard and times each step between yours. The run carries you instead of replacing you. You work. Nobody is asked to leave.
Data stays in place
Your machine is the boundary.
Computer and browser work runs in an isolated environment. Relam sees only the moments each step needs. Nothing from your disk is copied elsewhere. There is no second copy of your machine to lose.
Orders, receipts, reports — moved between apps, filed where you said. No window kept in focus.
Web work
The site that needs coaxing.
Order numbers grabbed, return forms filled, sessions kept open. The browser steps a good cursor goes to die on.
Careful edits
The change you must not get wrong.
Renames, cleanups, sheet edits — each arrives with a preview of exactly what will move, before anything does.
Your own work
The half-day you keep.
Give Relam the mechanical half. Write the other half in the same window. One afternoon back.
Computer Use FAQ
Before you begin.
Computer Use covers your whole machine: files, folders, apps. Browser Use is the same idea inside Chrome — pages read, forms filled, tabs managed. Same approvals. Same rules.
Computer Use covers your whole machine: files, folders, apps. Browser Use is the same idea inside Chrome — pages read, forms filled, tabs managed. Same approvals. Same rules.
Yes. Your cursor and keyboard stay yours. Relam works in its own region of the same window. Never paused, never interrupted, never asked to step aside.
Yes. Your cursor and keyboard stay yours. Relam works in its own region of the same window. Never paused, never interrupted, never asked to step aside.
Delete, submit, pay, send — each stops first. You see the exact step, then approve or decline. These never run on their own.
Delete, submit, pay, send — each stops first. You see the exact step, then approve or decline. These never run on their own.
Only the screen moments each step needs, only to choose the next action. Nothing from your machine is copied elsewhere. Permissions stay exactly what you granted.
Only the screen moments each step needs, only to choose the next action. Nothing from your machine is copied elsewhere. Permissions stay exactly what you granted.
Instructions compete with everything else a model carries into a step, and they never apply the same way twice. Relam’s holds are code, checked on every action. “Do not delete” becomes “cannot delete without you.”
Instructions compete with everything else a model carries into a step, and they never apply the same way twice. Relam’s holds are code, checked on every action. “Do not delete” becomes “cannot delete without you.”
It stops and shows what it aimed at versus what happened. Risky steps always wait for you first — a misread row cannot become lost data.
It stops and shows what it aimed at versus what happened. Risky steps always wait for you first — a misread row cannot become lost data.
Relam Computer Use
Keep your hands. Share the work.
Start with the task you keep putting off. Relam takes it from there — while you stay at your machine, doing yours.
