Repository navigation
Conductor 0.4.1
Fixes issue #3: Windows packaged Desktop and VS Code could resolve the same AppData ledger path differently, preventing VS Code from connecting to an existing local ledger.
Windows setup and repair
- New local installations keep task data in
%USERPROFILE%\.conductor, separate from the program installation. Setup rejects redirectable AppData task-data locations. - Existing installations have an explicit offline repair command. It verifies a consistent SQLite backup and all records, preserves private permissions and ownership metadata, switches settings atomically, and retains the original ledger and rollback journal. Logical and physical aliases of one database are recognized as one source; conflicting databases are rejected.
- Bridge errors identify a missing configured ledger and the possible Windows package-redirection mismatch. Startup and installer retries refuse to initialize an empty replacement for a configured missing ledger.
Existing users: downloading or rerunning setup does not migrate your ledger automatically. Close both clients and follow the repair instructions. Keep the original ledger until both clients pass the shared-read/write and restart checks.
Download ConductorSetup.exe below for new Windows installations. Run it as your normal Windows user. The accompanying SHA-256 file verifies the download. macOS and Linux state-directory defaults are unchanged.
Validation
Installer, GUI, bridge, and migration tests passed locally, including interrupted two-profile migration and rollback. The corrected installer passed its packaged self-test. Actual Codex Desktop and VS Code health, writes in both directions to the same migrated ledger, and post-restart reads were verified on the repaired Windows installation. Actual macOS client testing was not performed for this patch.
The release workflow builds the installer from this tag, runs Windows setup tests and the packaged self-test, and publishes the installer and checksum.