Skip to content

Windows package path redirection leaves shared local ledger inaccessible from VS Code #3

Closed

Description

@gonzoinc

Problem

Conductor's local ledger works from Codex Desktop but fails the MCP handshake from Codex in VS Code. Both clients share a configured path under %LOCALAPPDATA%\Conductor, but the existing approximately 1.5 MB ledger and ownership marker are physically under the Desktop package's LocalCache\Local\Conductor directory.

Desktop logs report conductor_coordination ready. VS Code logs show handshake closure on November 4 and 5, 2026. Launching the bridge outside the packaged app reproduces:

Private Conductor path must be a regular file or directory of the expected type

The ledger has not been deleted. These observations indicate Windows package path redirection; the exact installer process that created the redirected files has not been established.

Expected behavior

Both clients resolve the configured path to the same physical ledger. Existing task history survives repair. Startup never silently creates a second empty database.

Required changes

  1. Centralize Windows task-data defaults across gui/setup_app.py, scripts/bootstrap.py, scripts/install_support.py, and src/conductor_coordination/client_bridge.py. Choose a private local directory outside package redirection and keep it separate from program installation. Proposed default: %USERPROFILE%.conductor, subject to actual cross-client verification.
  2. Extend gui/setup_controller.py path validation to diagnose package-private/redirected selections. Installer-launched bridge health alone must not count as cross-client acceptance.
  3. Add explicit repair/migration. scripts/install_client.py currently preserves a differing client.json, preventing setup from repointing an existing installation. Preserve that overwrite protection outside the explicit repair workflow.
  4. Locate and validate the original ledger and ownership marker, including redirected legacy locations. Stop if sources are ambiguous or a conflicting destination exists.
  5. Quiesce writers and/or use a consistent SQLite backup. Preserve ownership metadata and private ACL protections; verify integrity and task-history preservation before switching. Update settings atomically with recoverable rollback. Retain the original ledger until both clients pass acceptance.
  6. Make bridge errors identify the configured path and explain a possible Windows package-redirection mismatch. Preserve refusal to create a missing database at startup.
  7. Update Windows setup/repair documentation and distribute a corrected installer.

Regression tests

Add focused tests alongside tests/test_gui_setup.py, tests/test_client_setup.py, and tests/test_client_bridge.py:

  • Shared Windows default-path resolution.
  • Redirected-path diagnosis.
  • Migration preserves task history, ownership marker, and private permissions.
  • Ambiguous sources and conflicting destinations fail safely.
  • Interrupted migration/settings updates support rollback.
  • Missing legacy ledger never causes creation of a second empty replacement.

Actual-client acceptance

  • Codex Desktop and VS Code both discover coordination_health and pass it.
  • A workload written from Desktop is readable from VS Code.
  • A write from VS Code is readable from Desktop and lands in the same ledger.
  • Both clients work after restart.

Installer and backend tests alone do not prove cross-client behavior.

Scope and current state

No Conductor source, settings, or ledger data was changed during diagnosis. Implementation and installation repair are complete. Actual Desktop/VS Code cross-client and restart acceptance passed. PR #4 is merged into main and the corrected installer is published in v0.4.1. Fix Conductor only; do not modify consuming project code or local_mcp.

Personal absolute paths, package identifiers, ledger contents, and raw application logs are omitted from this public report.

Activity

  1. self-assigned this
    on Nov 5, 2026
  2. gonzoinc commented on Nov 5, 2026

    @gonzoinc
    OwnerAuthor

    Implemented and verified in PR #4, which also prepares Conductor 0.4.1.

    Acceptance completed on the affected Windows installation:

    • Explicit offline migration succeeded; original ledger and rollback journal retained.
    • Actual Codex Desktop and VS Code both discovered and passed coordination_health.
    • Desktop wrote an acceptance workload at epoch 1; VS Code read it and wrote epoch 2; Desktop independently read the VS Code result.
    • Read-only database checks confirmed the acceptance record exists only in the migrated ledger, not the retained original.
    • Both clients passed health/read checks after restart, with client=vscode, epoch=2 and no active lease.

    Regression tests cover redirectable defaults, missing-ledger refusal, preserved records and private permissions, physical aliases, conflicting sources/destinations, and interrupted two-profile rollback. The local corrected installer passed its self-test. macOS/Linux defaults are unchanged; actual macOS client testing was not performed.

    This issue will be closed as resolved when PR #4 merges; the tagged Windows release will then publish the corrected installer and checksum.

  3. gonzoinc commented on Nov 5, 2026

    @gonzoinc
    OwnerAuthor

    Resolved by PR #4, merged into main as 7b864e5.

    Conductor v0.4.1 is now published as the latest stable release: https://github.com/gonzoinc/Conductor/releases/tag/v0.4.1

    The tagged Windows release workflow passed source/version checks, Windows setup tests, installer build, and packaged self-test, and published ConductorSetup.exe plus its SHA-256 checksum. All issue acceptance checkboxes are now complete. Existing installations still require the documented explicit repair; the original ledger and rollback journal from the verified repair remain retained.

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions