Implement live bot screen monitoring via screenshots and WebSocket updates #22

New Issue
Closed
opened 2026-06-14 09:34:46 +02:00 by retoor · 0 comments
retoor commented 2026-06-14 09:34:46 +02:00
Owner
Copy Link

Summary

Implement a feature where bots using Playwright take screenshots after every page load, field input, scroll, action, or screen change. These screenshots should be converted to lower quality and displayed in the admin area with automatic refresh, showing the bot's username and current action/status. The solution should be lightweight, supporting 5–30 bots, and ideally use WebSocket signals or leverage existing stdout reading for updates.

Steps to Reproduce

Not provided.

Expected Behaviour

  • Bots capture screenshots after each page load, field input, scroll, action, or screen change.
  • Screenshots are converted to lower quality and displayed in the admin area.
  • The admin area automatically refreshes to show the latest screenshots.
  • Each screenshot is accompanied by the bot's username and current action/status.
  • The solution is lightweight and scalable for 5–30 bots.
  • Updates are delivered via WebSocket signals or other lightweight mechanisms (e.g., reading from stdout).

Actual Behaviour

Not implemented yet.

Environment

Not provided.

Reported by retoor via DevPlace.

## Summary Implement a feature where bots using Playwright take screenshots after every page load, field input, scroll, action, or screen change. These screenshots should be converted to lower quality and displayed in the admin area with automatic refresh, showing the bot's username and current action/status. The solution should be lightweight, supporting 5–30 bots, and ideally use WebSocket signals or leverage existing stdout reading for updates. ## Steps to Reproduce Not provided. ## Expected Behaviour - Bots capture screenshots after each page load, field input, scroll, action, or screen change. - Screenshots are converted to lower quality and displayed in the admin area. - The admin area automatically refreshes to show the latest screenshots. - Each screenshot is accompanied by the bot's username and current action/status. - The solution is lightweight and scalable for 5–30 bots. - Updates are delivered via WebSocket signals or other lightweight mechanisms (e.g., reading from stdout). ## Actual Behaviour Not implemented yet. ## Environment Not provided. --- *Reported by **retoor** via DevPlace.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: retoor/devplacepy#22
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?