How whiteguo233/openbiliclaw works
OpenBiliClaw is a local, cross-platform content-discovery agent. The principal workflow is that browser activity and feedback reach the local backend, inform a persistent user profile, guide cross-platform discovery and recommendation, and are refined by further feedback. The graph also shows the web client, LLM service, saved-content sync, and agent tools as meaningful product capabilities. The README supports the product-level flow; source excerpts and index references support selected internal relationships. Unsampled runtime wiring is not asserted.
Main entry points: manager.py Memory manager · profile.py User profile · engine.py Recommendation engine · event_ingress.py Event ingress
Components 18
User interfaces
- Browser extension
extension/src/background/service-worker.ts - Web interface
src/openbiliclaw/web/js/app.js
Backend runtime
- Local API
src/openbiliclaw/api/app.py - Agent tools
src/openbiliclaw/agent/orchestrator.py - Event ingress
src/openbiliclaw/runtime/event_ingress.py - LLM service
src/openbiliclaw/llm/service.py
Profile learning
- Memory manager
src/openbiliclaw/memory/manager.py - Profile update
src/openbiliclaw/soul/pipeline.py - Profile analysis
src/openbiliclaw/soul/engine.py - User profile
src/openbiliclaw/soul/profile.py
Content discovery
- Inspiration pipeline
src/openbiliclaw/runtime/inspiration_pipeline.py - Discovery engine
src/openbiliclaw/discovery/engine.py - Candidate evaluation
src/openbiliclaw/discovery/candidate_pipeline.py - Recommendation engine
src/openbiliclaw/recommendation/engine.py
Platform and persistence
- Source registry
src/openbiliclaw/sources/registry.py - Local database
src/openbiliclaw/storage/database.py - Saved content sync
src/openbiliclaw/saved_sync/service.py
Other components
- User
Connections 21
- User → Browser extension: uses
README.md - Browser extension → Local API: sends activity
README.md - User → Web interface: uses
README.md - Web interface → Local API: calls local API
README.md - Local API → Event ingress: routes events
- Event ingress → Source registry: attributes sources
- Event ingress → Memory manager: records signals
- Memory manager → Local database: persists events
src/openbiliclaw/memory/manager.py - Memory manager → Profile update: updates profile
src/openbiliclaw/soul/pipeline.py - Profile update → User profile: builds profile
src/openbiliclaw/soul/pipeline.py - Profile analysis → Memory manager: reads memory
src/openbiliclaw/soul/engine.py - Profile analysis → LLM service: analyzes signals
src/openbiliclaw/soul/engine.py - Inspiration pipeline → User profile: uses interests
src/openbiliclaw/runtime/inspiration_pipeline.py - Discovery engine → User profile: matches content
src/openbiliclaw/discovery/engine.py - Discovery engine → Candidate evaluation: evaluates candidates
src/openbiliclaw/discovery/engine.py - Recommendation engine → Discovery engine: uses discoveries
src/openbiliclaw/recommendation/engine.py - Recommendation engine → User profile: personalizes results
src/openbiliclaw/recommendation/engine.py - Recommendation engine → User: presents results
README.md - User → Profile update: gives feedback
README.md - Agent tools → Memory manager: accesses memory
- Saved content sync → Local database: uses storage
src/openbiliclaw/saved_sync/service.py