conductor-remote 1.117.0 → 1.118.0

package/dist-node/src/writes/applescript/chat-targeting.applescript

@@ -0,0 +1,149 @@
+
+on tabGroups()
+	-- Level-order search, returning every tab group at the shallowest depth that
+	-- has one (the chat strip and the terminal strip are siblings). Bounded: the
+	-- pane sits ~5 levels down, and we must never descend into the transcript.
+	my requireWindow()
+	tell application "System Events" to tell process "Conductor"
+		set level to {window 1}
+		set depth to 0
+		repeat while (count of level) > 0 and depth < 8
+			set found to {}
+			set nextLevel to {}
+			repeat with entry in level
+				set node to contents of entry
+				try
+					set found to found & (get UI elements of node whose role is "AXTabGroup")
+					set nextLevel to nextLevel & (get UI elements of node)
+				end try
+			end repeat
+			if (count of found) > 0 then return found
+			set level to nextLevel
+			set depth to depth + 1
+		end repeat
+	end tell
+	return {}
+end tabGroups
+
+on stripRadios(tg)
+	-- Every radio button in a tab strip, whether it is a direct child or sits one
+	-- group deep, in tree order. Both shapes are live at once: the terminal strip's
+	-- tabs are direct children, while a chat tab is wrapped in its own AXGroup with
+	-- the file-view toggle beside it as a plain child. Reading only the direct ones
+	-- (and stopping as soon as any turned up) is what made a chat strip look like a
+	-- one-tab strip called "Close file view".
+	tell application "System Events" to tell process "Conductor"
+		set acc to {}
+		repeat with k in (UI elements of tg)
+			set node to contents of k
+			if (role of node) is "AXRadioButton" then
+				set end of acc to node
+			else
+				try
+					set acc to acc & (get UI elements of node whose role is "AXRadioButton")
+				end try
+			end if
+		end repeat
+		return acc
+	end tell
+end stripRadios
+
+on chatTabs(tg)
+	-- Of those, a chat tab is the one whose accessible name is its own close action,
+	-- "Close chat <title>". The strip's other radio button is "Close file view",
+	-- which is not a chat and must not shift the indices this file addresses tabs
+	-- by — off by one is how a prompt lands in the wrong conversation. Falls back to
+	-- every radio button when none carries the prefix, so a renamed label costs the
+	-- filter rather than emptying the strip.
+	set radios to my stripRadios(tg)
+	set chats to {}
+	repeat with entry in radios
+		set node to contents of entry
+		if (my axName(node)) starts with "Close chat" then set end of chats to node
+	end repeat
+	if (count of chats) > 0 then return chats
+	return radios
+end chatTabs
+
+on tabLabel(t)
+	tell application "System Events" to tell process "Conductor"
+		return (name of t) as text
+	end tell
+end tabLabel
+
+on pickChatStrip(strips, wantCount, wantTitle)
+	-- Score each candidate strip: a label match outweighs a tab-count match, and
+	-- a tie means we cannot tell the chat strip from the terminal strip.
+	set best to missing value
+	set bestTabs to {}
+	set bestScore to 0
+	set tied to false
+	repeat with entry in strips
+		set tg to contents of entry
+		set strip to my chatTabs(tg)
+		set score to 0
+		if wantCount > 0 and (count of strip) is wantCount then set score to score + 1
+		if wantTitle is not "" then
+			repeat with t in strip
+				if (my tabLabel(t)) contains wantTitle then
+					set score to score + 2
+					exit repeat
+				end if
+			end repeat
+		end if
+		if score > bestScore then
+			set bestScore to score
+			set best to tg
+			set bestTabs to strip
+			set tied to false
+		else if score is bestScore and score > 0 then
+			set tied to true
+		end if
+	end repeat
+	if bestScore is 0 then error "couldn't identify the chat tab strip"
+	if tied then error "can't tell which tab strip holds the target chat"
+	return {best, bestTabs}
+end pickChatStrip
+
+on lastPathSegment(s)
+	set saved to AppleScript's text item delimiters
+	set AppleScript's text item delimiters to "/"
+	set parts to text items of s
+	set AppleScript's text item delimiters to saved
+	return item -1 of parts
+end lastPathSegment
+
+on paneLabels(tg, wantRole)
+	-- Kept out of the caller's scope on purpose: inside a System Events tell,
+	-- ordinary-looking names (tabs, count) resolve as app terms instead of vars.
+	tell application "System Events" to tell process "Conductor"
+		set pane to value of attribute "AXParent" of tg
+		return (name of (UI elements of pane whose role is wantRole))
+	end tell
+end paneLabels
+
+on anyContains(haystack, needle)
+	repeat with entry in haystack
+		try
+			if (entry as text) contains needle then return true
+		end try
+	end repeat
+	return false
+end anyContains
+
+on assertWorkspace(tg)
+	-- The pane holding the chat strip also labels the open workspace: an
+	-- AXStaticText with the branch (sans owner prefix) and a repo popup button.
+	set wantBranch to system attribute "RELAY_WS_BRANCH"
+	if wantBranch is "" then return
+	set tail to my lastPathSegment(wantBranch)
+	if not (my anyContains(my paneLabels(tg, "AXStaticText"), tail)) then
+		error "the palette didn't land on " & tail
+	end if
+	set wantRepo to system attribute "RELAY_WS_REPO"
+	if wantRepo is not "" then
+		if not (my anyContains(my paneLabels(tg, "AXPopUpButton"), wantRepo)) then
+			error "the palette didn't land in " & wantRepo
+		end if
+	end if
+end assertWorkspace

package/dist-node/src/writes/applescript/composer.applescript

@@ -0,0 +1,195 @@
+
+on normalizeNewlines(s)
+	-- "do shell script" hands back CR-delimited text; the composer reads back LF.
+	-- Without this the verification below never matches a multi-line prompt.
+	set saved to AppleScript's text item delimiters
+	set AppleScript's text item delimiters to return
+	set parts to text items of s
+	set AppleScript's text item delimiters to linefeed
+	set joined to parts as text
+	set AppleScript's text item delimiters to saved
+	return joined
+end normalizeNewlines
+
+on composerField()
+	-- The composer's AXTextArea: an AXGroup named "composer" in the chat pane, one
+	-- text area inside it. Resolved once and handed to both the fill and the send
+	-- confirm below, because reaching it means walking the pane from the tab strip
+	-- and that walk measured ~0.5s on a live window. Returns missing value when the
+	-- composer isn't there at all, which is the caller's cue to fall back to pasting.
+	set strips to my tabGroups()
+	if (count of strips) is 0 then return missing value
+	try
+		tell application "System Events" to tell process "Conductor"
+			set pane to value of attribute "AXParent" of (item 1 of strips)
+			set composerBox to item 1 of (UI elements of pane whose name is "composer")
+			return item 1 of (UI elements of composerBox whose role is "AXTextArea")
+		end tell
+	end try
+	return missing value
+end composerField
+
+on composerTextOf(textBox)
+	-- What the box holds now, or missing value when it cannot be read at all. A pane
+	-- that re-rendered leaves the old reference pointing at a dead element, and
+	-- "can't read it" must never be reported as "still holding the prompt": that is
+	-- the one state that presses Enter again, and it would do so at the moment the
+	-- box may already be empty.
+	try
+		tell application "System Events" to tell process "Conductor"
+			return (value of textBox) as text
+		end tell
+	end try
+	return missing value
+end composerTextOf
+
+on fillComposer(textBox, promptText)
+	-- Write the prompt straight into the composer's AXTextArea instead of
+	-- stashing the clipboard, pressing Cmd+L and pasting. AXFocused and AXValue
+	-- are both settable, so this needs no keystrokes and no clipboard hijack.
+	-- Returns false (→ caller falls back to pasting) if anything looks off, but
+	-- *clears whatever it wrote first*: leaving half a prompt behind would make
+	-- the fallback paste append to it and send a garbled prompt.
+	if promptText is "" then return false
+	if textBox is missing value then return false
+	try
+		tell application "System Events" to tell process "Conductor"
+			set value of attribute "AXFocused" of textBox to true
+			set value of textBox to promptText
+			delay 0.25
+			if ((value of textBox) as text) does not contain promptText then
+				set value of textBox to ""
+				return false
+			end if
+		end tell
+	on error
+		try
+			my clearComposer(textBox)
+		end try
+		return false
+	end try
+	return true
+end fillComposer
+
+on clearComposer(textBox)
+	if textBox is missing value then return
+	tell application "System Events" to tell process "Conductor"
+		set value of textBox to ""
+	end tell
+end clearComposer
+
+on pressSend(queueIt)
+	-- Return sends, Command-Return queues the prompt behind the running answer.
+	-- The choice is made out here because inside a System Events tell an ordinary
+	-- parameter name can resolve as one of its own terms.
+	if queueIt then
+		tell application "System Events" to key code 36 using {command down}
+	else
+		tell application "System Events" to key code 36
+	end if
+end pressSend
+
+on submitComposer(textBox, promptText, queueIt)
+	-- Press Enter, then read the composer back. Conductor consumes the draft when it
+	-- accepts a prompt, so a box still holding the text is a keystroke that did
+	-- nothing — and that read is the only receipt a run can collect about its own
+	-- send.
+	--
+	-- Why it earns its place: the caller's other receipt is the transcript row, which
+	-- costs a 6s watch (CONFIRM_WINDOW_MS in server.ts) and then a whole second run
+	-- through activate, focus, tab and fill. Measured from this Mac's own relay logs,
+	-- a send whose single fault was a first Enter Conductor ignored took ~10s from the
+	-- prompt appearing in the composer to it being sent, with the text sitting on
+	-- screen the whole way. Exactly one user row was written, so the keystroke was
+	-- lost rather than delayed.
+	--
+	-- Pressing again is safe *because* of the read, not in spite of it: the prompt is
+	-- still in the box, so nothing was consumed, so there is nothing to duplicate.
+	-- The one state that would break that is a Conductor which queues on Command-Return
+	-- and *keeps* the draft, since the box would then read as unsent after a send that
+	-- worked. Unverified against the live app, and the only path that could reach it is
+	-- Command-Return in the phone's composer (Composer.tsx, a hardware keyboard); a tap
+	-- always sends. Worth checking before anything else starts queueing.
+	-- A Conductor too busy to have handled the first Enter is also too busy to answer
+	-- an AX read, which blocks here rather than handing back stale text.
+	--
+	-- **Two presses, not three, and the second one is on probation.** The first
+	-- occurrence in the wild (2026-09-01 16:59:57) had the box survive all three, and
+	-- no send has ever been recorded as rescued by a later press — so the value here
+	-- is the *detection*, which lets the caller stop watching for a row that cannot
+	-- come (`sendNeverStarted` in writes.ts) rather than spending the 6s window on it.
+	-- Every press past the first that doesn't work is pure delay added to a send that
+	-- is already failing, which is why the budget shrank from 3×1.2s to 2×0.8s.
+	--
+	-- Returns the press that cleared the box, or 0 for a box that never cleared. The
+	-- count is the point: a rescued send is otherwise indistinguishable from one that
+	-- worked first time, so the failure this handler exists for would stop appearing
+	-- in the log the day it stopped costing 10s, and nobody could tell whether it was
+	-- fixed or merely hidden.
+	if promptText is "" then
+		my pressSend(queueIt)
+		return 1
+	end if
+	repeat with pressCount from 1 to 2
+		my pressSend(queueIt)
+		if textBox is missing value then return pressCount
+		repeat with tick from 1 to 4
+			delay 0.2
+			set seen to my composerTextOf(textBox)
+			if seen is missing value then return pressCount
+			if seen does not contain promptText then return pressCount
+		end repeat
+	end repeat
+	return 0
+end submitComposer
+
+on pasteComposer()
+	-- Fallback for when the composer isn't reachable: Cmd+L focuses it (after the
+	-- palette, focus sits on a button, not the text box), then paste.
+	tell application "System Events"
+		set the clipboard to (do shell script "cat" & " " & quoted form of (system attribute "RELAY_PROMPT_FILE"))
+		keystroke "l" using {command down}
+		delay 0.3
+		keystroke "v" using {command down}
+		delay 0.15
+	end tell
+end pasteComposer
+
+on selectChatTab()
+	set wantIndex to (system attribute "RELAY_TAB_INDEX") as integer
+	if wantIndex is 0 then return
+	set wantCount to (system attribute "RELAY_TAB_COUNT") as integer
+	set wantTitle to my targetField(1)
+	set strips to my tabGroups()
+	if (count of strips) is 0 then
+		-- A lone chat has no ambiguity to resolve; more than one and we must not guess.
+		if wantCount <= 1 then return
+		error "couldn't find the chat tab strip"
+	end if
+	-- Assert the workspace first: every strip lives in the same pane, so this
+	-- reports "wrong workspace" rather than a confusing "no chat strip".
+	my assertWorkspace(item 1 of strips)
+	set picked to my pickChatStrip(strips, wantCount, wantTitle)
+	set tabs to item 2 of picked
+	tell application "System Events" to tell process "Conductor"
+		set target to missing value
+		if wantIndex <= (count of tabs) then
+			set candidate to contents of (item wantIndex of tabs)
+			if wantTitle is "" or (name of candidate) contains wantTitle then set target to candidate
+		end if
+		if target is missing value and wantTitle is not "" then
+			repeat with t in tabs
+				if (name of t) contains wantTitle then
+					if target is not missing value then error "several chat tabs match " & wantTitle
+					set target to contents of t
+				end if
+			end repeat
+		end if
+		if target is missing value then error "chat tab " & wantIndex & " not found"
+		if (value of target) is not true then
+			perform action "AXPress" of target
+			delay 0.5
+		end if
+		if (value of target) is not true then error "couldn't switch to the target chat tab"
+	end tell
+end selectChatTab

package/dist-node/src/writes/applescript/hotspot.applescript

@@ -0,0 +1,155 @@
+
+(* -- Instant Hotspot ----------------------------------------------------------
+   The funnel watchdog's last resort when this Mac has no route: press the row
+   for a personal hotspot in Control Center's Wi-Fi popover. networksetup can
+   only join a network that is broadcasting, and a personal hotspot usually
+   is not - the row in the Wi-Fi menu is fed by Continuity over Bluetooth, and
+   pressing it asks the phone to wake its hotspot, exactly like a human
+   clicking the Wi-Fi menu. Everything here targets process "ControlCenter",
+   not Conductor - same Accessibility grant, different process, which is why
+   the refusal mapping below skips refusalReason's -1712 branch (its words are
+   about a wedged Conductor).
+   Addressed by AXIdentifier throughout ("com.apple.menuextra.wifi",
+   "wifi-network-<name>", "wifi-header") - the items' names are missing value
+   and any visible text is localized, the identifiers are neither (measured
+   live on macOS 26.5, 2026-08). A "whose value of attribute ..." filter fails
+   wholesale (-1728) when any element lacks the attribute - several menu bar
+   items do - so every lookup here walks with a per-item try instead.
+   The SE-terms trap at the top of CLAUDE.md's applescript section bit this
+   code through a HANDLER PARAMETER: findAxId's first argument was once named
+   `container`, a System Events dictionary word, so inside the tell it
+   resolved as the term and the walk found nothing - through an error-eating
+   try, so a provably open popover read as "no popover" for a whole debugging
+   session while every direct read worked. osacompile accepts it, the handler
+   check can't see it. Keep every identifier in these handlers boring and
+   un-dictionary-like.
+   The menu bar item is a TOGGLE: the same press opens and closes the
+   popover, so nothing here presses it without first checking which state the
+   popover is in (wifiPopoverWindow), and an already-open popover aborts the
+   run - a human may be mid-gesture in it, and their next click kills an
+   automated run anyway (contention looks exactly like the status-row menu's:
+   fails while someone uses the Mac, clean when it is unattended). *)
+
+on wifiMenuBarItem()
+	try
+		with timeout of 6 seconds
+			tell application "System Events" to tell process "ControlCenter"
+				repeat with mi in menu bar items of menu bar 1
+					try
+						if (value of attribute "AXIdentifier" of mi) is "com.apple.menuextra.wifi" then return contents of mi
+					end try
+				end repeat
+			end tell
+		end timeout
+	on error errText number errNum
+		if errNum is not -1712 then
+			set refusal to my refusalReason({-1, errNum, errText})
+			if refusal is not "" then error refusal
+		end if
+		error "reading the menu bar failed (" & errNum & "): " & errText
+	end try
+	error "the Wi-Fi control is not in the menu bar - turn on Show in Menu Bar for Wi-Fi in System Settings > Control Center"
+end wifiMenuBarItem
+
+on findAxId(parentEl, wantedId, depth)
+	-- Depth-capped even though the popover is small: the cap is what keeps a
+	-- macOS reshuffle of this tree from turning one lookup into a full crawl.
+	-- `parentEl` is deliberately not `container` - see the section comment.
+	tell application "System Events"
+		try
+			set kids to UI elements of parentEl
+		on error
+			return missing value
+		end try
+	end tell
+	repeat with el in kids
+		try
+			tell application "System Events"
+				if (value of attribute "AXIdentifier" of el) is wantedId then return contents of el
+			end tell
+		end try
+		if depth > 1 then
+			set hit to my findAxId(el, wantedId, depth - 1)
+			if hit is not missing value then return hit
+		end if
+	end repeat
+	return missing value
+end findAxId
+
+on wifiPopoverWindow()
+	-- The popover is whichever ControlCenter window carries the "wifi-header"
+	-- id. Existence is read fresh on every call: pressing a network row can
+	-- close the popover by itself, and the menu bar item is a toggle, so a
+	-- blind second press would reopen what just closed.
+	tell application "System Events" to tell process "ControlCenter"
+		try
+			set wins to windows
+		on error
+			return missing value
+		end try
+	end tell
+	repeat with w in wins
+		if my findAxId(w, "wifi-header", 3) is not missing value then return contents of w
+	end repeat
+	return missing value
+end wifiPopoverWindow
+
+on closeWifiPopover(wifiItem)
+	if my wifiPopoverWindow() is not missing value then
+		try
+			tell application "System Events" to perform action "AXPress" of wifiItem
+		end try
+	end if
+end closeWifiPopover
+
+on joinInstantHotspot()
+	-- The name arrives via a file, like RELAY_PROMPT_FILE: do shell script
+	-- output is decoded as UTF-8, so a name with non-ASCII letters survives
+	-- where a system attribute read may not. AppleScript's default nonliteral
+	-- text comparison then treats composed and decomposed accents as equal,
+	-- which matters because the AX identifier uses whatever normalization
+	-- macOS chose.
+	set hotspotName to do shell script "cat " & quoted form of (system attribute "RELAY_HOTSPOT_FILE")
+	if hotspotName is "" then error "no hotspot name provided"
+	-- The lock screen hides the session from Accessibility, so behind it this
+	-- press has nothing to land on. Named up front, in the same words the send
+	-- path uses, instead of surfacing later as a popover that never opened.
+	if my screenLocked() is "locked" then error "The Mac is locked - the Wi-Fi menu can't be pressed until it unlocks"
+	set wifiItem to my wifiMenuBarItem()
+	if my wifiPopoverWindow() is not missing value then error "the Wi-Fi popover is already open - someone may be using it, so nothing was pressed"
+	tell application "System Events" to perform action "AXPress" of wifiItem
+	-- The popover renders in its own time (measured 1-2s), and a human's click
+	-- anywhere on the Mac closes it, so poll rather than sleep once.
+	set pop to missing value
+	repeat 8 times
+		delay 0.5
+		set pop to my wifiPopoverWindow()
+		if pop is not missing value then exit repeat
+	end repeat
+	if pop is missing value then error "pressing the Wi-Fi control opened no popover - someone clicking on the Mac closes it the moment it opens (contention, not a fault); otherwise Control Center is not answering"
+	set rowEl to missing value
+	repeat 4 times
+		set rowEl to my findAxId(pop, "wifi-network-" & hotspotName, 6)
+		if rowEl is not missing value then exit repeat
+		delay 0.5
+	end repeat
+	if rowEl is missing value then
+		my closeWifiPopover(wifiItem)
+		error quote & hotspotName & quote & " is not in the Wi-Fi menu - the iPhone is out of Bluetooth range, has Bluetooth off, or Personal Hotspot is off in its Settings"
+	end if
+	-- The row is a toggle too: value 1 means already connected, and pressing
+	-- it then would DISCONNECT - the one outcome worse than doing nothing.
+	-- Only a read of exactly 1 skips the press; an unreadable value presses.
+	set rowValue to 0
+	try
+		tell application "System Events" to set rowValue to value of rowEl
+	end try
+	if rowValue is 1 then
+		my closeWifiPopover(wifiItem)
+		return "already-connected"
+	end if
+	tell application "System Events" to perform action "AXPress" of rowEl
+	delay 1
+	my closeWifiPopover(wifiItem)
+	return "pressed"
+end joinInstantHotspot