engine.md

Engine updates

Grambot updates engine settings using a three-step strategy:

1. Local server running: send a mutation request over the local HTTP socket at .scout/scout.sock.
2. Local server not running: write directly to local files (settings + auth).
3. Remote server configured: reserved for future use.

Local socket

The start command launches a Fastify server bound to a Unix socket.

Current endpoints:

• GET /v1/engine/status
• GET /v1/engine/cron/tasks
• GET /v1/engine/sessions
• GET /v1/engine/sessions/:storageId
• GET /v1/engine/memory/search?query=... (requires the memory plugin)
• GET /v1/engine/plugins
• POST /v1/engine/plugins/load
• POST /v1/engine/plugins/unload
• POST /v1/engine/auth
• GET /v1/engine/events (SSE)

Plugin mutations accept:

• POST /v1/engine/plugins/load payload { "pluginId": "...", "instanceId": "...", "settings": { ... } }
• POST /v1/engine/plugins/unload payload { "instanceId": "..." }

sequenceDiagram
  participant Client
  participant Engine
  Client->>Engine: POST /v1/engine/plugins/load
  Engine->>Engine: load plugin + update settings
  Engine-->>Client: ok
  Client->>Engine: GET /v1/engine/events
  Engine-->>Client: stream events

Loading