> ## Content Index
> Fetch the complete content index at: https://blog.cloud-station.io/llms.txt
> Use this file to discover other available public pages before exploring further.

# Put an agent on a job in one step, and check its work
- URL: https://blog.cloud-station.io/changelog/hiring-an-agent-in-one-step/
- Published: 2026-09-19T10:00:00.000Z
- Updated: 2026-09-22T10:48:21.000Z
- Description: Describing a job is now enough: the right agent is chosen, started and reported back in one action. Charlie also checks what a finished agent claims against what it actually did.
- Author: Oumnya Benhassou
- Tags: #changelog, #cat-agents, #tr-hiring-an-agent-in-one-step

Putting an agent on a job used to be three separate steps: create it, tell it what to do, then wait and check. It is now one.

You describe the job. The right agent is chosen, given the skills it needs, started, and reported back to you. If something the job depends on cannot run here, you are told at that moment rather than after it fails.

When the work comes back, Charlie checks the claims against what the agent actually did before passing it on.

## What you can do now

- Describe a job and have the right agent picked and started in one step.
- Find out up front if something the job needs is not available.
- Define a team in advance and have the coordinator use only those people, in the order you set.
- Approve a step as the work reaches it, rather than watching for it.
- See a pass or fail verdict on a finished job instead of a claim.

## Why it matters

The gap between asking for something and it being underway is where delegation breaks down. Every extra step is a chance to pick the wrong agent, forget what it needs, or leave a job sitting.

Checking the work closes the other end. An agent reporting its own success is the weakest link in any handoff, and a verdict based on what it actually did is worth more than a summary it wrote about itself.

## Example workflows

- **Agency delivery:** A brief becomes a running job with the right specialist on it, in one message.
- **Operations:** A defined team handles a recurring process the same way every time.
- **Reviews:** A finished draft comes back with a verdict, not just a claim that it is done.
- **Handoffs:** A missing requirement surfaces before the work starts, not after it fails.

## What’s next

We're extending the same checks to longer jobs that run across several agents.