WebSockets for observability
Live events keep the interface synchronized with the automation process without polling.
LeadBotCommandCenter
01 / The problem
Automation scripts often behave like black boxes: users cannot see progress, stop a run safely or understand the quality of returned records until the process finishes.
02 / My response
I built a responsive command center around a FastAPI and Playwright workflow. WebSockets stream progress to a live terminal, stop controls keep the operator in charge, and normalized records can be searched, scored and exported.
What changed
01
Streamed live execution progress
02
Added safe stop and status controls
03
Normalized and exported structured results
Engineering decisions
The choices behind the interface.
Explicit operator control
Stop controls and visible states make long-running work understandable and interruptible.
Responsible-use boundary
The project documents permitted-data limits and demonstrates workflows with fictional records.
Stack & capabilities
PythonFastAPIPlaywrightWebSocketspandasDocker
View source on GitHub ↗