What it is
AgentLayer turns Claude Code or Codex into an agent that remembers your work, in a folder you own.
AgentLayer turns Claude Code or Codex into an agent that remembers your work, in a folder you own.
It installs as a plugin into the agent CLI you already use. Everything that makes the agent yours (its character, what it knows about you, your projects and tasks) lives in one folder of plain markdown on your disk. Any model can read it. You can browse it in Obsidian, keep it in git, and take it with you.
Meet Oppi
Your agent wakes up as Oppi ๐. An octopus keeps many arms busy at once with one brain behind them, and that is how it works for you: several jobs in flight, one memory of all of them. Call it whatever you like; Oppi is just who shows up first. See why an octopus.

Your agent's projects, what is due and what comes next, in the AgentLayer sidebar beside your terminals.
Who it is for
Anyone who would use an agent that remembers, not only engineers. Installing is one command, in the Quickstart. After that you talk to it. Pick the path that fits you:
I lead a team
Daily rhythm for the briefings and goals, then Standup and checkpoints, then the Dashboard, then Seed bundles to hand the agent to your team.
I write code
The engineer skill, then Pull requests, then Worktrees for parallel agents, then cmux to watch every session at once.
I run support
Helpdesk for the ticket queue, then Slack for the threads waiting on your team, then Attention to see who is waiting on you.
I want a personal assistant
Your first ten minutes, then Daily rhythm, then Capture to feed it anything, then the Dashboard to see your day.
The loop
01
Sessions
Every conversation, saved when it ends.
โ capture
02
Knowledge
Compiled into notes it reads before you type.
โ informs
03
Projects
Tasks and plans it keeps current.
โ generate
04
Results
Briefs, reviews and shipped work.
โ feeds the next session โบ
Every session is saved when you exit. Saved sessions are compiled into notes the agent keeps. Those notes load before you type a word in the next session. Everything else is built around that loop: skills and tools feed it and act on what it knows.
How it behaves
- You drive. It never starts a session on its own. Skills run when your request calls for one.
- No metered API key. Its tools return prompts and your own session does the thinking, on the plan you already have.
- Local by default. No cloud sync unless you put the folder somewhere that syncs. Keys sit in a store the agent's own tools cannot read. See Privacy.
- One plugin, many agents. A personal agent and a work agent share one install and keep separate folders.
Start here
Quickstart
One line in a terminal, a few questions, a working agent.
Your first ten minutes
Say hello, teach it something, see it remembered.
How it works
The folder, the brain, the rails, and skills and packs.
The open-source plugin is agentlayer: 36 skills, 84 tools and four hooks. The dashboard shows your own agent on one page.
Reading with a model? The site is also served as llms.txt (the index) and llms-full.txt (every page as Markdown).