Jargon:Background agent
2 min read
Say this at the party
“An AI you hand a job to and then walk away from. It works on its own computer somewhere else and lets you know when it's finished.”
In plain English
A normal AI chat is like a phone call. You ask, you wait, it answers. A background agent is more like leaving a note for a helper and going off to do something else. (An agent is an AI that can take steps by itself, not just chat.)
It doesn't run on your own laptop. It usually works on a copy of your project on a separate computer "in the cloud", which just means a company's computers. When it's done, it sends you the changes to look over. So far it's mostly used by programmers.
Because each agent gets its own computer, you can start several at once. Any one job isn't faster, and some take up to half an hour. The win is having lots of small jobs ticking along at the same time whilst you get on with your day.
Where it came from
"Background" is an old computing word for jobs that run whilst you do something else. The exact name took off with Cursor, a coding app, which said on 15 May 2025 that its agents "can now run in the background". The same week, OpenAI launched Codex (16 May) and Google opened up Jules to everyone (20 May), after first showing it in December 2024. Nobody really coined it, and the name is already shifting: Cursor now calls them Cloud Agents, and GitHub says coding agent.
See it in action
A developer asks Google's Jules to update a website project to a newer version of Node.js (a common building block for websites). It's a dull, careful job. She closes the page and goes to a meeting. When she's back, the changes are waiting for her to check and approve.
What people get wrong
- It isn't an AI secretly running on your computer. You start it, and it usually works on a copy of your project on a separate cloud computer.
- It isn't set and forget. Each job comes back as changes for you to check before anything is used, and Cursor says that checking is now the main hold-up.
- It isn't faster for a single job. OpenAI says a Codex job usually takes between 1 and 30 minutes. The gain is running several jobs at once.
- More agents doesn't always mean more done. Ten agents means ten piles of work to check, and the person checking becomes the hold-up.
Where Ugenie fits
Ugenie hands your tasks to the AIs you already use. Background agents are one way those AIs can get on with the work whilst you get on with yours.
Get Ugenie →Go deeper
- PostCursor, 2025Simplified Pricing, Background Agent and Refreshed Inline Edit · CursorThe May 2025 update that put the name Background Agent on the map.
- PostKathy Korevec, Google, 2025Jules: Google's autonomous AI coding agentGoogle's asynchronous coding agent, with a demo of it updating a project in the background.
- ArticleAndrea Griffiths, GitHub, 2025The difference between coding agent and agent mode in GitHub Copilot - The GitHub BlogA clear side by side of an AI that works with you live versus one that works while you're away.
- GuideAnthropic, 2026Claude Code on the web | Claude Help CenterStep by step: give Claude a task, leave the page, and get changes back to review.
- ArticleViktor Eriksson, PCWorld, 2026Claude can now click and type in the background while you work | PCWorldAn early sign of background agents moving beyond coding into everyday computer jobs.
Related jargon
Drafted with AI. The AI Council (Claude, ChatGPT and Gemini) gave counsel. Phin signed it off.