feat(mem0-plugin): complete all Tier 1-8 spec items, add scheduled dream and bash error detection
- Add /mem0:dream --schedule support via Claude Code /schedule command with local launchd/cron fallback for non-cloud users - Add /mem0:digest --schedule and file output to ~/.mem0/weekly-digest.md with digest-history.log for trend tracking - Add on_post_commit.sh PostToolUse hook: interactive prompt after git commit asking user to save change as memory with category suggestion - Add on_bash_output.sh PostToolUse hook: detects stack traces and error patterns in bash command output, injects mem0 search rubric for prior occurrences (complements existing user prompt error detection) - Fix session-end report: now shows per-category breakdown "wrote 3 memories (decision 2, anti_pattern 1)" matching spec - Wire new hooks into all 3 platforms (Claude Code, Cursor, Codex) - Add post_commit and bash_error telemetry events - Add CTO demo testing guide with tier-by-tier manual test steps
This commit is contained in:
kartik-mem0
@@ -65,7 +65,55 @@ Top categories: <top 3 by count>
|
||||
<2-3 sentence summary of the most important decisions, learnings, or patterns stored this week>
|
||||
```
|
||||
|
||||
### Step 4: Empty state
|
||||
### Step 4: Write digest to file
|
||||
|
||||
After displaying, write the digest to `~/.mem0/weekly-digest.md` for persistence
|
||||
and external consumption (email, Slack, etc.):
|
||||
|
||||
```bash
|
||||
mkdir -p ~/.mem0
|
||||
```
|
||||
|
||||
Write the full digest output (same markdown shown in terminal) to `~/.mem0/weekly-digest.md`
|
||||
using the Write tool. **Overwrite** the file each time — it always contains the latest digest.
|
||||
|
||||
Also append a one-line summary to `~/.mem0/digest-history.log` for trend tracking:
|
||||
|
||||
```bash
|
||||
echo "<YYYY-MM-DD> | <project_id> | +<new_count> memories | top: <top_category>" >> ~/.mem0/digest-history.log
|
||||
```
|
||||
|
||||
Print at the end:
|
||||
```
|
||||
Digest saved to ~/.mem0/weekly-digest.md
|
||||
```
|
||||
|
||||
### Step 5: Schedule recurring digests
|
||||
|
||||
When invoked with `--schedule` (e.g., `/mem0:digest --schedule weekly`), register
|
||||
a cloud routine via Claude Code's `/schedule` command:
|
||||
|
||||
```
|
||||
/schedule <frequency> /mem0:digest
|
||||
```
|
||||
|
||||
For example:
|
||||
- `/schedule weekly on Monday 9am /mem0:digest` — digest every Monday morning
|
||||
- `/schedule daily at 8am /mem0:digest` — daily digest
|
||||
|
||||
Print:
|
||||
```
|
||||
Digest scheduled: <frequency>
|
||||
Manage at: https://claude.ai/code/routines
|
||||
```
|
||||
|
||||
If `/schedule` is unavailable, print a cron one-liner the user can install manually:
|
||||
```bash
|
||||
# macOS/Linux — weekly Monday 9am
|
||||
(crontab -l 2>/dev/null; echo "0 9 * * 1 cd PROJECT_DIR && claude -p '/mem0:digest' >> /tmp/mem0-digest.log 2>&1") | crontab -
|
||||
```
|
||||
|
||||
### Step 6: Empty state
|
||||
|
||||
If no memories in the last 7 days:
|
||||
```
|
||||
|
||||
@@ -235,6 +235,110 @@ In auto mode:
|
||||
)
|
||||
```
|
||||
|
||||
**Note**: Claude Code does not have native cron/scheduling. To run dream periodically,
|
||||
use an external scheduler (cron, launchd) calling `claude -p "/mem0:dream --auto"`,
|
||||
or run it manually at the start of each week.
|
||||
## Scheduling recurring dreams
|
||||
|
||||
When invoked with `--schedule` (e.g., `/mem0:dream --schedule weekly`), register a
|
||||
cloud routine via Claude Code's built-in `/schedule` command so the dream runs
|
||||
automatically without any local cron or launchd setup.
|
||||
|
||||
### Step S1: Parse schedule frequency
|
||||
|
||||
Accept natural-language frequency after `--schedule`:
|
||||
|
||||
| User input | Cron equivalent | Description |
|
||||
|---|---|---|
|
||||
| `weekly` or `--schedule weekly` | Every Sunday 3:00 AM local | Default weekly consolidation |
|
||||
| `daily` | Every day 3:00 AM local | For high-volume projects |
|
||||
| `biweekly` | Every other Sunday 3:00 AM local | Lower frequency option |
|
||||
| Custom (e.g., `"every Monday 9am"`) | Pass verbatim to `/schedule` | Let Claude Code resolve it |
|
||||
|
||||
### Step S2: Create the routine
|
||||
|
||||
Use Claude Code's `/schedule` command to create a cloud routine. The routine runs
|
||||
`/mem0:dream --auto` on the specified schedule against the current repository:
|
||||
|
||||
```
|
||||
/schedule <frequency> /mem0:dream --auto
|
||||
```
|
||||
|
||||
For example:
|
||||
- `/schedule weekly /mem0:dream --auto` — runs every week
|
||||
- `/schedule daily at 3am /mem0:dream --auto` — runs every day at 3 AM
|
||||
- `/schedule every Monday 9am /mem0:dream --auto` — runs every Monday at 9 AM
|
||||
|
||||
The `/schedule` command handles all the cloud infrastructure: repository cloning,
|
||||
environment setup, and cron scheduling. The routine runs as a full Claude Code
|
||||
cloud session with access to the mem0 MCP tools.
|
||||
|
||||
### Step S3: Confirm to user
|
||||
|
||||
After the routine is created, print:
|
||||
|
||||
```
|
||||
Dream scheduled: <frequency>
|
||||
Routine name: mem0-dream-<project_id>
|
||||
Next run: <next scheduled time>
|
||||
|
||||
Manage at: https://claude.ai/code/routines
|
||||
Edit: /schedule list → /schedule update
|
||||
Cancel: /schedule list → delete the routine
|
||||
```
|
||||
|
||||
### Managing scheduled dreams
|
||||
|
||||
| Action | Command |
|
||||
|---|---|
|
||||
| List all routines | `/schedule list` |
|
||||
| Run dream now | `/schedule run` (select the dream routine) |
|
||||
| Change frequency | `/schedule update` (select the dream routine) |
|
||||
| Pause | Toggle off at claude.ai/code/routines |
|
||||
| Delete | Delete at claude.ai/code/routines or `/schedule update` |
|
||||
|
||||
### Fallback for non-cloud users
|
||||
|
||||
If `/schedule` is unavailable (API key auth, no claude.ai subscription), fall back
|
||||
to local options:
|
||||
|
||||
1. **macOS launchd plist** — generate and install:
|
||||
```bash
|
||||
cat > ~/Library/LaunchAgents/com.mem0.dream.plist << 'PLIST'
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
|
||||
<plist version="1.0">
|
||||
<dict>
|
||||
<key>Label</key><string>com.mem0.dream</string>
|
||||
<key>ProgramArguments</key>
|
||||
<array>
|
||||
<string>claude</string>
|
||||
<string>-p</string>
|
||||
<string>/mem0:dream --auto</string>
|
||||
<string>--allowedTools</string>
|
||||
<string>mcp__mem0__*</string>
|
||||
</array>
|
||||
<key>StartCalendarInterval</key>
|
||||
<dict>
|
||||
<key>Weekday</key><integer>0</integer>
|
||||
<key>Hour</key><integer>3</integer>
|
||||
<key>Minute</key><integer>0</integer>
|
||||
</dict>
|
||||
<key>StandardOutPath</key><string>/tmp/mem0-dream.log</string>
|
||||
<key>StandardErrorPath</key><string>/tmp/mem0-dream.err</string>
|
||||
<key>WorkingDirectory</key><string>PROJECT_DIR</string>
|
||||
</dict>
|
||||
</plist>
|
||||
PLIST
|
||||
launchctl load ~/Library/LaunchAgents/com.mem0.dream.plist
|
||||
```
|
||||
Replace `PROJECT_DIR` with the actual project path.
|
||||
|
||||
2. **Linux cron** — add entry:
|
||||
```bash
|
||||
(crontab -l 2>/dev/null; echo "0 3 * * 0 cd PROJECT_DIR && claude -p '/mem0:dream --auto' >> /tmp/mem0-dream.log 2>&1") | crontab -
|
||||
```
|
||||
|
||||
Print which method was used and how to verify:
|
||||
```
|
||||
Dream scheduled (local: launchd/cron): weekly Sundays 3am
|
||||
Verify: launchctl list | grep mem0 # macOS
|
||||
crontab -l | grep mem0 # Linux
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user