recallnest 1.4.1 → 2.2.0

package/.dockerignore

@@ -0,0 +1,11 @@
+node_modules/
+data/*
+!data/alias-map.example.json
+logs/
+.env
+.git/
+*.md
+src/__tests__/
+eval/
+integrations/
+scripts/

package/CLAUDE.md

@@ -24,9 +24,9 @@
 
 ## 4. Git Push 规则（重要！）
 
-- **所有 push 只推 origin**（`trihippo/recallnest`）
+- **所有 push 只推 origin**（`AliceLJY/recallnest`）
 - **绝对不要 push 到 upstream**（`CortexReach/memory-lancedb-pro`）—— 那是上游公开仓库，推了等于暴露私有改造
-- **绝对不要 push 到 public**（`AliceLJY/recallnest`）—— 除非用户明确要求
+- `trihippo/recallnest` 已停止维护，不再推送
 - 默认 `git push` 即可（默认推 origin）
 - 需要给上游提 PR 时，走 fork + PR 流程，不直接 push
 
@@ -34,9 +34,13 @@
 
 - `RECALLNEST_MULTI_VECTOR=true` — 多向量 L0/L1/L2 检索
 - `RECALLNEST_KG_MODE=true` — KG 三元组提取 + 图遍历
+- `RECALLNEST_EMOTION_SCORING=true` — Emotion detection + salience-weighted Weibull decay + arousal boost + retrieval scoring
+- `RECALLNEST_CONSTRUCTIVE_RETRIEVAL=true` — Multi-source candidate expansion + source-map grounded reconstruction (resume default, search opt-in)
+- `RECALLNEST_NARRATIVE_MODE=true` — Autobiographical narrative metadata layer (life-period / general-event / specific-event)
+- `RECALLNEST_PREDICTIVE_MEMORY=true` — Heuristic-predicted prospective reminders (zero LLM, behavioral signals)
 
 ## 6. 测试基线
 
 - 改完代码必须跑 `bun test`，全量通过才能 commit
-- 当前基线：643 tests / 0 fail
+- 当前基线：1428 tests / 0 fail
 - 新增功能必须配套测试，基线只能涨不能降

package/Dockerfile

@@ -0,0 +1,20 @@
+FROM oven/bun:1-alpine AS base
+WORKDIR /app
+
+# Install dependencies
+COPY package.json ./
+RUN bun install --frozen-lockfile 2>/dev/null || bun install
+
+# Copy source
+COPY src/ src/
+COPY data/alias-map.example.json data/alias-map.example.json
+
+# Default environment
+ENV RECALLNEST_API_PORT=4318
+ENV RECALLNEST_UI_PORT=4317
+
+EXPOSE 4318 4317
+
+# MCP stdio mode (default) — Glama introspection connects here
+# Override with CMD ["bun","run","src/api-server.ts"] for HTTP mode
+CMD ["bun", "run", "src/mcp-server.ts"]

package/README.md

@@ -12,7 +12,8 @@ A local-first memory system backed by LanceDB that turns scattered conversation
 [![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
 [![Bun](https://img.shields.io/badge/Runtime-Bun-f9f1e1?logo=bun)](https://bun.sh)
 [![LanceDB](https://img.shields.io/badge/LanceDB-Vector+FTS-orange)](https://lancedb.com)
-[![MCP](https://img.shields.io/badge/MCP-29_tools-blue)](https://modelcontextprotocol.io)
+[![MCP](https://img.shields.io/badge/MCP-41_tools-blue)](https://modelcontextprotocol.io)
+[![Tests](https://img.shields.io/badge/Tests-1428_pass-brightgreen)](https://github.com/AliceLJY/recallnest)
 [![CC Plugin](https://img.shields.io/badge/Claude_Code-Plugin-blueviolet)](https://github.com/AliceLJY/recallnest)
 
 **English** | [简体中文](README_CN.md) | [Roadmap](ROADMAP.md)
@@ -23,52 +24,22 @@ A local-first memory system backed by LanceDB that turns scattered conversation
 
 ## Why RecallNest?
 
-Most coding agents forget everything when you open a new window. Worse — your history is scattered across three different terminals with no shared memory.
+Coding agents forget everything between windows. Your context — project configs, debugging decisions, entity mappings — is scattered across Claude Code, Codex, and Gemini CLI with no shared memory.
 
-### Without RecallNest — every window starts from zero:
+RecallNest solves this: **a single LanceDB-backed memory layer that all three terminals read and write**. Context stored in one window is auto-recalled in another. Sessions checkpoint on exit and resume on start. Memory decays, evolves, and self-organizes — not just raw log storage.
 
-> **You (Claude Code):** "The Docker config lives at `/opt/app/config.json`, use port 4318."
->
-> *(switch to Codex)*
->
-> **You:** "The config is at... wait, let me find it again." 😤
->
-> *(next day, new Claude Code window)*
->
-> **You:** "We already fixed this exact bug last week! The solution was..."
->
-> **Agent:** "I don't have context about previous sessions." 🤷
+### Benchmark: LongMemEval (ICLR 2025)
 
-### With RecallNest — context carries over:
+Evaluated on 500 questions across 6 memory abilities ([methodology](https://arxiv.org/abs/2407.15168)):
 
-> **You (Claude Code):** "The Docker config lives at `/opt/app/config.json`, use port 4318."
->
-> *(switch to Codex — same memory layer)*
->
-> **Agent:** *(auto-recalls project entities)* "Using config at `/opt/app/config.json`, port 4318." ✅
->
-> *(next day, new window)*
->
-> **Agent:** *(resume_context fires)* "Continuing from yesterday — the Docker port conflict was resolved by..." ✅
+| | RecallNest | Vector-only baseline | Delta |
+|---|---|---|---|
+| Overall Accuracy | **29.6%** | 24.2% | **+5.4pp** |
+| User Facts | **64.3%** | 52.9% | +11.4pp |
+| Knowledge Update | **43.6%** | 42.3% | +1.3pp |
+| Abstention Rate | **55.6%** | 67.8% | **-12.2pp** |
 
-That's the difference: **one memory shared across terminals**, with context that survives window boundaries.
-
-### What you get
-
-| | Capability |
-|---|---|
-| **CC Plugin** | Install in Claude Code with one command — no manual config |
-| **Shared Index** | One LanceDB store for Claude Code, Codex, and Gemini CLI |
-| **Dual Interface** | MCP (stdio) for CLI tools + HTTP API for custom agents |
-| **One-Click Setup** | Integration scripts install MCP access and continuity rules |
-| **Hybrid Retrieval** | Vector + BM25 + reranking + Weibull decay + tier promotion |
-| **Session Continuity** | `checkpoint_session` + `resume_context` for cross-window recovery |
-| **Workflow Observation** | Dedicated append-only workflow health records, outside regular memory |
-| **Structured Assets** | Pins, briefs, and distilled summaries — not just raw logs |
-| **Smart Promotion** | Evidence → durable memory with conflict guards and merge resolution |
-| **6 Categories** | profile, preferences, entities, events, cases, patterns |
-| **4 Retrieval Profiles** | default, writing, debug, fact-check — tuned for different tasks |
-| **Multi-Source Ingest** | Import existing transcripts from all three terminals |
+Wins or ties in **all 6 categories**, with no regression. The hybrid retrieval pipeline (BM25 + vector + recency + RIF dedup) surfaces 12.2% more relevant context than vector-only search.
 
 ---
 
@@ -140,6 +111,117 @@ bun run src/cli.ts doctor
 
 ---
 
+## Web UI
+
+<p align="center">
+  <img src="assets/dashboard.png" alt="RecallNest Dashboard" width="800" />
+  <br><em>Dashboard — total count, category distribution, health score, and growth trends at a glance.</em>
+</p>
+
+<p align="center">
+  <img src="assets/screenshots/ui-full.png" alt="RecallNest Search Workbench" width="800" />
+  <br><em>Search Workbench — hybrid search with topic tag filtering, 4 retrieval profiles, Skills browser, and asset management.</em>
+</p>
+
+<p align="center">
+  <img src="assets/knowledge-graph.png" alt="RecallNest Knowledge Graph" width="800" />
+  <br><em>Knowledge Graph — interactive force-directed visualization with semantic bridges revealing cross-domain connections.</em>
+</p>
+
+```bash
+bun run src/ui-server.ts
+# → http://localhost:4317
+```
+
+---
+
+## Core Capabilities
+
+### Access & Setup
+
+| Capability | Description |
+|---|---|
+| **CC Plugin** | Install in Claude Code with one command — no manual config |
+| **Shared Index** | One LanceDB store for Claude Code, Codex, and Gemini CLI |
+| **Dual Interface** | MCP (stdio) for CLI tools + HTTP API for custom agents |
+| **One-Click Setup** | Integration scripts install MCP access and continuity rules |
+
+### Recall & Continuity
+
+| Capability | Description |
+|---|---|
+| **Hybrid Retrieval** | 6-channel: vector + BM25 + L0/L1/L2 multi-vector + KG graph (PPR) |
+| **4 Retrieval Profiles** | default, writing, debug, fact-check — tuned for different tasks |
+| **Session Continuity** | `checkpoint_session` + `resume_context` (full/light/summary modes) with repo-state guard |
+| **Session Distiller** | 3-layer conversation compression: microcompact → LLM summary → knowledge extraction |
+| **Conversation Import** | Import from Claude Code, Claude.ai, ChatGPT, Slack, and plaintext |
+| **Topic Tags** | Intra-scope topic partitioning — auto-detected, filterable in search |
+
+### Memory Lifecycle & Governance
+
+| Capability | Description |
+|---|---|
+| **Memory Evolution** | Supersede chains, decay scoring, LLM importance, consolidation, archival |
+| **Smart Promotion** | Evidence → durable memory with conflict guards, merge resolution, and audit trail |
+| **Privacy Tiers** | 4-tier (`ephemeral` / `private` / `durable` / `shared`) with cascade forgetting |
+| **Admission Control** | Write-time gating: noise filter, importance floor, dedup, rate limiting |
+| **Memory Lint** | Contradiction, duplicate, stale, and orphan detection with health score |
+| **Offline Consolidation** | `dream` command: clustering, merging, pruning of accumulated memories |
+
+### Reasoning & Structure
+
+| Capability | Description |
+|---|---|
+| **Knowledge Graph** | Entity relation graph with PPR algorithm for multi-hop questions |
+| **Constructive Retrieval** | Multi-source candidate expansion + grounded context reconstruction |
+| **Narrative Architecture** | 3-layer autobiographical metadata (life-period → general-event → specific-event) |
+| **Skill Memory** | Store, retrieve, and promote executable skills from recurring patterns |
+| **Predictive Reminders** | Behavioral-signal prediction engine surfaces "you might need this" suggestions |
+| **6 Categories** | profile, preferences, entities, events, cases, patterns — with category-aware merge strategies |
+
+### Visibility & Operations
+
+| Capability | Description |
+|---|---|
+| **Dashboard** | Web UI with stats, category distribution, growth trends, and health |
+| **Workflow Observation** | Dedicated append-only workflow health records, outside regular memory |
+| **Structured Assets** | Pins, briefs, and distilled summaries — not just raw logs |
+| **Data Checkup** | Data quality health checks on the memory store |
+| **Export Graph** | Export interactive HTML knowledge graph visualization |
+| **Batch Operations** | Store up to 20 memories in a single call with dedup |
+
+---
+
+## New in v2.1: Philosophy-Informed Memory
+
+v2.0 built the operational memory platform; v2.1 added philosophy-informed memory behavior.
+
+Five upgrades derived from 9 research dimensions in philosophy of memory, each mapped to concrete engineering:
+
+- **Emotion-Aware Decay** *(Affective Memory Theory)* — Memories with strong emotional content decay 20-30% slower. Keyword-based emotion detection computes `salience` (mnemonic significance), which feeds into the Weibull half-life formula and a rebalanced 4-factor evolution score. Zero LLM cost.
+
+- **Memory Ethics Layer** *(Right to Be Forgotten / GDPR Art. 17)* — Four privacy tiers (`ephemeral` / `private` / `durable` / `shared`). Cascade forgetting engine that propagates deletion through KG triples, evolution chains, pin assets, and briefs. Full audit trail. `forget_memory` MCP tool for agent-driven deletion.
+
+- **Autobiographical Narrative** *(Narrative Identity Theory / Conway's 3-layer model)* — Memories are tagged with `lifePeriod → generalEvent → specificEvent` hierarchy, orthogonal to existing 6 categories. Retrieval pulls narrative siblings. Context rendering groups by life period. Rule-based tagger with EN+CN support.
+
+- **Constructive Retrieval** *(Simulation Theory / Michaelian)* — Instead of returning raw stored text, RecallNest now reconstructs context from an expanded candidate set: KG neighbors + evolution chains + cluster members + narrative siblings. Source-map grounded coverage replaces lexical overlap. Contradictions are detected and flagged.
+
+- **Predictive Prospective Memory** *(Mental Time Travel / Tulving)* — Heuristic prediction engine that surfaces "you might need this" reminders from behavioral signals: stale checkpoint open loops, corrected workflow observations, high-frequency dormant memories, and uncovered query topics. Zero LLM cost. Auto-expire in 7 days if unaccepted.
+
+---
+
+## New in v2.2: Retrieval Quality Hardening
+
+v2.1 added philosophy-informed behavior; v2.2 closes the last three engine-layer gaps identified by a frontier research scan (ACC, PI-LLM, TSM).
+
+- **Memory Confidence Meta-tags** *(ACC / Dual-Process UQ)* — Each memory now carries structured `ConfidenceMetadata` (score, reliability tier: `direct` / `inferred` / `hearsay`). Auto-assigned from source on write (`manual` = 0.9, `agent` = 0.7, `conversation_import` = 0.5). Retrieval scores are weighted by confidence. `resume_context` tags low-confidence items with `[低置信]`.
+
+- **Interference Detection + Active Forgetting Gate** *(PI-LLM / SleepGate)* — Semantic cluster detection identifies groups of near-duplicate memories competing for retrieval. Enhanced RIF keeps only top-K (default 3) per cluster; extras are demoted 50% instead of removed. Write-time pre-warning: when a scope accumulates ≥5 high-similarity active memories, the weakest is flagged `pending_review`. `data_checkup` reports interference density.
+
+- **Temporal Validity Windows** *(TSM / TiMem / Zep)* — `store_memory` accepts `validUntil` (expiration) and `eventTime` (when the event actually happened). `search_memory` supports `validAt` (point-in-time query) and `includeExpired` (demote 80% instead of hide). Auto-GC applies 2× decay acceleration to expired memories.
+
+---
+
 ## Architecture
 
 ```
@@ -157,7 +239,7 @@ bun run src/cli.ts doctor
 │                   Integration Layer                       │
 │  ┌─────────────────────┐  ┌────────────────────────────┐ │
 │  │  MCP Server         │  │  HTTP API Server           │ │
-│  │  29 tools           │  │  19 endpoints              │ │
+│  │  41 tools           │  │  21 endpoints              │ │
 │  └─────────┬───────────┘  └──────────┬─────────────────┘ │
 └────────────┼─────────────────────────┼───────────────────┘
              └──────────┬──────────────┘
@@ -187,11 +269,19 @@ bun run src/cli.ts doctor
 └──────────────────────────────────────────────────────────┘
 ```
 
+### Internal Design
+
+- **L0 / L1 / L2 Dynamic Folding** — every memory stores 3 granularity layers (one-liner / bullet summary / full content); retrieval dynamically selects which layer to return based on relevance score and token budget
+- **Weibull Decay + Emotion Modulation** — memories decay along a parametric Weibull curve; importance scores modulate the half-life, and emotional salience extends it further (up to 30%)
+- **Vector Pre-filter + LLM Dedup** — 90% of dedup decisions use cheap cosine similarity (>= 0.92); only borderline cases invoke LLM judgment, keeping costs low without sacrificing accuracy
+- **Category-Aware Merge Strategies** — `profile` and `preferences` use merge-on-conflict (latest wins); `events` and `cases` use append-only (history preserved)
+- **Display Score vs Elimination Score** — dual-track retrieval: tier floor prevents core memories from ever dropping out, while decay boost lets fresh memories surface temporarily without permanently displacing stable ones
+
 > Full architecture deep-dive: [`docs/architecture.md`](docs/architecture.md)
 
 ---
 
-## Integrations
+## Interfaces
 
 RecallNest serves two interfaces:
 
@@ -210,77 +300,8 @@ Examples live in [`integrations/examples/`](integrations/examples/):
 
 ---
 
-## Core Features
-
-### Hybrid Retrieval
-
-```
-Query → Embedding ──┐
-                    ├── Hybrid Fusion → Rerank → Weibull Decay → Filter → Top-K
-Query → BM25 FTS ──┘
-```
-
-- **Vector search** — semantic similarity via LanceDB ANN
-- **BM25 full-text search** — exact keyword matching via LanceDB FTS
-- **Hybrid fusion** — vector + BM25 combined scoring
-- **Reranking** — Jina cross-encoder reranking
-- **Decay + tiering** — Weibull freshness model with Core / Working / Peripheral tiers
-
-### Session Continuity
-
-The killer feature for multi-window workflows:
-
-- **`checkpoint_session`** — snapshot current work state (decisions, open loops, next actions)
-- **Repo-state guard** — saved checkpoints strip `git status` / modified-file text so volatile repo state does not contaminate later handoffs
-- **`resume_context`** — compose startup context from checkpoints + durable memory + pins
-- **Managed rules** — integration scripts install continuity rules so `resume_context` fires automatically
-
-### Workflow Observation
-
-RecallNest now keeps workflow observations in a dedicated append-only store instead of stuffing them into the regular memory index:
-
-- **`workflow_observe`** — record whether `resume_context`, `checkpoint_session`, or another workflow primitive succeeded, failed, was corrected, or was missed
-- **`workflow_health`** — aggregate 7d / 30d health for one workflow or show a degraded-workflow dashboard
-- **`workflow_evidence`** — package recent issue observations, top signals, and suggested next actions for debugging
-
-These records live under `data/workflow-observations`, not in the 6 memory categories, and they are never composed into `resume_context` as stable recall.
-Managed MCP / HTTP continuity calls now append observations automatically for `resume_context` and `checkpoint_session`, while repo-state sanitization is recorded as a `corrected` checkpoint observation instead of polluting durable memory.
-
-### Memory Promotion & Conflict Resolution
-
-Raw transcripts don't silently become long-term memory:
-
-- **Evidence → durable** — explicit `promote_memory` with `canonicalKey` and provenance
-- **Conflict guards** — canonical-key collisions surface as conflict candidates
-- **Resolution** — keep existing, accept new, or merge — with advice and cluster views
-- **Audit + escalation** — `conflicts audit --export` for operational review
-
-### Retrieval Profiles
-
-| Profile | Best for | Bias |
-|---------|----------|------|
-| `default` | Everyday recall | Balanced |
-| `writing` | Drafting and idea mining | Broader semantic, older material OK |
-| `debug` | Errors, commands, fixes | Keyword-heavy, recency-biased |
-| `fact-check` | Evidence lookup | Tighter cutoff, exact-match bias |
-
-### Memory Categories
-
-| Category | Description | Strategy |
-|----------|-------------|----------|
-| `profile` | User identity and background | Merge |
-| `preferences` | Habits, style, dislikes | Merge |
-| `entities` | Projects, tools, people | Merge |
-| `events` | Things that happened | Append |
-| `cases` | Problem → solution pairs | Append |
-| `patterns` | Reusable workflows | Merge |
-
-Details: [`docs/memory-categories.md`](docs/memory-categories.md)
-
----
-
 <details>
-<summary><strong>MCP Tools (29 tools)</strong></summary>
+<summary><strong>MCP Tools (41 tools)</strong></summary>
 
 | Tool | Description |
 |------|-------------|
@@ -313,11 +334,23 @@ Details: [`docs/memory-categories.md`](docs/memory-categories.md)
 | `auto_capture` | Heuristically extract and store memory signals from text (zero LLM calls) |
 | `set_reminder` | Set a prospective memory reminder to surface in a future session |
 | `consolidate_memories` | Cluster near-duplicate memories and merge them (dry-run by default) |
+| `store_skill` | Store an executable skill with trigger conditions and verification |
+| `retrieve_skill` | Retrieve matching executable skills by semantic similarity |
+| `scan_skill_promotions` | Scan cases/patterns for promotion candidates to skills |
+| `list_tools` | Discover available tools by tier (core/advanced/full) |
+| `batch_store` | Store up to 20 memories in a single call with dedup |
+| `distill_session` | Distill a conversation into structured knowledge via 3-layer pipeline |
+| `import_conversations` | Import conversations from Claude Code, ChatGPT, Slack, and more |
+| `data_checkup` | Run data quality health checks on the memory store |
+| `dream` | Run offline memory consolidation (clustering, merging, pruning) |
+| `memory_lint` | Run memory quality checks: contradictions, duplicates, stale entries, orphans |
+| `forget_memory` | Cascade-delete a memory with KG cleanup, pin archival, and audit trail |
+| `export_graph` | Export memories as an interactive HTML knowledge graph |
 
 </details>
 
 <details>
-<summary><strong>HTTP API (19 endpoints)</strong></summary>
+<summary><strong>HTTP API (21 endpoints)</strong></summary>
 
 Base URL: `http://localhost:4318`
 
@@ -341,6 +374,7 @@ Base URL: `http://localhost:4318`
 | `/v1/resume` | POST | Compose startup context for a fresh window |
 | `/v1/search` | POST | Advanced search with full metadata |
 | `/v1/stats` | GET | Memory statistics |
+| `/v1/lint` | GET | Memory quality lint report |
 | `/v1/health` | GET | Health check |
 
 Full documentation: [`docs/api-reference.md`](docs/api-reference.md)
@@ -374,6 +408,12 @@ bun run src/cli.ts conflicts resolve af70545a --keep-existing
 bun run src/cli.ts conflicts resolve af70545a --merge
 bun run src/cli.ts conflicts resolve --all --keep-existing --status open
 
+# Memory health & visualization
+bun run src/cli.ts lint                         # memory quality report
+bun run src/cli.ts lint --scope project:myapp   # lint a specific scope
+bun run src/cli.ts graph --open                 # export & open knowledge graph
+bun run src/cli.ts graph --max-nodes 50         # smaller graph
+
 # Ingestion & diagnostics
 bun run src/cli.ts ingest --source all
 bun run src/cli.ts doctor
@@ -381,17 +421,36 @@ bun run src/cli.ts doctor
 
 </details>
 
-<details>
-<summary><strong>Web UI (debugging)</strong></summary>
+---
+
+## Multilingual Support
+
+RecallNest works out of the box with English. For multilingual memory (Chinese, Japanese, Thai, and 20+ more), install [babel-memory](https://github.com/AliceLJY/babel-memory) with the language packs you need:
 
 ```bash
-bun run src/ui-server.ts
-# → http://localhost:4317
+# Chinese
+npm install babel-memory jieba-wasm
+
+# Japanese
+npm install babel-memory @sglkc/kuromoji
+
+# Thai
+npm install babel-memory wordcut
+
+# European languages (German, French, Spanish, Russian, etc.)
+npm install babel-memory snowball-stemmers
+
+# Multiple languages at once
+npm install babel-memory jieba-wasm @sglkc/kuromoji snowball-stemmers
 ```
 
-The Web UI is for debugging and exploration, not the primary production interface.
+RecallNest auto-detects babel-memory at startup — no configuration needed. Without babel-memory, RecallNest still works perfectly with standard BM25 text search.
 
-</details>
+---
+
+## Project Status & Roadmap
+
+RecallNest is actively maintained. All major architecture phases are complete — see the full [Roadmap](ROADMAP.md) for current priorities and future plans.
 
 ---
 
@@ -406,21 +465,34 @@ RecallNest started as a fork of [memory-lancedb-pro](https://github.com/CortexRe
 
 | Source | Contribution |
 |--------|-------------|
-| [claude-memory-pro](https://github.com/CortexReach/claude-memory-pro) by [@win4r](https://github.com/win4r) | Retrieval core ideas and implementation base |
+| [memory-lancedb-pro](https://github.com/CortexReach/memory-lancedb-pro) by [@win4r](https://github.com/win4r) | Fork base — hybrid retrieval, decay modeling, and memory architecture |
 | Claude Code | Foundation and early project scaffolding |
 | OpenAI Codex | Productization and MCP expansion |
 
 Special thanks to Qin Chao ([@win4r](https://github.com/win4r)) and the [CortexReach](https://github.com/CortexReach) team for the foundational work.
 
-## Star History
+<details>
+<summary><strong>Ecosystem</strong></summary>
+
+Part of the **小试AI** open-source AI workflow:
+
+| Project | Description |
+|---------|-------------|
+| [babel-memory](https://github.com/AliceLJY/babel-memory) | Multilingual preprocessing for BM25 — 27+ languages, zero deps |
+| [content-alchemy](https://github.com/AliceLJY/content-alchemy) | 5-stage AI writing pipeline |
+| [content-publisher](https://github.com/AliceLJY/content-publisher) | Image generation + layout + WeChat publishing |
+| [wechat-ai-bridge](https://github.com/AliceLJY/wechat-ai-bridge) | Run Claude Code / Codex / Gemini in WeChat with session management |
+| [telegram-ai-bridge](https://github.com/AliceLJY/telegram-ai-bridge) | Telegram bots for Claude, Codex, and Gemini |
+| [telegram-cli-bridge](https://github.com/AliceLJY/telegram-cli-bridge) | Telegram CLI bridge for Gemini CLI |
+| [openclaw-tunnel](https://github.com/AliceLJY/openclaw-tunnel) | Docker ↔ host CLI bridge (/cc /codex /gemini) |
+| [openclaw-config](https://github.com/AliceLJY/openclaw-config) | OpenClaw bots configuration and memory backup |
+| [digital-clone-skill](https://github.com/AliceLJY/digital-clone-skill) | Build digital clones from corpus data |
+| [claude-code-studio](https://github.com/AliceLJY/claude-code-studio) | Multi-session collaboration platform for Claude Code |
+| [cc-genius](https://github.com/AliceLJY/cc-genius) | Web-based Claude chat client (PWA) — self-hosted, iPad-ready |
+| [agent-nexus](https://github.com/AliceLJY/agent-nexus) | One-command installer for memory + remote control |
+| [cc-cabin](https://github.com/AliceLJY/cc-cabin) | Complete Claude Code workflow scaffold |
 
-<a href="https://star-history.com/#AliceLJY/recallnest&Date">
-  <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=AliceLJY/recallnest&type=Date&theme=dark&transparent=true" />
-    <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=AliceLJY/recallnest&type=Date&transparent=true" />
-    <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=AliceLJY/recallnest&type=Date&transparent=true" />
-  </picture>
-</a>
+</details>
 
 ## License