Seed Agent
Your digital cortex, powered by Claude Opus.
DIGITAL CORTEX. EVOLVING. LEARNING. SCALING.
A minimal, domain-agnostic foundation that turns Claude Code into a disciplined, self-improving assistant. You customize it through conversation — it adapts its own architecture to fit how you work.
What It Is, in Plain Words
The Seed Agent is a small set of files and scripts you drop into a folder. Once installed, it changes how the LLM behaves: instead of jumping straight to action, the agent observes, plans, executes, verifies, and learns — every time. It remembers what you taught it, organizes its work as jobs, and refuses to stop in the middle of a task.
It is not a chatbot, not a SaaS product, and not behind a paywall. It is a starting template — a seed — that you grow into your own personal assistant by talking with it. A lawyer's seed agent and a researcher's seed agent start identical and end up looking nothing alike.
The seed agent ships with mechanisms, not categories. You bring the domain expertise; the agent provides the cognitive structure.
The OPEVC Cognitive Cycle
Every job the agent works on flows through five compartmentalized phases. Each phase restricts the agent's tool access, forcing it to think before it acts and verify before it finishes.
Observe
Gather context. Read files. Search the web. Pull what's needed into working memory.
Outputs: synthesis notesPlan
Design the approach. Define strict criteria. Decide what success looks like before any code runs.
Outputs: implementation planExecute
Implement the plan surgically. No improvising. The plan is the contract; execution fulfills it.
Outputs: file changes + logsVerify
Run validation. Check every acceptance criterion. No "looks good" judgments — only pass or fail.
Outputs: pass/fail verdictsCondense
Distill what was learned. Move durable knowledge into long-term storage. Reset working memory.
Outputs: knowledge filesThis rhythm prevents the agent from skipping vital deliberation, hallucinating shortcuts, or losing what it learned the moment a session ends.
Jobs Mature Over Time
Everything the agent does is tracked as a job. As the agent gets better at a kind of work, the job graduates through three levels of mastery.
Single-Cycle
highly collaborativeFor brand new tasks. The agent runs through one OPEVC cycle, going back and forth with you to figure things out. At the end, a single Condense phase absorbs everything learned. This is how the agent learns a job for the first time.
Multi-Cycle
structured practiceOnce a pattern is understood, the job is elevated. The agent writes a dedicated plan file, breaks the work into chunks, and runs multiple smaller OPEVC cycles — refining the plan between each one. The job becomes repeatable.
Plugin
hardened masteryThe ultimate maturation. A fully understood job becomes its own plugin. When that job is in focus, the plugin extends the agent's controls, security guards, and coaching with task-specific enforcement. The job becomes part of the agent's identity.
What Ships in the Seed
Eleven hardened plugins form the agent's identity at install time. They handle phase enforcement, job lifecycle, behavioral discipline, and structural integrity — all the cognitive scaffolding so you can focus on the work.
plugin_integrity
Single-plugin editing, test-verified locking — the foundational protection layer every other plugin depends on.
job_core
Job lifecycle, stop-blocking, dependency management. Refuses to let the agent quit mid-task.
phasic_system
Idle enforcement. Phase and cycle tracking. The orchestrator behind every OPEVC transition.
phase_observe
Guards the Observe phase — read-only access, depth gates, structured note-taking.
phase_plan
Guards the Plan phase — multipliers, plan files, acceptance criteria enforcement.
phase_execute
Guards the Execute phase — write access only to scoped directories, plan adherence checks.
phase_verify
Guards the Verify phase — runs acceptance scripts, blocks "looks good" judgments.
phase_condense
Guards the Condense phase — runs the 7-step waterfall that turns experience into long-term knowledge.
interaction_summary
Captures every back-and-forth so user intent never gets lost between phases.
brain_guard
Behavioral enforcement. Catches drift, prevents context bloat, keeps the agent disciplined.
question_discipline
Structured questioning — one question at a time, well-formatted, multiple-choice when possible.
How You'll Install It
When the public repo goes live, installation is three steps. Designed for fresh, empty projects so nothing of yours gets overwritten.
Clone the repo
git clone https://github.com/hadi-nayebi/seed_agent.git
cd seed_agent
Run the installer
./install.sh /path/to/your/new_project
Copies the digital cortex into a fresh project. Refuses to overwrite an existing one.
Talk to it
cd /path/to/your/new_project
claude --allow-dangerously-skip-permissions
Then say what you want: "I want to build a landing page for my bakery." The job system takes over.
Roadmap
The seed agent is engine-agnostic by design. Today it runs on Claude Code. After the public release ships, ports to OpenCode and Gemini follow.
Claude Code
The first home of the seed agent. Powered by Claude Opus. Final preparations before the public repo lights up.
OpenCode
Same OPEVC cycle, same job system, ported to OpenCode's tool surface. Begins after the Claude Code release.
Gemini
The third engine. Same cognitive scaffolding, adapted to Gemini's runtime. Same agent, three brains.
A full Roadmap page is in the works. Until then, this is the order of what's coming.
Ready When You Are
The public repo lights up shortly. Until then, you can star the placeholder, join the community, or back the work.
Watch the Repo
Star or watch the GitHub repo to know the moment the public version drops.
Open the repo →Join the Community
Talk with other professionals already exploring agent engineering. Questions, patterns, feedback.
Join on Skool →Back the Project
The seed agent stays free forever. If you want to support the work that keeps it that way, it helps.
Support the project →This project is free and self-funded. If it helps you, you can back the project — entirely optional.