Local API (WebSocket) to control playback/camera and read state for Automated Highlights & AI Director#207

Hi CA team! Thank you for the amazing work on CaptureAge.

I would like to suggest adding a simple local two-way API (like a local WebSocket) that allows external scripts or AI tools to send control commands to CaptureAge and receive real-time feedback on the current state.

While ticket #98 asks for exporting stats, having two-way communication to control the replay and camera would make it possible to build an Automated Smart Director and Highlight Generator.

What is needed (Two-Way Communication)

1. Commands (Input to CA):

   • Playback control: play, pause, set_speed(x), seek(timestamp)
   • Camera control: move_camera(x, y), select_player(id), lock_view(bool), set_zoom(level)
   • UI control: Toggle specific overlays on/off.

2. Feedback / State (Output from CA):

   • Current in-game timestamp and playback status (playing/paused, speed, or if the game is still loading/seeking).
   • Current camera position (x, y) and selected player POV.
   • Live snapshot of basic game events/stats (resources, pop, army value, fights happening).

Main Use Cases: Smart Director & Automated Highlights (via MCP / AI)

• Automated Match Highlights: A script or AI agent can analyze a replay to find the biggest battles, raids, or turning points, and then automatically pilot CaptureAge—jumping to the right timestamps, moving the camera to the action, and recording the clips (for example pairing it with OBS) without human intervention.
• MCP Server / AI Integration: With a local socket available, the community can easily wrap it into an MCP (Model Context Protocol) server. This would allow an AI to control CaptureAge directly, verify via feedback that the camera is in the right spot at the right second, and act as an automated caster/director or interactive review assistant.

Even a basic, opt-in local WebSocket enabled via a config file would be enough for the community to build these tools!