convez.ai
MCP ServerAutomaçãoAvançado
seraph-quest

Seraph: Agente IA Guardião com Memória e Automação

seraph-quest/seraph

Agente IA guardião que lembra, observa e age proativamente

Ver no GitHub
BomPluginScore · de 0 a 100

Um servidor MCP que implementa um agente IA proativo com identidade persistente, memória de longo prazo e capacidade de monitoramento de desktop. Seraph combina observação contínua, execução de workflows, integração com ferramentas e scheduler proativo para agir de forma inteligente sem esperar por prompts.

Instalação

$npx convez-ai seraph-quest/seraph

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
4
Forks
1
Acompanhando
0
Saúde
87%
Último commit
há 1 dia
Versão
v2026.11.17
Issues abertas
62
Contribuidores
1

Casos de uso

  • Automação de tarefas recorrentes e workflows complexos no desktop
  • Monitoramento contínuo com intervenções inteligentes baseadas em contexto
  • Execução de rotinas com memória de estado e histórico de decisões
  • Integração de múltiplos MCP servers para expandir capacidades de ferramentas

Veredito

Seraph é um protótipo robusto e pronto para produção para quem quer um agente guardião sério, não apenas um shell conversacional. Exige desenvolvimento em Python/React e está em evolução ativa, mas as fundações de memória, scheduler proativo e integração MCP já estão sólidas.

README

A tradução para o português deste README ainda está na fila.


What Seraph Is

Seraph is a workspace-first AI agent with:

  • persistent identity and long-term memory
  • proactive scheduling, briefings, reviews, and intervention policy
  • tool use, reusable workflows, and plug-and-play MCP server integration
  • a browser cockpit for live operation and inspection
  • an optional macOS daemon for window tracking and OCR-backed screen awareness

This repository is for builders and power users who want to run, inspect, and extend a serious guardian prototype rather than a chat-only assistant shell.

Current State

Shipped today on develop:

  • browser workspace UI, backend APIs, observer daemon, memory, goals, and proactive scheduler foundations
  • 17 built-in tool capabilities plus workflow, starter-pack, skill, and MCP integration surfaces
  • runtime routing, fallback, approval, audit, and policy foundations
  • a dense operator cockpit with activity history, approvals, interventions, and workflow inspection

Still in progress:

  • broader native reach beyond the current browser + macOS path
  • stronger long-horizon guardian intelligence and intervention learning
  • deeper execution hardening and richer extension ergonomics
  • a fully complete end-state product; Seraph is usable now, but still under active development

Start with:

Quick Start

Recommended: Local Direct Dev Stack

# 1. Configure
cp env.dev.example .env.dev
# Edit .env.dev and set OPENROUTER_API_KEY=your-key-here

# 2. Launch
./manage.sh -e dev local up

# 3. Open
open http://localhost:3001        # Current shipped browser UI
open http://localhost:8004/docs   # Swagger API docs

# 4. Inspect / stop
./manage.sh -e dev local status
./manage.sh -e dev local logs backend
./manage.sh -e dev local down

# 5. (Optional) Screen awareness daemon
./daemon/run.sh                   # Window tracking
./daemon/run.sh --ocr             # + OCR via Apple Vision

./manage.sh -e dev local up is the canonical direct browser-development path. It explicitly loads the repo-root .env.dev, starts the backend on 8004, starts the frontend on 3001, and avoids the cwd-sensitive env drift that can otherwise change the active model/provider.

Docker Dev Stack

./manage.sh -e dev up -d
open http://localhost:3000
open http://localhost:8004/docs

Architecture

LayerStack
FrontendReact 19, Vite 6, TypeScript, Tailwind CSS, Zustand
BackendPython 3.12, FastAPI, uvicorn, smolagents, LiteLLM (OpenRouter)
DatabaseSQLite (aiosqlite) + LanceDB (vector memory)
Tools17 built-in tool capabilities (auto-discovered) + reusable workflows + plug-and-play MCP servers
SchedulerAPScheduler — 9 jobs across briefings, reviews, strategist, observer cleanup, and memory/goal maintenance
DaemonNative macOS — window tracking, optional OCR (Apple Vision / OpenRouter)
InfraDocker Compose (backend + frontend + snekbox sandbox + http-mcp), uv

Project Structure

frontend/src/
  components/cockpit/ Guardian workspace operator surface, state rails, intervention feed
  components/        React overlays — chat, priorities panel, settings
  hooks/             useWebSocket, keyboard and operator interaction hooks
  stores/            Zustand stores — chat, priorities
  lib/               Tool parser and workspace helpers
  config/            Frontend constants

backend/src/
  api/               REST + WebSocket endpoints (chat, sessions, goals, tools, workflows, mcp)
  agent/             smolagents factory, onboarding, strategist, session manager
  tools/             @tool implementations + MCP manager
  workflows/         Reusable multi-step workflow loader, runtime, and gating
  memory/            Guardian record, LanceDB vector store, embedder, consolidator
  goals/             Hierarchical goal CRUD
  plugins/           Tool auto-discovery + registry
  scheduler/         APScheduler engine, connection manager, 9 background jobs
  observer/          Context manager, data sources, user state machine, delivery engine

daemon/              Native macOS screen daemon (window tracking + OCR)
docs/                Docusaurus docs site

Retired Surfaces

The retired village/editor line has been removed from the active repo path. Seraph is being built as a workspace-first guardian system, not a game-shell assistant.


MCP Servers

Add external tool servers with zero code changes:

./mcp.sh add things3 http://host.docker.internal:9100/mcp \
  --desc "Things3 task manager"

./mcp.sh list              # View configured servers
./mcp.sh test things3      # Test connection
./mcp.sh disable things3   # Toggle without removing
./mcp.sh remove things3    # Remove entirely

Also available via the Settings UI in the browser or the REST API (/api/mcp/servers).

Config: data/mcp-servers.json | Example: data/mcp-servers.example.json


Docker Management

./manage.sh -e dev up -d       # Start
./manage.sh -e dev down         # Stop
./manage.sh -e dev logs -f      # Tail logs
./manage.sh -e dev build        # Rebuild

Local Direct Runtime

./manage.sh -e dev local up
./manage.sh -e dev local status
./manage.sh -e dev local logs frontend
./manage.sh -e dev local logs backend
./manage.sh -e dev local down

Defaults for the local runtime:

  • frontend: http://localhost:3001
  • backend: http://localhost:8004
  • workspace dir: /tmp/seraph-dev-data
  • llm logs: /tmp/seraph-dev-logs

Override ports or local paths with env vars before launch if needed:

LOCAL_FRONTEND_PORT=3100 LOCAL_BACKEND_PORT=8100 ./manage.sh -e dev local up

Development Status

Seraph no longer uses the old phase model as the live planning surface.

Canonical docs now live in:

  • docs/implementation/ — shipped state, workstreams, and current status
  • docs/research/ — product thesis and design target

Current truth:

  • browser UI, backend APIs, observer daemon, memory, goals, and proactive scheduler foundations are shipped
  • Trust Boundaries, Execution Plane, and Runtime Reliability have strong foundations on develop
  • the source-of-truth docs now target a power-user guardian workspace and the browser app now defaults to that shell
  • no workstream is complete yet
  • Seraph still has substantial work left in presence, guardian intelligence, embodied UX, and ecosystem leverage

Start with:


Get Involved

Ver o original no GitHub

Bom para

Relacionados