Overview
Context Inject takes a sessionId copied from the AIFlare web dashboard and injects that session's latest saved report (the output of /summarize) into the current LLM context. It pairs with /summarize as a closed loop — when starting a new Claude Code session, you bring in the previous decision trail explicitly while keeping token cost under control.
Use Cases
Particularly effective in the following situations.
Pick up where you left off days ago by injecting that session's report and continuing from the same context.
A reviewer takes the author's sessionId, loads that session's intent and alternatives into their own session, and reviews on the same footing.
Inject reports of recent key sessions into a newcomer's session so the prior decision trail transfers without context loss.
Reference the intent and rejected alternatives of a past session that handled the same or similar problem to avoid repeating the same pitfalls.
Usage Guide
Command Syntax
Run the following command in Claude Code. sessionId is required and can be copied from the session detail page on the web dashboard.
/context-inject <sessionId>Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| sessionId | string | Required | None | ID of the past session to inject. Must point to a past session for which a report has already been saved via /summarize, not the current session. There is no fallback — it must be specified explicitly. |
Execution Flow
Error Reference
You ran /context-inject with no argument. Copy a sessionId from the web dashboard and pass it as the argument.
No report exists for the given sessionId. Run /summarize in that session first to save one.
aiflare.yml is missing at the project root or its api_key value is empty.