AIFlare
VisionDocs
Sign inStart free
Getting Started
  • Introduction
  • Quickstart
  • Migration
Features
  • Project Dashboard
  • Project Settings
  • Timeline
  • Team Collaboration
Skills
  • Skills Overview
  • Context Capture
  • Code Intent Lookup
  • Context Recall
  • Daily Digest
  • Weekly Digest
  • Session Summary
Administration
  • Members & Invitations
  • Account Settings
Features

Context Recall

Pull past intent, rejected alternatives, and related decisions for the code you are working on — straight from local git captures. Instead of a human copying a sessionId, a one-line signal reaches the agent the moment a file is edited, and the agent recalls exactly as much depth as it needs. Fully local, no server required.

Overview

Context Recall is the read surface through which an agent recalls, mid-work, the captures that context-capture stores in local git (refs/heads/aiflare/v1) on every commit. Right after a file edit, a hook announces that file's capture history as a one-line signal, and the agent pulls depth in stages with the aiflare recall CLI — capture timeline, then a single capture in full, then the conversation excerpt. It fully replaces context-inject, where a human copied a sessionId from the web dashboard to inject a report.

Use Cases

Particularly effective in the following situations.

01
Block Re-implementing Rejected Designs

When work heads toward a direction a past session reviewed and discarded, the agent warns the user, quoting the rejection reason.

02
Mobilize Context Before Starting

When starting work on a feature area with capture history, recall the relevant intent and decisions first and start from the record, not guesswork.

03
Automatic Signal While Editing

The moment a file is edited, its past capture count and the latest title arrive as one line — code with history never slips by unnoticed.

04
Keyword Discovery

Search titles, intent, and alternatives with --grep to find past decisions even when you don't know the file path.

Usage Guide

Automatic Signal

When a file is edited in Claude Code, a PostToolUse hook queries local git captures and adds a one-line signal in the format below to the agent's context. It stays silent for files with no captures and never blocks the editing flow, regardless of failure.

[aiflare] 3 past captures for this file (latest: 'Cap payment retries', 2026-05-14)

Recall CLI — Three Modes

On receiving a signal, the agent (or a human) pulls exactly as much depth as needed with aiflare recall. Every query reads local git only — no server or network required.

aiflare recall --file <path|dir>

Lists the capture timeline for a file or directory. Intent and rejected alternatives are included right at the list stage.

aiflare recall --grep <keyword>

Searches titles, intent, alternatives, and diff summaries by keyword. The discovery tool when you don't know the file path.

aiflare recall --id <captureId>

Fetches one capture in full, including the diff summary. Add --with-conversation to see the original conversation excerpt.

Interpretation Contract

Surface Conflicts

If the intended direction matches a rejected alternative, the agent quotes the rejection reason — but never changes course on its own. The decision belongs to the user.

Provenance First

intentSource NONE means a facts-only diff description with no conversation evidence. Limitations are always disclosed before the payload.

No Fabrication

The agent never invents intent that isn't in the captures. If the captures can't explain something, it says so.

Related Skills

Context Recall consumes the captures accumulated by context-capture, and shares its git-native read core with /why on the debugging axis.

/context-capture

Captures work intent, considered alternatives, and key changes to local git right after each commit — the source of everything Recall retrieves.

/why

Answers why a specific file:line was written that way, as a debugging-oriented timeline. Line-level questions go to why; work-context questions go to recall.

On this page

AIFlare
Made with ♥ in Seoul
© 2026 AIFlare. All rights reserved.
Product
SkillDocs
Company
Vision
Resources
PrivacyTerms
Connect
GitHub