fix(staged): strip ANSI escape codes before regex matching in run detection

apps/staged/src-tauri/Cargo.toml

@@ -54,6 +54,7 @@ acp-client = { path = "../../../crates/acp-client" }
 blox-cli = { path = "../../../crates/blox-cli" }
 
 regex = "1"
+strip-ansi-escapes = "0.2"
 async-trait = "0.1"
 tokio-util = { version = "0.7", features = ["compat"] }
 tauri-plugin-store = "2.4.2"

apps/staged/src-tauri/src/actions/run_detector.rs

@@ -23,6 +23,13 @@ use super::registry::{ActionRegistry, RunPhase};
 
 use crate::store::Store;
 
+/// Strip ANSI escape sequences so regexes written against plain text can match
+/// terminal output that includes colour/style codes.
+fn strip_ansi_codes(s: &str) -> String {
+    let stripped = strip_ansi_escapes::strip(s);
+    String::from_utf8_lossy(&stripped).into_owned()
+}
+
 /// Spawns a background task that polls the shared output buffer every 2 seconds,
 /// applies the given regex against new lines, and transitions `RunPhase` to
 /// `Running` when the pattern matches.
@@ -102,9 +109,10 @@ pub fn spawn_regex_matcher(
                 lines
             };
 
-            // Apply regex to each new line.
+            // Apply regex to each new line (strip ANSI codes before matching).
             for line in &new_lines {
-                if let Some(caps) = re.captures(line) {
+                let clean = strip_ansi_codes(line);
+                if let Some(caps) = re.captures(&clean) {
                     let endpoint = if has_endpoint_capture {
                         caps.name("endpoint").map(|m| m.as_str().to_string())
                     } else {
@@ -217,11 +225,10 @@ pub fn spawn_autodetect_poller(
             if tail.is_empty() {
                 continue;
             }
-            let output = tail
-                .iter()
-                .map(|s| s.as_str())
-                .collect::<Vec<_>>()
-                .join("\n");
+
+            // Strip ANSI codes before sending to AI and before regex matching.
+            let clean_lines: Vec<String> = tail.iter().map(|s| strip_ansi_codes(s)).collect();
+            let output = clean_lines.join("\n");
 
             // ---- Build and send the AI prompt ----
             let prompt = format!(
@@ -237,11 +244,24 @@ Recent terminal output (last ~200 lines):
 
 Analyze this output and determine:
 1. Is the application still building/compiling, or has it reached a running/ready state?
-2. If running: identify the specific output that indicates readiness (e.g.,
-   "Listening on http://0.0.0.0:3000", "Server started on port 8080", "ready in 300ms", "Local: http://localhost:1234/").
-3. Provide a regex pattern that would match for this and future runs. Be careful to avoid volatile values like timestamps, PIDs, version numbers or build durations.
-   - If the line contains a URL/endpoint, include a named capture group `(?P<endpoint>...)` for it.
-   - The regex should be general enough to work across restarts
+2. If running: identify the specific output line from the server or build tool that
+   indicates readiness (e.g., "Listening on http://0.0.0.0:3000", "Server started
+   on port 8080", "ready in 300ms", "Local: http://localhost:1234/").
+   - IMPORTANT: Pick the server/framework readiness message, NOT application-level
+     log output. For example, Vite prints "Local: http://localhost:PORT/" when ready —
+     use that, not subsequent browser console logs or webview messages that happen
+     to contain URLs.
+   - Prefer the EARLIEST line that indicates the service is up and accepting
+     connections.
+3. Provide a regex pattern that would match this readiness line in future runs.
+   The regex is tested against each output line individually (single-line matching),
+   so it must match within a single line.
+   Be careful to avoid volatile values like timestamps, PIDs, version numbers,
+   or build durations.
+   - If the readiness line contains a URL/endpoint, include a named capture group
+     `(?P<endpoint>...)` for it.
+   - The regex should be general enough to work across restarts but specific enough
+     to avoid matching unrelated log lines that happen to contain URLs.
 
 Respond ONLY with JSON, no other text:
 {{
@@ -313,8 +333,9 @@ If still building, set regex and has_endpoint_capture to null/false."#,
                 }
             };
 
-            // Validate that the regex matches at least one line in the current output.
-            let matched_line = lines.iter().find(|line| re.is_match(line));
+            // Validate that the regex matches at least one line in the current
+            // output (using the already-stripped lines).
+            let matched_line = clean_lines.iter().find(|line| re.is_match(line));
             if matched_line.is_none() {
                 log::warn!(
                     "autodetect_poller: AI regex does not match any output line for {execution_id}"