#13775: Lucas/enable corememories
channel: telegram
extensions: lobster
extensions: memory-lancedb
docker
agents
stale
<!-- greptile_comment -->
<h2>Greptile Overview</h2>
<h3>Greptile Summary</h3>
This PR enables CoreMemories integration - a hierarchical, file-backed memory store for tracking conversation history. The changes include:
- Added `@openclaw/core-memories` package scaffold (package.json only, no implementation)
- Integrated CoreMemories recording into auto-reply flow to capture inbound messages and assistant replies
- Added configuration schema for CoreMemories compression modes
- Fixed Windows compatibility issues in shell-env resolution, lobster tool, and vitest config
- Removed GitHub App token dependency from labeler workflow (now uses GITHUB_TOKEN)
- Fixed test tolerance for weekday prefixes in Telegram timestamp formatting
- Made Pi embedded runner's `process.chdir` calls more resilient to environments that don't support it
- Improved memory-lancedb extension to lazy-load OpenAI SDK
**Critical Issue**: The `@openclaw/core-memories` package is added as a dependency but has no implementation - only a package.json file exists. This will cause runtime failures when the auto-reply code tries to import `getCoreMemories`.
**Dependency Management**: Several extension-only dependencies (`@twurple/*`, `@vector-im/matrix-bot-sdk`, `music-metadata`, `nostr-tools`) were added to root package.json, violating the project guideline (AGENTS.md:11-12) that plugin-only dependencies should remain in extension package.json files.
<h3>Confidence Score: 1/5</h3>
- This PR has a critical issue that will cause runtime failures - the core-memories package has no implementation
- The PR adds `@openclaw/core-memories` as a dependency and integrates it into the auto-reply flow, but the package only contains a package.json with no actual source code or built artifacts. When dispatch-from-config.ts attempts to import `getCoreMemories`, it will fail at runtime despite the try/catch because the module resolution itself will fail. Additionally, several extension-only dependencies were incorrectly added to root package.json, violating project guidelines. While the Windows compatibility fixes and other improvements are solid, the missing core-memories implementation is a blocking issue.
- Pay close attention to packages/core-memories/package.json (missing implementation) and package.json (incorrect dependency placement)
<!-- greptile_other_comments_section -->
**Context used:**
- Context from `dashboard` - CLAUDE.md ([source](https://app.greptile.com/review/custom-context?memory=fd949e91-5c3a-4ab5-90a1-cbe184fd6ce8))
<!-- /greptile_comment -->
Most Similar PRs
#9816: core-memories: ingest chat into Flash + capture assistant replies
by Itslouisbaby · 2026-02-05
82.9%
#19341: Mind Memory Fork
by juliopx · 2026-02-17
78.8%
#8713: feat: gateway memory monitor, install linger, docs and failover
by quratus · 2026-02-04
77.5%
#22138: Create ContextMemory documentation
by AkashKobal · 2026-02-20
77.5%
#8795: feat(memory): add Redis-backed long-term memory plugin
by tf-gmail · 2026-02-04
77.3%
#19787: feat: Antigravity Fork - Token Economy, Mem0, sqlite-vec, Auto-Arch...
by msrovani · 2026-02-18
77.0%
#9818: coremem-tools: add coremem_recent/coremem_find agent tools
by Itslouisbaby · 2026-02-05
76.8%
#2884: fix: Create memory directory and symlink identity files during work...
by webdevtodayjason · 2026-01-27
75.4%
#6060: feat(onboarding): add Memory Optimization step to onboarding wizard
by GodsBoy · 2026-02-01
75.2%
#4450: fix bug #4366: Error: Config validation failed: plugins.slots.memor...
by tryagain3 · 2026-01-30
74.8%