It learns the work from the people who do it.
Process documents describe the job as it should go. Your experts know how it actually goes: which screen they check first, which exception they always catch, which customer gets a call instead of an email. Observer captures that, so AIOS builds from what your experts do, not from what someone typed into a prompt.
Three ways in.
Record a process. The expert does the job and talks it through. AIOS watches, asks questions wherever something is unclear, and writes the workflow.
Describe it first. Explain the process in chat. AIOS asks to watch when it has enough to go on.
a cohort study. Pick a team, ask one question and set a window. AIOS finds the routines they repeat and where they stop to decide.
What Observer does.
Nobody writes a requirements document. The expert keeps doing their job for an afternoon, and AIOS takes the notes.
Record the work as it happens.
The expert does the job on screen and talks it through. AIOS records what they open, what they decide and what they do.
Ask why, not just what.
AIOS asks about the judgment calls it saw: why this document, why that exception, what would change the answer. It asks out loud when the expert is ready, and in writing after the recording. The reasoning goes into the workflow beside the steps.
Build once, when the expert is ready.
Nothing is built while they work. When they choose Review & create, AIOS writes the whole workflow in one pass, ready for your team to read.
Sensitive values stay on the machine.
Account numbers and personal details are masked in captured frames on the expert's own computer, before anything leaves it. Your admin decides what gets masked.
Or describe it first.
No time to record? Explain the process in chat, and AIOS asks to watch when it has enough to go on. Or it builds straight from the description and shows you the plan first.
When AIOS asks, and why.
AIOS never interrupts the work. While the expert works, it keeps a list of what it couldn't learn by watching, and asks when they're ready.
It notices what watching can't explain.
Why this option and not that one. Where a number came from. Why they waited, who has to approve, what happens when something fails. Each goes on the list as it comes up.
It drops what's already answered.
Experts explain a lot as they go. When they have already covered something out loud, the question comes off the list without being asked.
It asks first about what changes the workflow.
A question whose answer would change the steps goes to the top. “What starts this each time?” is always on the list.
It raises a hand and waits.
When a question is ready, a hand goes up on the recording bar. The expert says “go ahead” or taps Ask now, and AIOS asks a few out loud. “Later” puts them off.
It asks for an example when an answer is vague.
“It depends” gets one follow-up: tell me about a recent case. That is usually where the real rule is.
Anything left waits for the review.
After the recording, AIOS asks what is still open in writing and points to the moment it saw: “In your second recording at 3:42…”. Each answer is kept as the reason behind that step of the workflow.
How it compares.
The first two rows are offered in full by none of the four alternatives.
| Capability | AIOScvlSoft | Agent platformsOpenAI Frontier, Anthropic | Service agentsSierra, Fin, Decagon | AutomationUiPath, Power Automate | In-app agentsSalesforce Agentforce |
|---|---|---|---|---|---|
| Watches an expert work and drafts the workflowThe desktop Observer records what they open, decide and do, then asks why. | |||||
| Interviews your experts and writes it downTheir answers become steps, systems and reasoning your team approves. | |||||
| Builds from a plain descriptionDescribe the process. It shows a plan first, then builds, checks and test-runs it. |
A category view, not a product audit: each column names one or two examples, and individual products vary. See all 33 rows
Questions.
Does the expert have to write anything down?
No. They do the work and talk it through. AIOS writes the workflow, and they review it with your team in plain English.
What does Observer see?
The expert's screen while they record, and only then. Sensitive values are masked on their computer before any frame leaves it, under rules your admin sets.
Will AIOS interrupt the expert while they work?
No. It notes its questions as it watches and raises a hand when one is ready. It asks out loud only when the expert says go ahead, and anything left over is asked in writing after the recording.
Can we start without recording anything?
Yes. Describe the process in chat and AIOS shows a plan before it builds. Recording is the faster way to capture the judgment calls a description leaves out.
Who builds the first one?
cvlSoft does the initial build. AIOS interviews your expert, your team reviews the workflow, and an expert signs off before it goes live.