---
type: "BlogPosting"
title: "Six Channels for Your Context (Claude Code 2.0 Builder Guide Repurpose)"
description: "Claude Code 2.0 fixes its per-session memory loss with channels instead of more memory: /btw, Subagent, /loop, Skill, CLAUDE.md and /effort — the decision aid for every session."
resource: "https://www.contextstudios.ai/blog/six-channels-for-your-context-claude-code-2-0-builder-guide-repurpose"
language: "en"
tags: ["Claude Code", "AI Agents", "Context Engineering", "Developer Tools"]
generated:
  by: "process:contextstudios-md/1"
  at: "2026-10-24T18:13:06.257Z"
status: "stable"
---

# Six Channels for Your Context (Claude Code 2.0 Builder Guide Repurpose)

Published: 2026-09-09
Tags: Claude Code, AI Agents, Context Engineering, Developer Tools

![Six Channels for Your Context (Claude Code 2.0 Builder Guide Repurpose)](https://wary-platypus-754.convex.cloud/api/storage/d0112e8f-4979-4c62-bbda-be3de0b4c757)

Does your Claude Code forget nothing and learn nothing? Wrong: it forgets everything per session. And your main thread becomes a junk drawer if you drop every side question, log excerpt, and half-finished guess into it.
Claude Code 2.0 (as of 11.08.2026, v2.1.227) solves this not with more memory, but with channels. The decision aid I take into every session now:

```
Question, no tool?           → /btw
Tools + fresh context?       → Subagent
Repeated check?              → /loop + stop
Repeatable procedure?        → Skill (SKILL.md)
Rule for every session?      → CLAUDE.md
```

One example, twice:

❌ /loop optimize this further
✅ /loop 5m check the preview deploy, report only on status change

Same function, different result. Vague loops burn tokens without a finish line; loops with a stop condition replace your manual polling.

Two details that weren't clear to me at first: /btw sees the whole history but has no tools — ideal for "what did we actually decide?". Subagents start with an empty context window but full tool access. And Auto-Memory: per the docs, the first 200 lines (25 KB) load into every new session. Curating pays off, hoarding doesn't.

And /effort is like gears in a car: rename = low, architecture or migration = xhigh. max on every task isn't a proof of quality, just an expensive default.

The complete guide with the effort table, the /dataviz example, and the Definition of Done is published on the blog.

Which of these channels is missing in your setup right now?

## Related

- [AI Agent Development](https://www.contextstudios.ai/ai-agent-development.md)
- [AI Development](https://www.contextstudios.ai/ai-development.md)
- [Multi-Agent Systems](https://www.contextstudios.ai/multi-agent-systems.md)
- [AI Agency](https://www.contextstudios.ai/ai-development-company.md)