Skip to content

fix: Resolve Windows Automations not mapping to workspace in UI - #3239

Open
Pallavikumarimdb wants to merge 1 commit into
different-ai:devfrom
Pallavikumarimdb:fix/windows-automations
Open

fix: Resolve Windows Automations not mapping to workspace in UI#3239
Pallavikumarimdb wants to merge 1 commit into
different-ai:devfrom
Pallavikumarimdb:fix/windows-automations

Conversation

@Pallavikumarimdb

Copy link
Copy Markdown

Summary

  • Normalizes directory paths inside resolveConnectWorkspace to match workspaces correctly on Windows.
  • Adds teardown capability in workspace-kv-store.ts to release SQLite database file handles on Windows during test teardown.

Why

  • Background scheduled automation runs and CLI executions on Windows use standard Windows directory formats (backslashes, casing).
  • The Electron UI registers workspaces with forward slashes, extended-length path prefixes (\\?\), or different casing.
  • This format discrepancy fails the server's path-matching logic, meaning background automation runs execute but are never linked to their workspace in the UI.

Issue

Scope

  • Directory path normalization in apps/server/src/connect-state.ts's normalizeDirectory.
  • Database hook/teardown adjustments in workspace-kv-store.ts.
  • Additional unit tests inside connect-state.test.ts.

Out of scope

  • Modifying how the desktop UI registers workspaces or how the Task Scheduler invokes execution commands directly.

Testing

Ran

  • bun test src/connect-state.test.ts (run in apps/server)

Result

  • pass/fail: pass

CI status

  • pass: N/A (local runner only)
  • code-related failures: None
  • external/env/auth blockers: None

Manual verification

  1. Start the server locally on Windows.
  2. Query /experimental/connect/state?directory=<path> with varied casing, backslashes, trailing slashes, and \\?\ prefixes matching a workspace root.
  3. Verify that the response returns the matching workspace metadata rather than resolution: "unknown".

Evidence

  • Unit test passing output:
    src\connect-state.test.ts: Reload watcher enabled (2) (pass) connect state Cloud health scoping > uses verified health for the exact requested directory without borrowing another workspace [250.00ms]

Risk

  • Low. Path normalization changes are scoped entirely to workspace retrieval matching logic.

Rollback

  • Revert changes to apps/server/src/connect-state.ts, workspace-kv-store.ts, and connect-state.test.ts.

@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
openwork-landing Ready Ready Preview, Comment, Open in v0 Jul 28, 2026 5:05pm

@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

@Pallavikumarimdb is attempting to deploy a commit to the Different AI Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Windows Automations do NOT work

1 participant