{ "@context": "https://schema.org", "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2025-12-11-thread-map/#webpage", "@type": [ "WebPage", "ArchiveComponent" ], "articleBody": "Two days ago, Lewis wrote about [working with short threads](https://ampcode.com/200k-tokens-is-plenty) — a lot of them, connected via [handoff](https://ampcode.com/manual#handoff) and [thread mentions](https://ampcode.com/manual#referencing-threads) and forks. In his post, he showed a diagram, a *map* of one feature spread across 13 threads.\n\nThat map? It exists now, we built it:\n\n![Old whisperer of the orb reading a thread map](https://ampcode.com/\\(marketing\\)/news/thread-map2.jpg)\n\nRun `threads: map` in the [Amp CLI command palette](https://ampcode.com/news/command-palette) to try it out.\n\nYou'll see a top-down view of all threads connected to your current thread via mentions, handoffs, or forks. If you hit `Enter`, you'll open the selected thread and can continue your work there.\n\n(Yes, it's only available in the Amp CLI right now, but coming to other clients soon.)\n\nIf you only use handoff and forks occasionally, you might not need this yet. But if you do work with many short, connected threads — like [Lewis](https://ampcode.com/200k-tokens-is-plenty) or [Igor](https://x.com/bedesqui/status/1998374596144406754) — this map might make it even easier, because you can see the *shape* of your work.\n\nHere are some patterns we've noticed so far:\n\n## 1\\. Hub-and-Spokes\n\n![Bicycle spokes pattern](https://static.ampcode.com/news/thread-map-bicycle-spokes.png)\n\nOne thread will form a core from which many other threads can be created. This might be an initial implementation thread, or a context-gathering research thread. The spokes might be refactoring threads, or subfeatures. They don't need the context of the other spokes—by linking only to the hub thread, the context window of each spoke remains lean and relevant.\n\n## 2\\. Chain\n\n![Chains pattern](https://static.ampcode.com/news/thread-map-chains.png)\n\nMany short threads chained together. This is a common pattern when one change depends on another. This pattern often emerges when using the `handoff` feature to extract only the relevant context from a previous thread, allowing you to keep threads short but still continue serially dependent work. This is common in research or exploratory tasks, where the desired state is unknown.\n\nIt's not uncommon for the end of a chain to lead to the central node of a hub-and-spokes pattern; a desired state is found and work can be more easily parallelised.\n\n## What's Next?\n\nOur bet is that there are many more patterns out there, waiting to be recognised. Let us know what you find.\n\n![Thread map patterns](https://static.ampcode.com/news/thread-map-patterns-slow.gif)\n", "authors": [], "captured_at": "2026-10-03T23:09:50.514863041+00:00", "category": "programming", "content_html": "

Two days ago, Lewis wrote about working with short threads — a lot of them, connected via handoff and thread mentions and forks. In his post, he showed a diagram, a map of one feature spread across 13 threads.

\n

That map? It exists now, we built it:

\n

\"Old

\n

Run threads: map in the Amp CLI command palette to try it out.

\n

You'll see a top-down view of all threads connected to your current thread via mentions, handoffs, or forks. If you hit Enter, you'll open the selected thread and can continue your work there.

\n

(Yes, it's only available in the Amp CLI right now, but coming to other clients soon.)

\n

If you only use handoff and forks occasionally, you might not need this yet. But if you do work with many short, connected threads — like Lewis or Igor — this map might make it even easier, because you can see the shape of your work.

\n

Here are some patterns we've noticed so far:

\n

1. Hub-and-Spokes

\n

\"Bicycle

\n

One thread will form a core from which many other threads can be created. This might be an initial implementation thread, or a context-gathering research thread. The spokes might be refactoring threads, or subfeatures. They don't need the context of the other spokes—by linking only to the hub thread, the context window of each spoke remains lean and relevant.

\n

2. Chain

\n

\"Chains

\n

Many short threads chained together. This is a common pattern when one change depends on another. This pattern often emerges when using the handoff feature to extract only the relevant context from a previous thread, allowing you to keep threads short but still continue serially dependent work. This is common in research or exploratory tasks, where the desired state is unknown.

\n

It's not uncommon for the end of a chain to lead to the central node of a hub-and-spokes pattern; a desired state is found and work can be more easily parallelised.

\n

What's Next?

\n

Our bet is that there are many more patterns out there, waiting to be recognised. Let us know what you find.

\n

\"Thread

\n", "content_markdown": "Two days ago, Lewis wrote about [working with short threads](https://ampcode.com/200k-tokens-is-plenty) — a lot of them, connected via [handoff](https://ampcode.com/manual#handoff) and [thread mentions](https://ampcode.com/manual#referencing-threads) and forks. In his post, he showed a diagram, a *map* of one feature spread across 13 threads.\n\nThat map? It exists now, we built it:\n\n![Old whisperer of the orb reading a thread map](https://ampcode.com/\\(marketing\\)/news/thread-map2.jpg)\n\nRun `threads: map` in the [Amp CLI command palette](https://ampcode.com/news/command-palette) to try it out.\n\nYou'll see a top-down view of all threads connected to your current thread via mentions, handoffs, or forks. If you hit `Enter`, you'll open the selected thread and can continue your work there.\n\n(Yes, it's only available in the Amp CLI right now, but coming to other clients soon.)\n\nIf you only use handoff and forks occasionally, you might not need this yet. But if you do work with many short, connected threads — like [Lewis](https://ampcode.com/200k-tokens-is-plenty) or [Igor](https://x.com/bedesqui/status/1998374596144406754) — this map might make it even easier, because you can see the *shape* of your work.\n\nHere are some patterns we've noticed so far:\n\n## 1\\. Hub-and-Spokes\n\n![Bicycle spokes pattern](https://static.ampcode.com/news/thread-map-bicycle-spokes.png)\n\nOne thread will form a core from which many other threads can be created. This might be an initial implementation thread, or a context-gathering research thread. The spokes might be refactoring threads, or subfeatures. They don't need the context of the other spokes—by linking only to the hub thread, the context window of each spoke remains lean and relevant.\n\n## 2\\. Chain\n\n![Chains pattern](https://static.ampcode.com/news/thread-map-chains.png)\n\nMany short threads chained together. This is a common pattern when one change depends on another. This pattern often emerges when using the `handoff` feature to extract only the relevant context from a previous thread, allowing you to keep threads short but still continue serially dependent work. This is common in research or exploratory tasks, where the desired state is unknown.\n\nIt's not uncommon for the end of a chain to lead to the central node of a hub-and-spokes pattern; a desired state is found and work can be more easily parallelised.\n\n## What's Next?\n\nOur bet is that there are many more patterns out there, waiting to be recognised. Let us know what you find.\n\n![Thread map patterns](https://static.ampcode.com/news/thread-map-patterns-slow.gif)\n", "dateCreated": "2026-10-03T23:09:50.514863041+00:00", "date_created": "2025-12-11T00:00:00+00:00", "date_modified": "2025-12-11T00:00:00+00:00", "date_published": "2025-12-11T00:00:00+00:00", "description": "Two days ago, Lewis wrote about working with short threads — a lot of them, connected via handoff and thread mentions and forks. In his post, he showed a diagram, a map of one feature spread across 13 threads. That map? It exists now, we…", "external_url": "https://ampcode.com/news/thread-map", "git": { "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e", "path": "items/ampcode-com/2025/12/2025-12-11-thread-map.md", "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/ampcode-com/2025/12/2025-12-11-thread-map.md" }, "id": "urn:aggr:item:a3f2fc147b7c1567003aab4a2d0efeb647c43b24", "isBasedOn": { "@id": "https://ampcode.com/news/thread-map" }, "mainEntity": { "@id": "https://ampcode.com/news/thread-map", "@type": "CreativeWork", "archivedAt": { "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2025-12-11-thread-map/#webpage" }, "dateModified": "2025-12-11T00:00:00+00:00", "datePublished": "2025-12-11T00:00:00+00:00", "headline": "Thread Map", "timeRequired": "PT2M", "url": "https://ampcode.com/news/thread-map", "wordCount": 345 }, "name": "Archived snapshot: Thread Map", "preview": null, "reading_minutes": 2, "replicated_at": null, "source": "ampcode-com", "source_name": "Amp News", "summary": "Two days ago, Lewis wrote about working with short threads — a lot of them, connected via handoff and thread mentions and forks. In his post, he showed a diagram, a map of one feature spread across 13 threads. That map? It exists now, we built it: Run threads: map in the Amp CLI command palette to try it out. You'll see a top-down view of all threads connected to your current thread via mentions, handoffs, or forks. If you hit Enter, you'll open the selected thread and can continue your work there. (Yes, it's only available in the Amp CLI right now, but coming to other clients soon.) If you only use handoff and forks occasionally, you might not need this yet. But if you do work with many short, connected threads — like Lewis or Igor — this map might make it even easier, because you can see the shape of your work. Here are some patterns we've noticed so far: 1. Hub-and-Spokes One thread will form a core from which many other threads can be created. This might be an initial implementation thread, or a context-gathering research thread. The spokes might be refactoring threads, or subfeatures. They don't need the context of the other spokes—by linking only to the hub thread, the context window of each spoke remains lean and relevant. 2. Chain Many short threads chained together. This is a common pattern when one change depends on another. This pattern often emerges when using the handoff feature to extract only the relevant context from a previous thread, allowing you to keep threads short but still continue serially dependent work. This is common in research or exploratory tasks, where the desired state is unknown. It's not uncommon for the end of a chain to lead to the central node of a hub-and-spokes pattern; a desired state is found and work can be more easily parallelised. What's Next? Our bet is that there are many more patterns out there, waiting to be recognised. Let us know what you find.", "tags": [], "temporalCoverage": "2026-10-03T23:09:50.514863041+00:00", "title": "Thread Map", "url": "https://aggr.aymericbeaumet.com/items/ampcode-com/2025-12-11-thread-map/", "word_count": 345 }