How biohazardious/emberline works
Emberline is a self-hosted browser workbench for running real AI coding-agent CLIs against project tickets. The main journey is board ticket → queued run on an isolated worktree → persistent agent terminal → review and approval → merge and optional forge push. It also offers project setup and previews, repository and issue workflows, usage-aware scheduling, notifications, and operational health/backup features. The README documents product-level flows; source-index references and excerpts support selected internal connections, while unsampled implementation details are not inferred.
Main entry points: server.ts Core HTTP server · runs/service.ts Run lifecycle · ptyd-bridge.ts PTY bridge · tickets/service.ts Ticket workflow
Components 22
Browser Workbench
- Workbench UI
apps/web/src/App.tsx - Web API client
apps/web/src/api.ts - Review controls
apps/web/src/components/review/useReviewCommentsController.ts
Core Runtime
- Core HTTP server
apps/core/src/server.ts - Runtime configuration
apps/core/src/config.ts - SQLite state
apps/core/src/db/schema.ts - Project settings
apps/core/src/db/project-settings.ts - Ticket workflow
apps/core/src/tickets/service.ts - Run lifecycle
apps/core/src/runs/service.ts - Usage scheduler
apps/core/src/scheduler/service.ts
Agent Execution
- Command execution
apps/core/src/command-exec.ts - PTY bridge
apps/core/src/ptyd-bridge.ts - Persistent terminals
apps/ptyd/src/server.ts - Agent adapters
packages/adapter-sdk/src/provider.ts
Projects and Git
- Factory planning
apps/core/src/factory/roadmap.ts - Repository service
apps/core/src/repository/service.ts - Git gateway
apps/core/src/git-gateway/gateway.ts
External Services
- Forge integration
apps/core/src/forge/service.ts - Docker engine
apps/core/src/docker/engine.ts - Agent providers
- Git forge
Other components
- User
Connections 27
- User → Workbench UI: uses
- Workbench UI → Web API client: requests through
- Web API client → Core HTTP server: sends HTTP
apps/web/src/api.ts - Core HTTP server → Ticket workflow: serves ticket routes
- Core HTTP server → Run lifecycle: serves run routes
- Core HTTP server → Usage scheduler: starts scheduler
apps/core/src/main.ts - Core HTTP server → SQLite state: uses state
apps/core/src/server.ts - Core HTTP server → Runtime configuration: uses settings
apps/core/src/main.ts - Ticket workflow → SQLite state: persists tickets
apps/core/src/tickets/service.ts - Ticket workflow → Run lifecycle: starts ticket runs
apps/core/src/tickets/service.ts - Usage scheduler → Run lifecycle: dispatches runs
apps/core/src/scheduler/service.ts - Usage scheduler → PTY bridge: checks terminal capacity
apps/core/src/scheduler/service.ts - Run lifecycle → PTY bridge: controls sessions
- PTY bridge → Persistent terminals: connects to daemon
apps/core/src/ptyd-bridge.ts - Command execution → PTY bridge: executes via
apps/core/src/command-exec.ts - Persistent terminals → Agent providers: runs CLI sessions
- Agent adapters → Agent providers: adapts provider CLIs
- Review controls → Web API client: loads and submits comments
apps/web/src/components/review/useReviewCommentsController.ts - User → Review controls: reviews changes
- Run lifecycle → Repository service: merges approved work
- Repository service → Git gateway: uses Git access
apps/core/src/repository/service.ts - Git gateway → Git forge: proxies Git operations
apps/core/src/git-gateway/gateway.ts - Forge integration → Git forge: syncs issues and releases
- Factory planning → Project settings: reads factory settings
- User → Factory planning: sets up projects
- Run lifecycle → Docker engine: uses container previews
- Core HTTP server → Forge integration: registers forge services
apps/core/src/server.ts