AutoGo · Build your own Aurix agents

Describe the process. Ship an agent your IT team will approve.

AutoGo Agent Builder turns a plain-English description of a back-office task into a compiled, tested agent that runs as a service on your own servers. Every agent is built inside guardrails, tested on your sample files, and runs on Aurix, the same engine behind the AutoGo agents we deliver.

Book a demo See how an agent is built

✓ Runs on your infrastructure✓ Readable source code✓ Tested before export

AutoGo Agent Builder — vendor-payment-router

← SessionsChatCode

build: greentest: passed ▶ Run TestBuildExport ▾

YouWhen a bank payment-advice email arrives, find the beneficiary in our vendor list and forward the advice to that vendor's email address.
Agent BuilderYour vendor list has two email columns, "E-Mail" and "Finance E-Mail". Which one should receive payment advices?⏳ Waiting for your reply
YouFinance E-Mail. Fall back to E-Mail if it's blank.
Writing MyAgent.cs
Build blocked: File.ReadAllText isn't allowed, switching to ctx.Data
Building the agent: succeeded
Running a test on advice-sample.html: passed
Agent BuilderDone. The test advice for ACME SUPPLIES SDN BHD was matched and forwarded to its finance contact. Ready to export when you are.

Describe what the agent should do…

☐ Try harderSend

USAGE · Trial: $0.38 used · $4.62 of $5.00 left

AutoGo Agent Builder — vendor-payment-router

← SessionsChatCode

MyAgent.csCodeDiff

1[AgentMetadata(Id = "vendor-payment-router")]
2public class VendorPaymentRouter : AgentBase
3{
4  public override async Task<JobOutput> ProcessAsync(
5      JobInput input, IAgentContext ctx, CancellationToken ct)
6  {
7    var advice  = ParseAdvice(input.Files[0]);
-    var csv = File.ReadAllText(@"C:\finance\vendors.csv");+    var vendors = await LoadVendorsAsync(ctx.Data, ct);9    var vendor  = vendors.Match(advice.Beneficiary);
10   ctx.Logger.Information("Matched {Vendor}", vendor.Name);
11   ...

You describe the task in chat. The Builder asks when something is unclear, fixes its own build errors, and tests before you can export. Switch to Code view at any time to review the source, and watch model usage and remaining credit as you build.

Why enterprises stall on AI agents

Most agent projects die between the demo and production.

Prototype agents

Impressive in a demo. Rejected at security review.

A model with open access to files, the network and credentials is hard to sign off. Nobody can say exactly what it will do on a bad day.

Screen-scraping RPA

Breaks every time a layout changes.

Recorded clicks are brittle, licences are per bot, and every fix waits on a specialist.

Custom development

Weeks of work for each small process.

Every automation needs its own scaffolding for logging, retries, scheduling and deployment before any business logic gets written.

AutoGo Agent Builder takes a different approach. The AI writes the agent; the agent itself is ordinary compiled code with a fixed, audited set of things it is allowed to touch. You get the speed of describing work in plain English and the predictability of software your team can read, test and version.

How the approaches compare	AI prototype agentmodel with open access	Screen RPArecorded clicks	Custom developmenthand-built service	AutoGo Agent Builder
Built from a plain-English description
Access limits enforced, not just requested
Keeps working when a screen layout changes
Source code a developer can review
Monitoring, retries and restart recovery built in

Yes Partly No

How it works

From a description to a running service in one sitting.

The Builder handles the plumbing every agent needs (registration, heartbeat, job claiming, recovery after restart) so the generated code only contains your business logic.

01You
Describe the task in chat
Tell the Builder what should happen, in plain English, or start from a template. Point it at the reference files it needs, such as a vendor list or rate table.
02Builder
It writes and compiles
The Builder writes the agent, compiles it, and reads its own build errors. Anything outside the guardrails fails the build and gets fixed.
03Builder + you
It tests on your samples
Drop in real sample files. The agent runs in a sandbox with dummy secrets until the output is right. If something is unclear, the Builder asks you.
04You
Export one file
Export produces a single self-contained executable with encrypted settings and install instructions. No runtime to install.
05Aurix
Run and monitor
The agent registers with the Aurix Control Centre and starts taking jobs from email, schedules, folders or the dashboard.

AutoGo Agent Builder — vendor-payment-router

← SessionsChatCode

MyAgent.csCodeDiff

1[AgentMetadata(Id = "vendor-payment-router")]
2public class VendorPaymentRouter : AgentBase
3{
4  public override async Task<JobOutput> ProcessAsync(
5      JobInput input, IAgentContext ctx, CancellationToken ct)
6  {
7    var advice  = ParseAdvice(input.Files[0]);
-    var csv = File.ReadAllText(@"C:\finance\vendors.csv");+    var vendors = await LoadVendorsAsync(ctx.Data, ct);9    var vendor  = vendors.Match(advice.Beneficiary);
10   ctx.Logger.Information("Matched {Vendor}", vendor.Name);
11   ...

Code view

Chat for the business user. Code for the reviewer.

Switch any session to Code view to read the agent's source, and use Diff to see exactly what the last message changed. Your developers review a single short file before anything reaches production.

Run Test

Run Test pre-filled from last run

About this agentVendor Payment RouterForwards bank payment advices to the matching vendor's finance contact.

Sample input files

htmladvice-sample.html18 KB

htmladvice-unknown-vendor.html17 KB

+ Add files

Folders, browser & secrets

Reference data folder ctx.Data (read-only)

C:\Data\VendorRoute

Test secrets ctx.Secrets

smtp.password

•••• set

CancelRun

Test on real samples, safely

Drop in the files the agent will really receive, including the awkward ones. Test runs use sandboxed folders and secrets that exist only for the test.

Export Agent

Export Agent pre-filled from this session

Connection

Control Centre URL

https://controlcentre.example.com

Target runtime

Windows x64 (.exe) ▾

Capabilities on the target machine

Reference data folder ctx.Data

D:\AutoGo\VendorRoute

Browser allowed hosts ctx.Browser

blank = browser disabled

This agent reads smtp.password via ctx.Secrets. Values are not exported. The README tells the operator where to set them.

CancelPublish

Export for the machine it will run on

Pick Windows, Linux or macOS. Production folders and the Control Centre address are sealed into encrypted settings, and passwords never leave your hands.

Governance by design

Guardrails are enforced by the compiler, not by a prompt.

Instructions to an AI can be ignored. A failed build cannot. Every agent can only reach the outside world through a small set of approved doors, and the build fails if the code tries any other route.

Green doors are the only side-effect surface an agent has. Red calls fail the build with an error that points to the approved alternative.

At build time

Banned-API analyzer

A compiler rule rejects direct file, network, process, registry and environment access, hardcoded paths and raw browser drivers.

At build time

Package allowlist

Agents can use three vetted, version-pinned libraries for Excel, CSV and local OCR. Any other package fails the build.

During testing

Sandboxed test runs

Test runs are isolated child processes with a 5-minute timeout and memory and CPU caps, a file jail, and dummy secrets so real keys never reach a test.

In production

Allowlisted hosts, encrypted settings

Browser automation only reaches hosts you list. Server URL and agent token ship encrypted. Secret values are never exported with the agent.

Always

Readable, reviewable code

Each agent is one C# file. Code view shows the source and a diff of every change, so developers can review it and keep it in source control.

If generated code tries	The build fails and points to
`File.ReadAllText(@"C:\finance\vendors.csv")`	`ctx.Data.OpenReadAsync("vendors.csv")`
`new HttpClient()`	`ctx.Http`
`Environment.GetEnvironmentVariable("API_KEY")`	`ctx.Secrets.Get("erp.api_key")`
`Console.WriteLine(...)`	`ctx.Logger`

Operate at scale

One Aurix Control Centre for every agent you deploy.

Aurix Control Centre — Agents

AgentsJobsSubmit jobMail rulesTriggersAudit log

6Agents online

1,284Jobs today

98.6%Succeeded

7Need review

Agent	Status	Trigger	Last heartbeat	Jobs today
vendor-payment-router	Active	mail	12 s ago	214
ar-journal-processing	Running	folder	4 s ago	532
ar-matching	Active	schedule	21 s ago	389
einvoice-submitter	Review queue	api	9 s ago	149
sdr-outreach-drafter	Paused	manual	2 h ago	0

Agent

Status

Trigger

Last heartbeat

Jobs today

vendor-payment-router

Active

mail

12 s ago

214

ar-journal-processing

Running

folder

4 s ago

532

ar-matching

Active

schedule

21 s ago

389

einvoice-submitter

Review queue

api

9 s ago

149

sdr-outreach-drafter

Paused

manual

2 h ago

Trigger jobs the way work already arrives

Route matching emails to an agent, run on a schedule, pick up files dropped in a folder, or submit by hand from the dashboard.

email ruleschedulefolder dropdashboardAPI

See every job

Each job records its inputs, progress, output files, metrics and final status. Failed jobs show the agent's own log lines.

Survives restarts

Agents send a heartbeat, claim jobs from a central queue, and pick up where they left off after a reboot. That behaviour is part of the platform, not something each agent has to get right.

Illustrative dashboard. Figures are examples.

How it fits together

Agents and your data stay inside your network.

Agents call out to the Aurix Control Centre to claim work and report results. Nothing needs to call in to your servers.

What agents can do

Wide enough for real back-office work. Narrow enough to trust.

ctx.Files

Process documents

Read the files attached to a job and write output files back: PDFs, HTML emails, text and JSON.

ClosedXML · CsvHelper

Excel and CSV

Parse spreadsheets with odd header rows, reconcile ledgers, and produce formatted Excel reports.

Tesseract

Local OCR

Pull text out of scanned documents on your own machine, without sending pages to an outside service.

ctx.Http · ctx.Secrets

Call your systems

Post to ERP, e-invoicing and internal APIs, with credentials kept in a secrets store and out of the code.

ctx.Browser

Web portals without APIs

Headless browser automation for portals that have no API, restricted to hosts you allow and checked on every action.

ctx.Data · ctx.Workspace

Reference data and working folders

Read lookup tables like vendor lists or rate cards, and work inside a shared folder you nominate.

Built on Aurix

Agents running in finance and operations today.

Accounts payable

Vendor payment advice routing

Bank advice email→Extract beneficiary→Vendor list lookup→Forward to vendor

Payment advices from the bank are read as they arrive, matched against the vendor master, and sent on to the right supplier.

Accounts receivable

AR journal processing and matching

Statements and remittances→Parse lines→Match to invoices→Journal file

Incoming remittances are matched to open invoices and turned into journal entries ready for the ERP, with exceptions listed for a person to resolve.

Tax and compliance

E-invoice submission

Invoice data→Validate fields→Submit to tax API→Store response

Invoices are validated and submitted to the e-invoicing system, and every acknowledgement or rejection is kept with the job.

Sales

Prospect research drafts

Prospect details→Public research→Match product→Draft email for review

The agent researches a prospect and drafts a short, specific email. It only drafts: a person reads and sends every message.

Looking for a ready-made agent instead? See the AutoGo agents we deliver.

Deployment and data

Your servers, your data, your keys.

Runs where you choose

Agents install as a service on your servers or cloud VMs: Windows x64, Linux x64 and arm64, or macOS.

One engine for every agent

Agents you build register with Aurix just like the AutoGo agents we deliver: one queue, one dashboard, one job history.

Bring your own model key

Use the managed key that comes with your trial, or connect your own Anthropic account and keep billing in your name.

Cost visible as you build

The Builder shows model usage and remaining trial credit while you work, so there are no surprise bills.

publish/ — VendorPaymentRouter

# What Export produces
VendorPaymentRouter.exe            ~70 MB, self-contained, no runtime to install
appsettings.production.json        encrypted: Control Centre URL, agent token, config
README.txt                         install steps and the secret names this agent needs

> VendorPaymentRouter.exe --install-service
> sc start AIAgent.vendor-payment-router
✓ Registered with Control Centre · waiting for jobs

Questions from IT and finance

Frequently asked questions

How does Agent Builder relate to Aurix and AutoGo?+

Aurix is the engine every AutoGo agent runs on. Agent Builder is how your team builds its own Aurix agents, instead of waiting for us to build each one. Agents you build sit alongside the ones we deliver, in the same Control Centre.

Do we need C# developers to build agents?+

No. Analysts and operations leads build agents by chatting with the Builder and testing on sample files. Developers are useful for reviewing code before production, and the code is short and readable for that purpose.

What stops an agent from doing something it shouldn't?+

Three things. The compiler rejects any code that touches files, the network, processes or the registry outside the approved context. Testing happens in a resource-capped sandbox with dummy secrets. In production, browser access is limited to hosts you list and credentials live in a secrets store, not in code.

Does our data go to an AI provider?+

While building, the task description and generated code are sent to the model. Your test files stay on the machine running the Builder. Deployed agents only call an AI model where a step needs one, such as summarising text, and only through the approved HTTP surface.

How is this different from RPA?+

RPA replays recorded clicks and breaks when a screen changes. Aurix agents work with files, data and APIs directly, and use a browser only where a portal has no API. Each agent is one code file you can version and review.

Can we change an agent after it's deployed?+

Yes. Reopen the session, describe the change in chat, re-test on your samples, and export a new version. Your developers can also edit the code directly.

Is it available on-premise?+

Agents always run on your infrastructure. The Aurix Control Centre is available as a managed service or installed in your own environment for data-residency requirements.

Bring one process. Leave with a working agent.

We'll build an agent with your team on one of your real back-office tasks, using your sample files, and show it running in the Aurix Control Centre.

Book a demo See delivered agents

Describe the process. Ship an agent your IT team will approve.

Most agent projects die between the demo and production.

Impressive in a demo. Rejected at security review.

Breaks every time a layout changes.

Weeks of work for each small process.

From a description to a running service in one sitting.

Describe the task in chat

It writes and compiles

It tests on your samples

Export one file

Run and monitor

Chat for the business user. Code for the reviewer.

Run Test pre-filled from last run

Test on real samples, safely

Export Agent pre-filled from this session

Export for the machine it will run on

Guardrails are enforced by the compiler, not by a prompt.

Banned-API analyzer

Package allowlist

Sandboxed test runs

Allowlisted hosts, encrypted settings

Readable, reviewable code

One Aurix Control Centre for every agent you deploy.

Trigger jobs the way work already arrives

See every job

Survives restarts

Agents and your data stay inside your network.

Wide enough for real back-office work. Narrow enough to trust.

Process documents

Excel and CSV

Local OCR

Call your systems

Web portals without APIs

Reference data and working folders

Agents running in finance and operations today.

Vendor payment advice routing

AR journal processing and matching

E-invoice submission

Prospect research drafts

Your servers, your data, your keys.

Runs where you choose

One engine for every agent

Bring your own model key

Cost visible as you build

Frequently asked questions

Bring one process. Leave with a working agent.