How yoheinakajima/babyagi works
BabyAGI is an experimental framework for registering, storing, and executing reusable functions, including an exploratory self-building-agent workflow. Users register or load functions, then invoke them directly or through the API; the executor resolves dependencies and secrets, records execution logs, and runs triggers. The dashboard and API provide function, version, key, dependency, and log management. README capabilities are included where documented; some pack and route wiring is not shown in the sampled source, so uncertain links are omitted.
Main entry points: babyagi/__init__.py Package entry · api/__init__.py HTTP API · db_router.py Database router · framework.py Framework
Components 19
Function framework
- Package entry
babyagi/__init__.py - Framework
babyagi/functionz/core/framework.py - Registration
babyagi/functionz/core/registration.py - Function executor
babyagi/functionz/core/execution.py
Persistence
- Database router
babyagi/functionz/db/db_router.py - Local database
babyagi/functionz/db/local_db.py - Data models
babyagi/functionz/db/models.py
User interfaces
- HTTP API
babyagi/api/__init__.py - Dashboard routes
babyagi/dashboard/__init__.py - Function details UI
babyagi/dashboard/static/js/function_details.js - Logs and graphs UI
babyagi/dashboard/static/js/log_dashboard.js
Function packs
- Default functions
babyagi/functionz/packs/default/default_functions.py - AI functions
babyagi/functionz/packs/default/ai_functions.py - Function calling chat
babyagi/functionz/packs/default/function_calling_chat.py - Agent and code drafts
babyagi/functionz/packs/drafts
External integrations
- Plugin functions
babyagi/functionz/packs/plugins
Other components
- Developer
- Browser user
- External services
Connections 26
- Developer → Package entry: registers or loads
- Package entry → Framework: creates framework
- Package entry → HTTP API: registers blueprint
- Package entry → Dashboard routes: creates dashboard
- Framework → Registration: uses
- Framework → Function executor: uses
- Framework → Database router: uses
- Registration → Database router: stores function data
- Registration → Function executor: runs update triggers
- Function executor → Database router: reads and logs
- Database router → Local database: routes database calls
- Local database → Data models: persists records
- Browser user → HTTP API: sends API requests
- Browser user → Dashboard routes: opens dashboard
- HTTP API → Function executor: executes functions
- HTTP API → Database router: reads and updates
- Dashboard routes → Database router: reads function data
- Function details UI → HTTP API: requests function actions
- Logs and graphs UI → HTTP API: requests log data
- Package entry → Default functions: loads pack
- Package entry → AI functions: loads pack
- Package entry → Function calling chat: loads pack
- Framework → Agent and code drafts: loads function packs
- AI functions → External services: calls language model
- Agent and code drafts → Plugin functions: uses search and scraping functions
- Plugin functions → External services: calls service APIs