Full Compatibility
This page tracks the compatibility boundary: what Eve-facing code can rely on, what works with caveats, and what is intentionally left to Flue-native APIs.
Supported
| Surface | Notes |
|---|---|
/eve/v1/* HTTP routes | Health, info, session start, follow-up, and stream replay |
| TypeScript client | Client, ClientSession, streaming, reconnects, result() |
| React hook | useEveAgent, reducer output, stop/reset, session persistence |
| HITL | input.requested and inputResponses |
| OAuth park events | Authorization event mapping and callback support |
| Connections | MCP tools exposed as connection__* |
| Production auth | Bearer auth and fail-closed defaults |
| Persistence | Memory, file, SQLite, Redis, KV, and Durable Object patterns |
| Framework integrations | Vite, SvelteKit, Nuxt, Nitro, Node, and Cloudflare-oriented helpers |
Works with caveats
| Item | Status | Notes |
|---|---|---|
| Live MCP 401 against real MCP server | Polish | Mock e2e works; real MCP pending |
| In-process admission on Workers | Partial | Service Binding works; in-process stabilization |
| Eve file layout agent discovery | Partial | Scaffold imports declarative layout; full auto-load not planned |
Per-turn continuationToken rotation | Not planned (v1) | Stable token per session |
Intentionally outside this adapter
- Reimplementing Eve's runtime.
- Treating Flue workflow runs as Eve sessions.
- Exposing Flue stream URLs, offsets, or submission IDs to Eve clients.
- Eve platform channels such as Slack or Discord; use Flue channel integrations
or
@flue-eve/channels.
See PLAN.md on GitHub for the authoritative implementation plan and per-surface ledger.