fix: curator JSON parsing and CLI response extraction #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes memory curation failing silently due to JSON parsing errors and incorrect CLI response extraction.
Changes
message["message"]["content"]instead ofmessage["content"]ast.literal_evalwhen LLM returns Python dict syntax despite instructions/memory/statsnow returns actual counts instead of placeholder zerosRoot Cause
The curator was returning 0 memories because:
'key': 'value'examples, so Claude followed that format and returned invalid JSON{"type":"assistant","message":{"content":[...]}}but the code looked formessage["content"]directlyTesting
Regression tests added to verify the fixes:
test_cli_response_extraction.py: Validates nested Claude Code message format handlingtest_json_parsing_fallback.py: Validates ast.literal_eval fallback for single-quote JSONtest_storage_stats.py: Validates get_stats() returns real database countsAll tests verified to fail on main branch and pass on this branch.
🤖 Generated with Claude Code