-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
Summary
Add a user-prompt-submit hook that reminds Claude to log decisions, insights, and risks to the recap system. This addresses the gap where Claude may forget to call add_entry after making decisions.
Problem
Claude has instructions to log decisions/insights/risks to recap, but doesn't always do so consistently. This is a pattern-matching gap - the instruction exists but isn't always applied in the moment.
Trying to enumerate every scenario in prompts isn't scalable.
Proposed Solution
A user-prompt-submit hook that injects a brief reminder before each response:
If you made any decisions, discovered insights, or identified risks in your previous turn, log them to recap before continuing.
This keeps recap logging in Claude's working memory without requiring explicit prompting for every scenario.
Implementation Options
- Add to existing
iloom-hook.js- Check forUserPromptSubmitevent type and output reminder - Separate hook file - Keep concerns separated (status broadcasting vs behavioral nudges)
Considerations
- Keep reminder brief to minimize context overhead
- Only inject when ILOOM=1 (same as existing hook)
- Consider whether to always inject or only when recap file exists
Related
- Track artifacts in recap #351 - Track artifacts in recap
- Consider hook-based automatic artifact capture for recap #358 - Hook-based automatic artifact capture
- Loom Recap MCP Server #346 - Recap MCP Server
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
No status