Context Composer

The Context Composer assembles a set of docs into a single block of text you can hand to an AI agent — with a live token count so you always know where you stand against the context window.

Open it with Compose context in the top bar or the command palette (⌘K). It opens as a centered modal or a side dock — your choice in Appearance settings.

Selecting docs

Tick the docs you want to include. As you select:

• Each row shows a per-doc token count next to the title.
• The total at the top shows combined tokens and a percentage of a 200K context window.

Token counts are cached per file content and update automatically when a doc changes.

Example: you’re about to ask Claude to redesign the database layer. You tick: - CLAUDE.md (rules) — so Claude follows your conventions - architecture.md (arch) — background on the current system - adr/0005-choose-postgres.md — the relevant decision record - plans/v2-backend.md — the current plan

The Composer shows “22,450 tokens · 11% of 200K” — well within budget.

The payload format

When you copy or hand off, Bedrock assembles the docs like this:

# Context

## docs/CLAUDE.md

<content of CLAUDE.md>

---

## docs/architecture.md

<content of architecture.md>

---

Each section is prefixed with ## <relative path> so the model always knows which file it’s reading.

Copy

Click Copy to put the assembled payload on your clipboard. A small toast confirms the copy and shows the token count. Paste into any AI chat or terminal.

Hand off

Click Hand off to send directly to Claude CLI (if configured) or fall back to the clipboard. This is the fastest path to starting a Claude session with your context already loaded. See AI integrations to enable Claude CLI.

Bundles

A bundle is a named, saved selection. Tick a useful set of docs, then:

1. Click Save bundle.
2. Enter a name (e.g. “Backend change context”).
3. Click Save.

Next time, click Load bundle → Backend change context to restore that exact selection in one click. Bundles live in .bedrock/bundles.json and travel with the project.

Useful bundles to create:

Token budget tips

• Stay under ~80% of the 200K window to leave room for the model’s reply and your own prompt.
• If you’re over budget, the per-doc token counts show exactly which files are heavy — candidates for splitting into smaller focused docs.
• Short, focused docs compose better than one giant file — arch-overview.md plus arch-details.md gives you more flexibility than a single massive file.