Cloud recall

Skill itsjwill/claude-memory/skills/cloud-recall

Persistent memory for Claude Code. Auto-capture decisions, learnings, client info. Cloud backup to Supabase. Never lose context again. Free alternative to Mem.ai, Rewind AI, Personal AI.

Install

npx -y skills add itsjwill/claude-memory --skill cloud-recall

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Search cloud memory backup when local results are insufficient. Use when memory_search returns few/no results for a topic you know was discussed before. Cloud preserves everything - even memories that were deleted or compacted locally.

SKILL.md

2.3 KB, as published. Nobody here has run it

Cloud Recall - Search Permanent Cloud Memory

Search the Supabase cloud backup for memories that may have been consolidated, compressed, or deleted locally. The cloud NEVER deletes memories - it preserves everything forever.

When to Use

Local memory_search returns few or no results
User asks about something from a past session that seems missing
User says "I told you about X" but local memory doesn't have it
Restoring context after a fresh install or device switch

Execution Steps

Search cloud backup:
```
python3 -m cloud.cli search "$ARGUMENTS" --limit 10 --include-deleted
```
Run this from the claude-memory directory (~/coding/claude-memory/)
If results found that don't exist locally:
- Present results to user with [CLOUD] indicator
- Offer to restore: "Found X memories in cloud. Restore to local?"

Restore if requested:

python3 -m cloud.cli restore --hash <hash1>,<hash2>

For full restore (new device or data loss):
```
python3 -m cloud.cli restore --all
```

Important Notes

Cloud search uses text matching (not embeddings) by default
Deleted memories show as [DELETED LOCALLY] but full content is preserved
Summary memories show as [SUMMARY] and link to original memories
All cloud operations are read-only unless explicitly restoring

Example Flow

User: "What did we decide about the API authentication?" Local search: 0 results

Run: python3 -m cloud.cli search "API authentication decision" --include-deleted
Found: 3 results from cloud (2 were deleted during consolidation)
Display: "Found 3 memories in cloud backup about API authentication:"
- [CLOUD] Decision: Use JWT with refresh tokens (deleted locally Jan 15)
- [CLOUD] Reference: Auth middleware at /src/auth/jwt.py
- [CLOUD] Pattern: Always validate tokens server-side
Ask: "Want me to restore these to local memory?"