ExperienceEngine

ExperienceEngine

English | [简体中文](./README.zh-CN.md)

**A local experience-governance layer for coding agents.**

ExperienceEngine helps coding agents avoid repeating the same failed execution paths by turning prior task outcomes into short, governed prompt-boundary hints.

Memory helps agents remember context. ExperienceEngine governs whether prior execution experience should intervene.

Supported hosts today: **Codex**, **Claude Code**, **OpenClaw**, and **Google Antigravity** through different hook / MCP / plugin paths.

**ClawHub status (2026-07-21):** public `0.5.3` is available, scan-clean, and independently passed reverse-download plus full OpenClaw `2026.7.1` WSL/Linux live-host validation. Use the unversioned install command below. The exact public `0.5.2` artifact remains incomplete and must not be installed.

---

10-Second Example

Without ExperienceEngine:

• A coding agent sees a SQLite startup failure.
• It spends several turns debugging connection pool settings.
• It eventually discovers the real issue: the DB connection was opened before the migration ran.
• Days later, in a similar repo or task, it repeats the same failed path.

With ExperienceEngine:

• The prior failure/fix/success path is distilled into a reusable experience node.
• When a similar task starts, ExperienceEngine may inject one compact hint:

Run the migration before opening the DB connection.

• After the run, ExperienceEngine tracks whether that hint helped, harmed, or remained uncertain.
• If the hint keeps helping, it can become more trusted.
• If it starts harming similar tasks, it can cool down, be quarantined, or retire.

Core loop:

task signals
→ distilled experience
→ hybrid retrieval
→ compact intervention
→ helped/harmed feedback
→ governance

---

Why It Exists

Coding agents are already strong. They can handle large codebases, call tools, follow multi-step tasks, and often recover from mistakes.

But one failure mode still appear