AgentLayer▸docs
About

Before the plugin

The agent started as a daemon with a chat bot and scheduled jobs. Subscription billing rules turned it into a plugin.

The first version was a standalone program, not a plugin. The brain was the same markdown folder you see today. What ran around it was different:

PartWhat it did
A long-running daemonTalked to the Claude Agent SDK on your behalf, so the agent could work while you were away
A chat botLet you reach the agent from a messaging app on your phone
Scheduled jobsSent a morning briefing at 7am and an evening wrap, and compiled knowledge every six hours

Why it changed

Anthropic closed off the Agent SDK from subscription billing, so headless SDK calls became pay-per-token only. The design depended on a flat monthly subscription, not on a bill for whatever the agent did overnight. Without a subscription-backed SDK the daemon could not survive.

What it became

The agent was rebuilt as a plugin, first for Claude Code, then for Codex. The brain is intact and the skills were ported. The MCP server runs locally and returns prompts that you, in your own session, synthesize on your plan. That is why everything in the plugin makes the host do the model work, never the plugin itself. See Architecture.

KeptGone
Memory compounding, the wiki pipelineProactive messaging at 7am
Projects, tasks, audits, briefings on demandThe chat bridge
Everything file-based and portableThe scheduling daemon (an external scheduler can run a headless host, on API billing)

If the Agent SDK ever reopens to subscription billing, the daemon comes back. Until then, the plugin is as much of the agent as fits inside the rules.

On this page