Xynapse IDE

AI-Powered Development Environment

Website | English | Русский

---

Updates via GitHub Releases

Xynapse supports manual in-app updates on Windows through GitHub Releases.

1. The user clicks Help -> Check for Updates.
2. Xynapse requests the latest release from the repository configured in vscode/product.json.
3. The app compares the current version with the release semver tag.
4. If a newer version exists, Xynapse selects the matching Windows asset.
5. Setup builds download the installer and apply it through the standard restart flow. Portable builds open the release asset for download.

Detailed documentation:

• English update notes
• Russian update notes

Profile, Account, and Encrypted Backup

• profile.json stores user-readable identity:
  • name
  • email
  • isConfigured
• account.json stores the sync payload:
  • name
  • email
  • isConfigured (derived from real key material)
  • createdAt
  • keys (full raw content of key files from your local .xynapse folder, including config.yaml, config.json, config.ts, out/config.js, .env, .xynapserc.json, and sharedConfig.json)
• isConfigured is computed from actual keys, not from cached flags in JSON files.
• Strict mode: if account key material is absent, key files are not applied and profile is local/unconfigured.
• Legacy auto-migration: if account.json is missing but old key files exist in .xynapse, Xynapse creates an account automatically and notifies the user.
• On first start (if profile/account is missing and no keys are found), Xynapse creates a local profile and shows a notification about setup for encrypted sync.
• Export/Import config backup always includes both profile.json and account.json and keeps local/remote sync reproducible across machines.
• Git sync is still supported through exported .enc files; local import/export also works via Ctrl+Shift+P actions.

Council and BVC

Xynapse has two separate multi-agent planning modes:

• /council is a free-form Council discussion: PM, Architect, Developer, and Reviewer propose, critique, and synthesize council-plan.md.
• /bvc is the formal Budgeted Verified Council algorithm from the diploma: fixed axes root_cause_location, fix_strategy, dependencies_to_update, test_coverage, structured votes, D_vote, D_cov, adaptive critique, budget guard, and bvc-plan.md.

The modes are intentionally separate: Council is for practical planning UX, BVC is for mathematically traceable planning.

Portable Build

A portable package can be assembled in a dedicated folder:

.\portable-build.bat

What it does:

• uses built VSCode-win32-x64 output,
• creates portable-build\xynapse-portable,
• stores user data under portable-build\xynapse-portable\data.

How to test:

.\portable-build\xynapse-portable\Xynapse.exe

If you want to use a custom source/output path, pass them as arguments:

.\portable-build.bat "C:\Path\To\WinBuild" "C:\Path\To\Out"