How zhudotexe/redel works
Project type and purpose
• ReDel is a full-stack research toolkit: a Python backend library for recursive multi-agent LLM systems plus a bundled web visualization frontend. It exposes both a programmatic API and a web server (VizServer) for interactive sessions and replay of logged experiments.
Main components
a. Frontend (viz/)
• Vue.js SPA (TypeScript)
• Components: Chat, Tree, Load/Save, Notifications
• Communicates with the backend via REST/WebSocket (HTTP API & streaming)
• Bundled in viz/index.html, built with Vite
b. Backend server (redel/server/)
• VizServer: HTTP/WebSocket endpoints, session management
• SessionManager: tracks interactive sessions, state
• Indexer & Models: stores/queries logs, session metadata
• Server entrypoint: redel/server/server.py and __main__.py
c. Core library (redel/)
• ReDel class (app.py): orchestrates root vs. delegate engines
• Delegation modules: delegate_and_wait, delegate_one, base interfaces
• Event system: central events.py and EventLogger for granular logs
• Tools plugin system: redel/tools/* (browsing, email, travelplanner, etc.)
• Configuration & state: config.py, state.py, tool_config.py
• Utilities: embeddings.py, namer.py, utils.py
• Kani integration: base_kani.py—drives LLM calls (OpenAIEngine, function calling)
d. External services
• LLM API provider (OpenAI, via kani.engines.openai)
• Optional tool backends: web browsing, email SMTP, travel planner DB, WebArena process
e. Persistence
• File-based logs of all events (JSONL) in working directory or experiments/
• (No external database by default; can be extended in models.py)
f. CLI & Sandbox
• CLI entrypoints: server.py, terminal.py
• Sandbox scripts for ad-hoc experiments (sandbox/)
Architectural patterns & design principles
• Event-driven core: all components communicate through events; EventLogger captures every signal
• Modular plugin architecture: Tools and delegation strategies implement a common interface
• Clear separation:
• Presentation (Vue.js)
• Application server (VizServer + REST/WebSocket)
• Domain logic (ReDel orchestration, delegation, tools)
• Infrastructure (logging, persistence)
Relationships & data flow
1. User interacts via SPA or CLI → HTTP/WebSocket request to VizServer
2. VizServer → SessionManager loads/creates a ReDel instance
3. ReDel.query() → emits events → Delegation modules schedule sub-queries
4. Kani engine invokes LLM Calls → returns responses
5. EventLogger writes each event to disk; SessionManager broadcasts events to frontend in real time
6. Frontend renders new messages, tree updates, notifications
7. On “replay” mode: frontend loads stored log file, replays events locally