How zhangzhangooo/open-workbench works
OpenWorkbench is a self-hosted local workbench: users work through a browser UI, call the local Python server, and receive results from local business data, machine capabilities, or configured integrations. The main documented flows include AI chat, OpenClaw task execution with reviewed write-back, file search and document processing, and personal productivity modules. The sampled server routes confirm API-to-store handling; broader subsystem links follow the README’s capability descriptions where implementation excerpts were not supplied.
Main entry points: server.py HTTP API Server · integrations.py Integration Services · core.js Workbench Shell · indexer.py File Index & Search
Components 22
Browser Workbench
- Workbench Shell
static/core.js - AI Chat
static/mod-ai.js - OpenClaw UI
static/mod-claw.js - Dashboard
static/mod-home.js - Document UI
static/mod-docs.js - System Tools UI
static/mod-system.js - Productivity Modules
static
Local Service
- HTTP API Server
server.py - File Index & Search
indexer.py - Document Reading
docsio.py - Document Generation
docswrite.py - Integration Services
integrations.py - Email Client
mail.py - Machine Status
sysinfo.py - ConPTY Terminal
conpty.py
Local Data
- Business Data Store
store.py
External Systems
- Ollama API
- OpenClaw
- IMAP / SMTP
- Push Connectors
integrations.py
Other components
- Workbench User
- Local Files
Connections 23
- Workbench User → Workbench Shell: uses
- Workbench Shell → HTTP API Server: calls API
- AI Chat → HTTP API Server: sends chat
- OpenClaw UI → HTTP API Server: submits tasks
- Dashboard → HTTP API Server: loads dashboard
- Document UI → HTTP API Server: requests documents
- System Tools UI → HTTP API Server: requests tools
- Productivity Modules → HTTP API Server: calls modules
- HTTP API Server → Workbench Shell: serves UI
- HTTP API Server → Business Data Store: reads and writes
- HTTP API Server → File Index & Search: searches files
- File Index & Search → Local Files: indexes files
- HTTP API Server → Document Reading: reads documents
- HTTP API Server → Document Generation: generates documents
- HTTP API Server → Integration Services: runs integrations
- HTTP API Server → Email Client: handles email
- HTTP API Server → Machine Status: gets status
- HTTP API Server → ConPTY Terminal: runs commands
- Integration Services → Ollama API: sends prompts
- Integration Services → OpenClaw: runs tasks
- Email Client → IMAP / SMTP: uses IMAP SMTP
- HTTP API Server → Push Connectors: dispatches pushes
- Integration Services → Business Data Store: queues write-backs