Australis
DocsPricingFor Work
Get the beta
Agents

Agents that work for you,
never around you.

Two agents, one rule: you approve. Ozzy plans and builds in Canvas, and the code agent proposes diffs in Code — with an independent verifier checking both.

Can I review what the agent changes?

In Code view, the agent never touches your files directly. Every change arrives as a diff — what's added, what's removed, per file — and you accept or reject it. Rejected work vanishes without a trace.

Claude writes the code on every build. Verification runs separately, so the check never comes from the thing being checked.

Agent — working on "make the table sortable"00:12
src/components/AssetTable.tsx+14 −3
@@ AssetTable @@
- const shown = assets;
+ const [sort, setSort] = useState<"name" | "due">("name");
+ const shown = [...assets].sort(by(sort));
RejectAccept
Ozzy, in Canvas

Plans with you, builds only after you approve, and narrates in plain words. Every build ends with a verification receipt, never a claim.

The code agent, in Code

Works your open project through reviewable diffs and ⌘K inline edits. It proposes; you decide; the gate re-verifies.

Can the agent talk its way past verification?

Verification runs independently of whichever model wrote the code — the builder never grades its own work.

Request the betaHow verification works
© 2026 Australis Technologies Pty Ltd · ACN 700 968 930 · 1B Talbot Place, Ingleburn NSW 2565, Australia · +61 434 046 046. All rights reserved.
PrivacyTermsDPA & subprocessorsSecurity