---
title: From Agent to Agent
link: https://ampcode.com/news/from-agent-to-agent
source: ampcode-com
published: 2026-07-17T00:00:00Z
updated: 2026-07-17T00:00:00Z
first_seen: 2026-10-03T23:09:50.514863041Z
summary: 'You can now ask your agents in Amp to spawn other agents. In orbs, your local machine [^1], or on any other machine. They can send messages and files to each other, too. You can have agents in orbs work on side quests while you continue your work: Spin up an orb thread with what you know about this unrelated bug, ask it to fix it, then keep working here. Or fan out work: Run four low-mode threads in parallel to test this flow in Chrome at four screen sizes and report back with screenshots. Find and continue old work by pulling in the important files: Pull the files from my abandoned prototype thread into this workspace and integrate the useful parts into our current approach. Offload work to another machine: Start a new thread on cloud-dev-box and upload this test matrix we created. Ask it to run through each row at least 10 times. Coordinate cross-project work: Spawn an agent in the docs project, send it what it needs to document this API change, and ask it to report back. Agents running locally, or in orbs, or anywhere else, and sending messages and files to each other? It''s a whole new world.'
content: extracted
html: 2026-07-17-from-agent-to-agent.html
preview:
  file: 2026-07-17-from-agent-to-agent.preview-c4404a4125ed.webp
  width: 256
  height: 134
  color: '#685d4b'
images:
- source: https://ampcode.com/og?_template=news&_version=7&title=From+Agent+to+Agent&date=July+17%2C+2026&tagline=Agents+can+spawn+other+agents%2C+message+them%2C+and+exchange+files+across+Amp+threads.&backgroundImage=https%3A%2F%2Fstatic.ampcode.com%2Fnews%2Ffrom-agent-to-agent-background.jpg&sig=b56aae918c2f90ff2572841b70412fad9981b339c508e76ebcae9e143571b953
  original:
    file: 2026-07-17-from-agent-to-agent.image-d54a848158ab.png
    width: 1200
    height: 630
  variants:
  - file: 2026-07-17-from-agent-to-agent.image-2f3188244273.webp
    width: 320
    height: 168
  - file: 2026-07-17-from-agent-to-agent.image-607c9e90daad.webp
    width: 640
    height: 336
  - file: 2026-07-17-from-agent-to-agent.image-5df9ba4f1f45.webp
    width: 960
    height: 504
  - file: 2026-07-17-from-agent-to-agent.image-12e31d4492e5.webp
    width: 1200
    height: 630
  color: '#272315'
- source: https://static.ampcode.com/news/from-agent-to-agent-handoff.png
  original:
    file: 2026-07-17-from-agent-to-agent.image-df552308f07c.png
    width: 1492
    height: 772
  color: '#1e2021'
---

You can now ask your agents in Amp to spawn other agents. In [orbs](https://ampcode.com/news/agents-in-orbs), your local machine , or on [any other machine](https://ampcode.com/news/agents-anywhere).

They can send messages and files to each other, too.

![An Amp agent creating a new thread in an orb and uploading the changed news post](https://static.ampcode.com/news/from-agent-to-agent-handoff.png)

You can have agents in orbs work on side quests while you continue your work:

```
Spin up an orb thread with what you know about this unrelated bug,
ask it to fix it, then keep working here.
```

Or fan out work:

```
Run four low-mode threads in parallel to test this flow in Chrome
at four screen sizes and report back with screenshots.
```

Find and continue old work by pulling in the important files:

```
Pull the files from my abandoned prototype thread into this workspace
and integrate the useful parts into our current approach.
```

Offload work to another machine:

```
Start a new thread on cloud-dev-box and upload this test matrix
we created. Ask it to run through each row at least 10 times.
```

Coordinate cross-project work:

```
Spawn an agent in the docs project, send it what it needs to
document this API change, and ask it to report back.
```

Agents running locally, or in orbs, or anywhere else, and sending messages and files to each other? It's a whole new world.