Open-source guardian system

The agent workspace that remembers what matters.

Seraph keeps plans, memory, tool runs, timing, and approvals in one visible loop, so long-running work does not reset every time the chat gets quiet.

Start local GitHub

Quick Start

Run the guardian locally.

Keep this section practical. The page should make Seraph feel like software you can inspect today, not a concept poster.

seraph.local

$ git clone https://github.com/seraph-quest/seraph.git
$ cd seraph
$ ./manage.sh -e dev local start

# Open the workspace
$ open http://localhost:5173

What it does

Not a prettier chat. A working memory loop.

Remembers the thread

Plans, notes, recent activity, and decisions stay attached to the same workspace.

Acts through tools

Workflows and MCP servers stay part of the visible system instead of separate surfaces.

Asks before risk

Approvals, fallback paths, and degraded states stay legible while execution moves.

Why it feels different

The important state stays on-screen.

The product promise is continuity: memory, timing, execution, and human steering remain close enough that useful work can continue after the first answer.

Long-term memory should be visible, editable, and connected to action.
Memory

Interventions should be ranked by usefulness, not just model availability.
Timing

Execution should leave receipts before anyone has to reconstruct state after the fact.
Audit

Open surface

Built for teams that need open, inspectable agent infrastructure.

React FastAPI SQLite LanceDB MCP Open Source