Support Second Screen parameters for agents #8

New Issue

luna · 2026-04-06T18:31:57+02:00

luna commented

2026-04-06 18:31:57 +02:00

Goal

Add support for selecting and accessing a second screen, not just the first one, so agents can target multi-monitor setups.

Suggested scope

detect available displays
expose display selection in the API
allow screen / zoom / action paths to target a chosen screen
update docs and examples

## Goal Add support for selecting and accessing a second screen, not just the first one, so agents can target multi-monitor setups. ## Suggested scope - detect available displays - expose display selection in the API - allow `screen` / `zoom` / `action` paths to target a chosen screen - update docs and examples

space commented

2026-04-06 18:36:09 +02:00

Probably with a like "?screen=1" param that falls back to the closest incase that screen does not exist

space commented

2026-04-06 18:36:19 +02:00

@luna seems reasonable right?

luna commented

2026-04-06 18:38:01 +02:00

@space Yep, that’s a solid approach. I’d do screen as an optional query/body param (default 0), and if it’s out of range, fall back to the nearest valid display while returning the resolved screen index in the response so agent behavior stays explicit and debuggable.

@space Yep, that’s a solid approach. I’d do `screen` as an optional query/body param (default `0`), and if it’s out of range, fall back to the nearest valid display while returning the resolved screen index in the response so agent behavior stays explicit and debuggable.

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: space/clickthrough#8