Automation
RPA software that builds working apps, not brittle click scripts
Classic RPA software copies what a person does on screen, so it breaks the day a screen changes. AgentCode takes the same processes, writes real code for them, and hands your team a small web app that keeps running.
You describe the work · the agent writes the code · your team reviews before anything goes live
In short
RPA, or robotic process automation, is software that carries out repetitive office work the way a person would: opening systems, copying values between them, and following a fixed set of rules. Traditional robotic process automation software records those clicks and replays them. AgentCode reaches the same result from the other side. You describe the process in plain language, the agent writes code that performs it, and what you are left with is an application your company owns.
What the agent builds instead of a bot
- A web form that replaces the spreadsheet your team fills in weekly
- Code that reads the files from a folder and posts the results onward
- A reconciliation screen that flags the rows a person needs to review
- Logic your own systems can call directly, with no screen to click
- Clear error handling, so a failed run tells you exactly what broke
- Tests your team runs before any change reaches the live process
A process from Finance
The problem
Every Monday someone exports three reports, pastes them into one spreadsheet and fixes the columns by hand before the close meeting. One person knows which column goes where.
What the agent builds
The agent writes a small web app that takes the three exports, matches them on invoice number, and shows the merged view with the mismatches at the top.
What you end up with
A page your finance team opens instead of a spreadsheet, a short list of rows that genuinely need a decision, and the code behind all of it in your own repository.
What RPA software is and how it works
Robotic process automation software automates work by imitating a person at a keyboard. A designer records or draws the steps, the tool identifies buttons and fields on the screen, and a software robot repeats the sequence on a schedule or on demand. Products in this category usually split into three parts: a studio where processes are drawn, robots that run them, and an orchestrator that queues the work.
- Attended robots sit on a desktop and help a person during a task
- Unattended robots run on a server against a queue of items, often overnight
- Screen selectors tell the robot where to click, which is where most breakages start
- Orchestration handles retries, logging and the order in which items are processed
The category earned its place because it needs no change to the systems underneath. That is also its limit. A robot that reaches into a screen depends on that screen staying exactly where it was, so a routine interface update upstream becomes an outage for your process. For the other route to the same outcome, read how it works.
Why AgentCode writes code instead of recording clicks
AgentCode is an automation platform for companies, not a recorder. You explain the process in the panel the way you would explain it to a new colleague: where the data starts, what has to happen to it, who checks the result. The agent reads your existing code, writes a plan, changes the files, runs your tests, and gives the finished change back for a person to approve. Nothing merges on its own.
The practical difference shows up in three places.
- A code path does not care where a button moved to, so a redesign upstream does not stop the run
- The logic is readable, so a new person can see what the process does without opening a diagram
- The work belongs to you: the code sits in your repository and stays there whatever you decide about your subscription
The output is a small application rather than a robot licence, which is why teams here usually end up with a shelf of them. See internal tools for the shape of what comes out.
Processes finance teams hand over first
Finance teams reach for robotic process automation software because their work is rule based and repeats on a calendar. The same processes suit an agent that writes code, and the result is easier to audit, because every rule is written down in one place rather than embedded in a recording.
- Invoice data pulled out of files and posted to the ledger, with the odd ones held back for a person
- Bank lines matched against open items, so only the unmatched rows need attention
- Month end packs assembled from several exports instead of pasted together by hand
- Supplier statements compared with your own records, line by line
- Expense claims checked against policy before anyone is asked to approve them
Most of this work touches a ledger and a spreadsheet, so QuickBooks and Excel are the usual starting points. When the process crosses into another department, read business process automation. Plans and limits are on the pricing page.
Questions teams ask
Is AgentCode RPA software?
It sits in the same place in your day and removes the same work, but the mechanism is different. Instead of a robot that clicks through an interface, you get code that performs the process directly plus a small web app your team opens. There is no recorder and no selector to repair after an interface update.
Do we need developers to use it?
No. The person who knows the process writes the description, in the language of their own department. The agent handles the code. A technical colleague usually reviews the change before it goes live, the same way any other change to a business system gets a second pair of eyes.
What happens when the source system changes?
Where a screen robot fails on a moved button, code fails only when the data itself changes shape. When that happens you describe the change in the panel, the agent updates the code and reruns your tests, and the result waits for a person to approve. The fix is a sentence rather than a rebuild.
Who owns the automations we build?
You do. The agent works on your repository at GitHub or GitLab, so every file it writes lands in your own version history. You can read it, change it, hand it to another team, or keep it running without us. We do not train on your code.
More the agent builds
Describe your first finance process
Tell the agent what happens every Monday morning, and get back an app that does it.