The issue context bundle
One call — get_issue_context, or the fetch that opens every parsemend fix run — returns everything Parsemend knows about one issue as a single JSON object. This page is what is in it.
> get the context for postlyra-12Narrowing it
A bundle with a trace tree and five sample events full of breadcrumbs will crowd a session's context window. Ask for the parts you want:
{ "issue": "postlyra-12", "include": ["issue", "sample_events", "code_mappings"] }include filters the top-level keys by name, so a narrowed bundle contains exactly the sections you asked for and nothing else — including no meta. Omit it for the whole thing.
Sections
These eight names are what include accepts.
| Section | Contents |
|---|---|
issue | Title, culprit, type, level, status, times_seen, user_count, first and last seen, and the fixability score and hypothesis. |
project | Id, slug, and the platform the events arrived as. |
code_mappings | Repository full name, default branch, and the stack_root → source_root pair that turns a stack-frame path into a repo-relative one. |
sample_events | Real events for this issue: exception values with their frames, the breadcrumbs leading in, tags, user, trace id, and when each arrived. |
connected_errors | Other issues whose events share a trace with this one — the failure's neighbours. |
trace_tree | The trace this issue's event belongs to: transactions, and the spans under each with op, description, status and duration. |
related_logs | Log records carrying the same trace id, with level, body and attributes. |
existing_output | Any prior fix run for this issue, local or from the agent: root cause, plan, change set, change description, and confidence. |
Always present, not selectable
Four more keys ride along with a full bundle and are dropped by include:
| Key | Contents |
|---|---|
triggering_event_id | The event the bundle was assembled around. |
project_agent_settings | The project's executor, stopping point, and whether code generation is enabled. |
qa_run | Present when the issue was filed from a failed QA flow run: the flow, the failing step, and its triage verdict. null for an ordinary issue. |
meta | generated_at, and not_yet_available — the sections the platform could not assemble for this issue. |
What is often missing
trace_tree and related_logs are null unless the triggering event carried a trace id. An exception captured by an SDK with no tracing configured has none, so both sections are empty for a large share of real issues, and no amount of asking will produce them. meta.not_yet_available names what is missing for the issue in front of you rather than leaving you to infer it from nulls.
code_mappings is an empty array until a repository is connected to the project and mappings exist. existing_output is null until something has run against the issue.
Reading it as a human
parsemend issues --json gives you the list rows, but the bundle itself has no CLI printer — it is built to be read by a model. From a session, ask for the sections you want in prose rather than pasting raw JSON around.