How ataraxiavibin/the-bunker works
Bunker is a personal automation hub. Its main workflow runs from Telegram commands through intent registration and a routed call, to a host-side agent that executes a service and returns a normalized result. A separate CLI path reports execution events, while health checks and the two initial services provide additional product capabilities. The agent excerpt is partial, so links are limited to the documented and visible call paths.
Main entry points: agent.py Agent API and CLI · bunker.py Orchestrator API · bot.py Bot handlers · transmitter.py HTTP transmitter
Components 20
Telegram UI
- Bot handlers
bot/bot.py - TUI formatting
bot/tui.py - Health checks
shared/connection.py - HTTP transmitter
shared/transmitter.py
Bunker Hub
- Orchestrator API
bunker.py - Token verification
shared/auth.py - Message contracts
shared/models.py - Reply processing
bunker.py
Agent Runner
- Agent API and CLI
agent.py - Service dispatch map
agent.py - Subprocess execution
agent.py - Service argument parser
shared/parser.py - CLI event reporting
agent.py
Services
- Chapter checker
services/berserk_checker/checker.py - Chapter cache
services/berserk_checker/checker.py - Bluetooth controls
services/pods_connect/connect.py
Other components
- Telegram user
- Telegram
- MangaDex API
- bluetoothctl
Connections 30
- Telegram user → Telegram: sends commands
- Telegram → Bot handlers: delivers updates
- Bot handlers → TUI formatting: formats responses
- Bot handlers → Health checks: checks failures
- Health checks → Orchestrator API: pings
- Health checks → Agent API and CLI: pings
- Bot handlers → HTTP transmitter: registers intent
- Bot handlers → HTTP transmitter: sends call
- HTTP transmitter → Orchestrator API: HTTP requests
- Orchestrator API → Token verification: verifies token
- Agent API and CLI → Token verification: verifies token
- Bot handlers → Message contracts: builds messages
- Orchestrator API → Message contracts: validates messages
- Agent API and CLI → Message contracts: uses contracts
- Orchestrator API → Agent API and CLI: forwards call
- Agent API and CLI → Service dispatch map: resolves target
- Agent API and CLI → Subprocess execution: launches service
- Subprocess execution → Chapter checker: runs action
- Subprocess execution → Bluetooth controls: runs action
- Chapter checker → Service argument parser: parses arguments
- Bluetooth controls → Service argument parser: parses arguments
- Chapter checker → MangaDex API: fetches chapters
- Chapter checker → Chapter cache: reads and writes
- Bluetooth controls → bluetoothctl: runs commands
- Agent API and CLI → Reply processing: returns reply
- Reply processing → Orchestrator API: processes reply
- Orchestrator API → HTTP transmitter: returns result
- Agent API and CLI → CLI event reporting: reports CLI result
- CLI event reporting → HTTP transmitter: sends event
- HTTP transmitter → Orchestrator API: posts event