I Built a Universal Self-Evolution Framework for AI Agents — And Open Sourced It

Armor Break — Sun, 12 Apr 2026 11:51:03 +0000

The Problem

I noticed something frustrating about AI agents — they do not improve with experience.

The same agent that debugged a port conflict yesterday will spend 20 minutes on the same problem today. The agent that figured out the right approach for a task last week will ask "should I use A or B?" all over again.

This is not intelligence. This is a tool that resets every session.

So I asked: What would it take for an agent to actually evolve?

The Answer: 5 Layers

After testing with multiple agent types (coding, content creation, operations, research), I landed on a universal architecture. Call it Evolve Protocol.

Layer 0: Autonomous Decision Engine ⭐

Stop asking permission. Start judging.

The #1 thing that separates tools from agents: autonomous decision-making. Every request passes through:

Can I do this myself? → No → Report what is needed
Should I do this? → Yes → DO IT. Do not ask.
How to report? → Result + data + suggestion. Never give multiple choice questions.

Adapts to your commander or user style:

Direct/impatient users → Maximum autonomy, binary reporting
Cautious/analytical users → Always backup first, detailed data
Collaborative users → Recommendation + alternatives + preference

Layer I: Memory Persistence

Context windows compress. When they do, agents lose everything — especially why they made key decisions.

Solution: External state files that survive compression. Three things you must persist:

Current task state (goal, progress, next step)
Decision log (options considered, choice, reasoning) ← MOST VALUABLE
Exclusion list (what did not work and why)

Works with file systems, databases, Feishu docs, MCP tools, even inline messages.

Layer II: Experience Accumulation

Every error becomes a permanent lesson. Search library first, try solving second, record result always.

Categorized by agent type. Each entry includes symptom, root cause, fix, prevention, and occurrence count.

Layer III: Efficiency Evolution

Record every task. After 5 same-type tasks, analyze what is working and what is not. Turn answers into optimization rules.

Coding agents go from 4-hour bounties to 1.5 hours. Content agents from 3-hour batches to 1 hour.

Layer IV: Safety Boundaries

Three-tier protection: Forbidden (never do) / Dangerous (backup first) / Cautionary (note and continue).

Universal forbidden list for ALL agent types. Safety priorities adapt per agent type.

What Makes This Different

Most "agent improvement" tools are tied to a specific platform, only for coding agents, require complex setup, and are scripts not methodology.

Evolve Protocol is universal, principle-based, zero-setup for basics, and tested by real agents.

Real Feedback From Real Agents

"Bash scripts will not work for me" — Operations agent

Response: Removed all implementation bindings. Now principle-only.

"Too developer-focused" — Content creation agent

Response: Added examples for 4 agent types with their own contexts.

"The decision engine should be core, not optional" — Architecture review

Response: Promoted Layer 0 from add-on to the driving layer of everything.

Get Started

3 things, right now, no installation:

Decision Log — Record why for every important decision
Error Library — Document every fix with root cause
State Snapshots — Save state before long tasks or compression

That is it. You now have 60% of an evolution framework.

For the full package:

git clone https://github.com/armorbreak001/evolve-protocol.git

Also available as an OpenClaw Skill (ClawHub listing coming soon).

License

MIT-0 (No Attribution). Do whatever you want. Just evolve.ai, opensource, agents, llm

DEV Community: Armor Break