Context bundles

A context bundle gathers the available context for one issue into a bounded Markdown document on your clipboard. Assembly is automatic; completeness depends on which sources are present and linked. It is useful task context, not a guarantee that every relevant source was discovered.

From an open issue: Copy context bundle. This is separate from Copy intent in the Intent panel, which copies the displayed or editing text without approval metadata. One bundle action assembles the broader task material.

Copy and check a bundle

1. Open the issue you want someone to review. Finish your edits and check the latest approved Intent.
2. Choose Copy context bundle on the issue. This action does not call an AI model.
3. Paste into a document or review tool. Check the issue reference, the approved revision and any warnings before forwarding it.
4. Provide the exact change separately, such as the pull request and commit to inspect. Repository code and test results are not fetched by the bundle action.

Check that it worked: the pasted heading names your issue. A confirmed agreement appears under Intent, with an approval and revision. A Working intent heading or confirmation warning needs attention before someone treats the text as the agreement.

Example: what your reviewer receives

This is a shortened illustration of the current export format for the fictional CSV task in the quickstart. Names, IDs and times are fictional. The real export also includes its available context sections and source list; those are omitted from this excerpt.

# Context bundle: ENG-42 — Export filtered issues to CSV

Generated 2026-09-28T10:00:00.000Z · Team: Example team · Source: Orneos local replica
Note to agent: this bundle is bounded and may be truncated — truncations are marked in place.

## Task
**ENG-42 — Export filtered issues to CSV**
Status: in_progress · Priority: medium · Type: feature
Assignee: Alex · Author: Sam
Let someone export the issues currently shown in a filtered view.

## Intent
Approved v1 by Sam on 2026-09-28
Intent ID: example-intent-id · revision 1 · version 1

**Goal**
Let someone export the issues currently shown in a filtered view to a CSV file.

**Acceptance criteria**
- Only matching issues are exported.
- The export includes visible columns in their displayed order.
- An empty result produces headers and no issue rows.

**Non-goals**
- Scheduled exports, importing CSV, and exporting hidden columns.

The approval identifies the agreement to inspect. It does not establish that the change meets it. Give the recipient the complete actual bundle, including source and gap notices, rather than this teaching excerpt.

When the result is not ready to share

What you see	What to do
Approval pending	Let the approval sync, inspect any failed submission, and copy again. Do not label the pending writing as confirmed.
Confirmed Intent could not be established	Reconnect and allow the issue to refresh, then copy again. If the notice remains, ask for help before relying on the export as the agreement.
No approved intent exists yet	Write and approve an Intent if this review requires one. A task restatement is not an approved agreement.
Missing discussion or truncation notices	Open the relevant source, provide the missing material separately if permitted, or tell the reviewer what remains unavailable.
Clipboard failure	Use the HTTPS app, allow clipboard access if your browser asks, and retry. Verify the pasted result rather than relying on a click.
The team changed or the issue is unavailable	Return to the intended team, reopen the issue and copy again.

What is in it

Section	Contents
Task	The issue: reference, title, description, status, priority, dates, labels, project.
Intent	The latest server-confirmed approved agreement, when available — goal, acceptance criteria, non-goals, revision and approval metadata. Unsynced approval is not exported as confirmed authority.
Project and related work	Project details, parent/sub-issues and typed relations, within the bundle limits.
Discussion	Relevant comments, attributed.
Reference docs	Titles and links for explicitly referenced, team-visible Vault pages. Page bodies are not included.

Paste it wherever the reader is: a pull request, a message, an agent’s prompt, a document.

The three properties that make it useful

Every claim names its source

A bundle does not assert facts in its own voice. Each part carries its source: a criterion from Intent v3, a reference to a named Vault page, or a comment attributed to its author. A named page reference does not mean the assembler read or quoted its body.

It is bounded, and says where it was cut

A bundle has a size limit. When something does not fit, the bundle marks the truncation in place rather than silently dropping it.

This is deliberate and it is the more useful of the two possible designs. A bundle missing the comment that mattered is bad; a bundle missing it without the reader knowing is worse, because the reader concludes the context is complete.

It is assembled locally

Assembly reads the local workspace and copies Markdown without sending it to an AI provider. The adapter can trigger a network read for comments that have not loaded yet and waits for a bounded interval. Offline or incomplete reads use available material and disclose the gap; do not interpret a successful copy as a complete discussion.

Author display names also depend on identity data. If that has not resolved yet the copy still succeeds and tells you the names are raw identifiers rather than quietly writing the wrong thing.

Export boundaries

Restricted/private Vault references are excluded from source enrichment even if you can access them. Unknown space visibility is excluded too, with a visible notice. User-authored text is preserved verbatim, including any URLs it already contains; the export cannot enforce a later recipient’s access.

The bundle does not crawl arbitrary links, read your repository or retrieve full Vault page contents. See Getting the right context for the remaining source and selection gaps.

Freshness

If you were editing a field and clicked Copy, the click that starts the copy is also the click that commits your edit. The bundle waits for pending edits to settle before taking its snapshot, so “edit, then copy” exports what you just typed.

The wait is bounded. If it cannot settle in time the copy still completes and says so, rather than hanging the button.

Failure is always reported

Every way this can fail — no active team, a team switch mid-copy, the issue not present locally, the clipboard blocked by permissions or a non-secure context — produces a message saying what happened. A copy that quietly did nothing, or that reported success for the wrong issue, would be the worst outcome here, so the action is checked against the issue it started on at each step and reports what actually reached the clipboard.

What it is for

Handing work to a reviewer. The common case. Instead of “look at PR 214”, the reviewer gets the change and what it was supposed to do.

Giving an agent context. A bundle is markdown; it pastes into any agent’s prompt. Direct MCP delivery is Work in progress and is not included in this app snapshot.

Writing something down elsewhere. Anything that needs the decision record — a post-mortem, a status update, a specification.

What it is not

It is not a review. It is the material a review works from.

Automated review is work in progress. An assisted review can bridge evidence collection and interpretation while the production path is completed.

Related

• Intent — the agreement that anchors the bundle.
• MCP surface — Work in progress: direct context delivery to a supported agent.
• Evidence and unknowns — how we talk about what material proves.