Getting started — your plain-language guide

Welcome. This product lets you run AI agents with confidence — knowing exactly what each one can do, how much it can spend, and that everything is recorded and verified. You don't need to be technical. If you can use a phone, you can use this.

This guide walks you through the handful of things you'll actually do. Each takes a minute or two. Do them in order the first time; after that, come back to any section as a reminder.

The one idea to hold onto: a new agent can do nothing until you allow it. You're never racing to lock things down — you start fully safe and open up only what you choose. Every screen is built around that.

There are only six things to know about in the whole product: Agents, Permissions, Budgets, Approvals, Stop, and Proof. That's it. For a quick definition of each, see the six concepts.

A 30-second tour

When you sign in, you land on the Dashboard. It answers one question: is everything okay?

A big, calm headline tells you the state: "Everything is governed" in green when all is well, or something like "2 approvals are waiting for you" in amber when you're needed.
Below it: how many agents are Safe, how many Needs attention, how many are Stopped, and total spend this month.
At the very bottom, a green strip reads "Verified — every action is governed and recorded." (On a phone it shows up top as a small "Verified" pill.) That's your ambient reassurance — tap it any time to see the proof.

Colors mean the same thing everywhere:

Color	Means
🟢 Green	Safe and on track
🟠 Amber	Needs your attention
🔴 Red	Stopped or blocked

📷 Screenshot: the Dashboard — see the prototype Dashboard screen. (The prototype shows the amber "needs you" state — "2 approvals are waiting for you" — so you can see what attention looks like.)

Connect a runtime (administrators)

Where: outside this app — your deployment's connector configuration. There's no button for this inside FeirOS.

A runtime is the place an agent actually runs — the harness FeirOS hands scoped credentials to instead of the agent itself. Before anyone can add an agent, at least one runtime has to be registered. That registration happens in your deployment's connector configuration (ask whoever operates this workspace's infrastructure — it's a config + restart step, the same shape as turning on enforcement below), not inside the web app. Once it's registered, FeirOS picks it up automatically.

Until a runtime is registered, the Agents screen's Connected runtimes panel says so plainly, and Add agent stays blocked — there's nothing to create an agent on yet.
Once it's registered, that same panel shows it as Connected — nothing further to do here.

1. Add your first agent

Where: the Agents screen → Add agent.

Adding an agent is a short, three-step dialog: Job, Guardrails, then Review. Nothing is created until you confirm on the last step.

Open Agents from the left menu. If you're new, you'll see: "No agents yet. Add your first — it'll start completely locked down, and you decide what it can do."
Click Add agent.
Job — say what it's called and who owns it:
- Name — what this agent is, in plain words (e.g. "Refund assistant").
- Owner — the person accountable for it. Pick a real human.
- What's it for? (optional) — a short note for your own reference, shown back to you in the review step.
- Advanced setup (optional, collapsed by default) — for operators who need to pick a specific connected runtime, import a saved profile, choose a model, or schedule a recurring job with a cron time and a prompt. Most people never need to open this; the agent's runtime is chosen for you automatically.
Click Next: Guardrails.
Guardrails — the two independent safety choices:
- Risk level — Low, Medium, or High: how consequential its actions are. There's a one-line explanation under each. (High means it can take actions that are hard to undo, like moving money — those actions ask for your approval by default.)
- How independently may it work — Observe only, Suggest actions, Act after approval, or Act within limits: how much it may do without asking you first. This starts at the most cautious option, Observe only.
- Monthly budget (optional) — a spending cap in dollars. Leave it blank for no limit.
Review — a plain-language summary of every choice you made. Check it, then click Create agent.

You'll land on a reassuring confirmation: "Agent created. It can't do anything yet — you choose what to allow." From there you can go straight to Set permissions (recommended — it starts with everything off) or View agent to see its detail page first.

That's the point. Your new agent exists, it's named, it has an owner — and it is completely safe, because it can't do a single thing until you say so.

💡 Tip: Risk level and independence are separate dials. Risk sets how consequential an allowed action is; independence sets how much it may do without asking. The riskiest actions still pause for your approval by default regardless of independence — you're always in control.

📷 Screenshot: the Add agent dialog's Guardrails step — see the prototype Agents screen.

2. Allow it to do one thing — safely

Where: open your agent (click its row in Agents) → Manage permissions.

Right now your agent can't do anything. Let's allow it one capability — only what it actually needs.

From the Agents list, click your agent to open its detail page.
Under What it's allowed to do, you'll see "Cannot do anything yet." Click Manage permissions.
At the top, a banner reassures you: "Everything is off unless you turn it on. An agent with nothing on is completely safe."
You'll see a plain list of capabilities, each switched Off — for example "Read customer data," "Send emails," "Issue refunds."
Turn on just the one you want. When you do, a short note appears inline:
- how risky it is, in plain words ("Refunds move real money and can't be undone."),
- and whether it asks for your approval each time. The riskiest capabilities are set to wait for you automatically — and you can turn that on for safer ones too. (Narrow limits like "only refunds under $500" aren't available yet.)
That's it. Leave everything else Off.

The golden rule: turn on only what the agent needs, one at a time. Every switch left off is one less thing to worry about.

💡 Why "off" is good: an off switch here isn't a gap you forgot to fill — it's protection working. The fewer things on, the safer the agent.

📷 Screenshot: the Permissions toggles with an inline risk note — see the prototype Permissions screen.

3. Set a budget

Where: Budgets in the left menu (all agents), or Manage budget on an agent's detail page (just that agent).

A budget is how much an agent can spend in a month — like a prepaid card.

Open Budgets, or click Manage budget on your agent.
Set a monthly cap — a simple amount. The screen phrases it plainly: "Stop spending around $500/month."
Watch the usage bar: it fills green, turns amber as it nears the cap, and red when it's reached.
Choose what happens when the cap is reached:
- Just alert me — keep running. (The in-product alert that tells you is coming; for now, the usage bar on this screen is where to look.)
- Slow it down — keep going, more carefully.
- Stop it — halt the agent. (Recommended for high-risk agents.)
Save. You can reset the count anytime with Reset this month's usage. (Showing exactly when the monthly count resets is coming.)

⚠️ An honest note about budgets. A budget is a smart limit, not a to-the-cent wall. Spending is watched continuously and acted on quickly, but a small overshoot is possible before a hard stop kicks in. So set your cap as "stop around here," not an exact ceiling. The screen reminds you of this too — it's there so you're never surprised.

📷 Screenshot: the Budget cap, usage bar, and the three on-cap choices — see the prototype Budgets screen.

4. Approve (or deny) a request

Where: Approvals in the left menu. A number badge shows how many are waiting; it turns amber when there's anything to do.

When an agent wants to do something risky that you set to need approval, it pauses and waits for you. Nothing happens until you decide.

Open Approvals. You'll see one simple card per waiting action:
- What it wants to do: "Refund assistant wants to issue a $240 refund to Acme Co."
- Why it needs you: "Refunds can't be undone."
- Who and when: which agent, how long it's been waiting, and when the request expires.
Click Approve to let it proceed, or Deny to stop it.
The card shows a short confirmation and drops off the list. The badge count updates.

A few reassurances:

If you don't decide in time, the request expires safely. The agent does not sneak the action through. Doing nothing is always the safe choice. (A visible log of expired requests is coming.)
When there's nothing waiting, you'll see the good state: "Nothing waiting. You're all caught up."

💡 The riskiest capabilities always wait for you here — the product sets that automatically. You can turn approval on for other capabilities too, in Permissions.

📷 Screenshot: an approval card with Approve / Deny — see the prototype Approvals screen.

5. Stop an agent

Where: the Stop button on any agent's detail page.

If something ever looks wrong — an agent behaving oddly, or you just want to be safe — you can stop it instantly. Think of it as the big red emergency-stop button on a machine.

Open the agent and click Stop.
A confirmation appears: "Stop [agent] now?" with a plain explanation: "It will stop immediately, lose its access, and be blocked from acting again until you turn it back on. Anything in progress stops at once."
Click Stop now to confirm (or Cancel to back out).
You'll see: "Stopped. It can't do anything else." The agent's status turns red everywhere it appears.

What this means in plain terms: the agent isn't just paused on one task — it's fully held back across everything it could do.

Bringing it back: a stopped agent shows a Restart agent button on its detail page. It comes back with the same permissions it had before — still subject to budget and approvals like any other agent. Anything it was doing when stopped does not resume on its own. So treat Stop as what it is: the emergency brake, not a one-way door.

📷 Screenshot: the Stop confirmation and the "Stopped. It can't do anything else." result — it appears as a confirm dialog on the prototype Agent detail screen.

6. Get a proof report

Where: Proof in the left menu, the green trust strip at the bottom, or View proof on any agent.

Proof is your evidence that everything was governed — a report you can hand to a board member, an auditor, or a regulator. It's like a receipt with a tamper-proof seal.

Open Proof. At the top is a Verified badge: "Verified. Nothing was tampered with."
Below it, a plain summary — one sentence per kind of activity:
- "1,204 actions — all governed."
- "38 approvals (32 approved, 6 denied)."
- "3 agents stopped — each fully blocked from acting."
- "Nothing in this record was altered."
Today the report covers your full record. (Focusing it by time range or by agent isn't available yet — the controls on the screen say so too.)
Click Export to produce a file you can share. You'll pick how much detail to include:
- Summary only (the default — safest, shares the least)
- Standard report
- Full evidence
A footer confirms: "This report is complete and verifiable. Anyone can independently confirm it wasn't changed."

⚠️ An honest note about proof. Proof shows what was governed and that the record is complete and unaltered — no one quietly changed it after the fact. It doesn't claim every action was correct in the real world; it faithfully records what happened and seals it so it can be trusted. That honest framing is exactly what makes it trustworthy to an auditor.

📷 Screenshot: the Verified badge, summary, and Export options — see the prototype Proof screen.

Turn on enforcement (administrators)

Where: the Control Center's would-block report — and your deployment's configuration, outside this app.

A new workspace starts in Observing mode: policies are evaluated but never enforced, so you can see exactly what would have been blocked before anything actually is. The Control Center shows a would-block report — what enforcement would have stopped in the observation window — with a Mark report as reviewed action once every category's evidence is visible.

Once the report is reviewed and current, the banner reads Ready to enforce. There's deliberately no in-app switch for the next step: turning on enforcement is a config + restart change an administrator makes in your deployment's configuration, the same way connecting a runtime is (see above) — never a button inside this web app. This page starts showing Enforcing automatically the next time it checks, once that change is live.

You're set up

That's the whole product. Day to day, you'll mostly just:

glance at the Dashboard to confirm everything's green,
clear any Approvals waiting for you, and
occasionally adjust a Permission or Budget.

If anything ever feels off, Stop is one click away — and Proof is always there to show everything was governed.

A good first-week routine:

Add one agent.
Turn on the single capability it needs (leave the rest off).
Set its budget and choose what happens at the cap.
Check Approvals once a day.
At month-end, open Proof and export a Summary — just to see how easy it is.

You started fully safe, and you only opened up what you chose. That's the whole idea.

Need a refresher on the six core ideas? See the six concepts.