Overview
Reuse proven ways of working and hand real work between people and agents.
Epismo gives people and AI agents two things they usually lose when work moves between tools: a shared way to approach the work, and a durable account of the work worth continuing.
- A Playbook preserves reusable guidance as immutable Versions.
- A Case represents one real piece of work, with Tasks created only when explicit coordination is useful.
- An append-only Record preserves outcomes, decisions, comments, references, and handoffs without copying the agent runtime's private reasoning or every tool call.
- A Suggestion turns a lesson from real work into a proposed improvement to a specific Playbook Version.
Epismo is not an agent runtime. Codex, Claude Code, an MCP client, or your own agent still chooses models, tools, retries, subagents, permissions, and execution graphs. Epismo stores only the shared contract and durable coordination state.
Read by surface
| Section | What it answers |
|---|---|
| Getting started | Install the CLI, choose a surface, and run your first Case |
| Concepts | What Playbooks, Cases, Tasks, Records, Suggestions, aliases, ACLs, and Versions mean |
| Guides | Task-by-task walkthroughs: authoring, publishing, coordinating, and improving a Playbook |
| Authentication | How people, the CLI, and MCP clients sign in and hold credentials |
| Administration | Workspaces, teams, billing, credits, and SSO |
| CLI | How people, agents, and CI operate the full Epismo surface from a terminal |
| MCP | How MCP clients discover Playbooks and coordinate work with the same domain operations |
| API | OAuth, HTTP conventions, and integration surfaces that are not sufficiently explained by CLI commands |
If you are new, start with Getting started, read Concepts for the model, then connect an agent through MCP when you want the agent to operate Epismo directly.
The shortest useful loop
find Playbook → read immutable Version → work in any runtime
↓ when shared state is useful
start Case → append outcome / create Task for handoff or review → close Case
↓ when the way of working should improve
create Suggestion → publish a new Version → resolve the SuggestionA Case is optional. Reading a Playbook never creates one, and starting a Case never expands every Step into a Task.