Overview
One folder, one agent, a brain that compounds. The AgentLayer agent, documented on the three layers it is built from.
The agent installs as a plugin into the agent CLI you already use, Claude Code or Codex. Everything that makes it yours (character, memory, knowledge, projects, tasks) lives in one folder of plain markdown on your disk. Any model can read it. You can browse it in Obsidian, commit it to git, and take it with you if you ever change hosts.
It is not a chat wrapper. It is an operating system for one agent: a 56-tool MCP server, 39 skills, four hooks, and a knowledge pipeline that turns every conversation into structured, queryable memory. The open-source plugin behind it is agent-kevin.
Three layers
The product is one progression, and the docs follow it.
| Layer | What it is | Start with |
|---|---|---|
| 01 Platform · Context | The brain: the home folder, the compile pipeline, memory, capture, seed bundles | The agent home |
| 02 Agent · Harness | The agent that loads that context: hosts, hooks, permissions, tasks, cadences, worktrees | Hosts |
| 03 Modules · Powers | What it can do and what it can reach: skills, tools, packs | Skills |
The dashboard renders all three as one static page: the operator surface.
The loop
Every session is captured on exit. Captured sessions compile into a wiki. The wiki loads before you type a word in the next session. That loop is the whole product; the skills and tools exist to feed it and to act on what it knows.
How it behaves
- You drive. Every bundled skill waits for you to invoke it. A handful of read-only helpers (dashboard, where-am-i, find-session, standup, api-collections, roadmap) may run when a request clearly calls for them, and none of them mutates state.
- Subscription-billed. The MCP server returns prompts; your own session does the thinking. Nothing bills a metered API key. See Hosts.
- Local by default. No cloud sync unless you commit the folder somewhere. Secrets sit in a deny-gated store the agent's own tools cannot read.
- One plugin, many homes. A personal agent, a work agent, an SEO agent: same install, separate brains, told apart by the folder you launch from.
What can it do?
The capabilities, grouped by what they are for. Start with the group that matches the work in front of you.
Plan and run
Projects and tasks, roadmap, goals, briefings, the session radar.
Build and ship
Worktrees, pull-request review, API collections, deploy checks.
Reach and see
Browser, logs, database, search, chat, support desk, SEO.
Brain and memory
Capture, compile, self-review, sync, seed bundles.
Start here
Install
Prerequisites and the two-minute marketplace install.
Onboarding
What the init wizard asks and what it writes.
The brain
How raw sessions become compiled memory.
The harness
Hosts, hooks, permissions, and what gets recorded.
Every capability
Skills, tools, and packs, grouped by what they do.
Dashboard
The one-file mission-control page, and a live demo.
Reading with a model? The whole site is also served as llms.txt (the index) and llms-full.txt (every page as Markdown).
The plugin is named after Kevin, the loyal minion. Your agent does not have to be. See Naming.