Repository navigation
Releases
v0.4.4
Synrex v0.4.4 — first-use and Windows deployment reliability
This patch addresses the problems observed during a real Windows first-time
deployment. The original public MCP URL, OAuth identity, SQLite state and
installation owner remain unchanged.
Changes
- Uses arrow keys and Enter for a single ChatGPT / Coding Agents / Both choice,
with explicit Space instructions only for genuine multi-selection. - Skips irrelevant Coding Agents setup when only ChatGPT is selected.
- Adds
synrex config roots list|add|removeto avoid repeated
init --forcefor normal project changes. The initial Windows
flow favors a dedicated D: project root when present and asks before
creating new directories. - Adds
synrex doctor --connectwith read-only local MCP, public
MCP and OAuth metadata checks, explaining expected 401 Bearer, missing DNS
routes, origin 502 and authorization interception. - Improves the existing Windows portable Task Scheduler generator: silent
startup, separate bounded logs, repeat-on-failure policy, single-instance
policy, and Unicode-safe script encoding. - Extends native Windows acceptance with generated script syntax, project
management and task registration/startup checks.
Upgrade / rollback
- Stage and activate the official v0.4.4 archive with the portable installer;
the previous version remains available for explicit--rollback. - The installer never replaces an existing scheduled task, Cloudflare Tunnel,
Owner secret or OAuth store. Generate and inspect new task definitions
before registering; old customized scripts are not silently overwritten. - Windows task autostart is user-login based, not a pre-login SYSTEM service.
- Production activation remains separately gated by real authenticated MCP
verification, backup and rollback.
Availability requires an annotated v0.4.4 tag, a successful exact-commit
main CI run and a published GitHub archive/checksums. Notes alone do not
prove publication.
v0.4.3
Synrex v0.4.3 — Windows silent startup and tunnel recovery
This patch integrates the verified tunnel recovery change and makes newly
generated Windows portable autostart tasks launch without a visible console.
Changes
- A bounded Cloudflare tunnel watchdog can request nonblocking recovery after
repeated zero-HA samples even when the WAN probe is unavailable. It does not
infer tunnel recovery from a successful restart request. - Newly generated
Synrex.PortableWindows Task Scheduler definitions use
wscript.exewith a generated hidden launcher, avoiding a transient
interactive PowerShell or Node console. Generation remains opt-in and
refuses to replace existing service definitions. - Existing standalone operational tasks
Synrex.WinDirectand
Synrex.SwyPublicMonitorremain separate, user-managed installations.
Updating the official portable package intentionally does not overwrite
those scheduled tasks, addresses or OAuth configuration.
Compatibility and rollback
- CLI, OAuth identity, SQLite state, tool contracts and installation prefix
remain compatible with v0.4.2. - The optional Windows startup script is a newly generated artifact; running
the release installer alone does not register or start it. - Use the portable installer to stage and explicitly activate v0.4.3; prior
versions remain available for--rollback. - swy1 production promotion is separately gated by the immutable main
release, backup, tests and its existing rollback procedure.
Release availability requires a verified annotated v0.4.3 tag, CI-successful
source commit and published GitHub archive/checksums. This note alone is not
evidence that publication has completed.
v0.4.2
Synrex v0.4.2 — Windows portable install repair
These notes describe the intended v0.4.2 patch release. The immutable tag,
published archive, checksums and CI evidence—not this document—establish whether
the release has been published.
Why this patch exists
Real Windows x64 testing of v0.4.1 found that pnpm could install successfully
in a temporary directory but create absolute Junction targets. Moving that
directory to releases/v0.4.1 broke module resolution, including
@clack/prompts, although --stage had reported success. A separate initial
npx failure also lacked sufficient diagnostics when its output was on stdout.
Changes
- Verify release archive content and digest in a temporary staging directory;
move the unpacked package into its final version directory before pnpm
creates dependency links, still using pnpm 11.25.0 and the exact published lock. - Verify actual CLI execution from the final path before accepting staging,
activation or rollback. Never treat package metadata alone as success. - On failed installation, remove only the incomplete new release; preserve
existing versions and the active portable version pointer. - Report the child-process exit code and bounded stdout/stderr on installation
failures, and prevent regressions with native and synthetic Junction tests.
Compatibility and scope
- Node.js >=22.19 and <27. Existing CLI aliases, MCP/OAuth endpoints, Owner
credentials, SQLite, worker identity and interface contracts are unchanged. - Linux production remains a separate pinned release and is not switched by
publishing this patch. A Windows peer already using v0.4.1 is not implicitly
upgraded by the GitHub Release. - The manual Windows reproduction used the official v0.4.1 archive with the
repaired installer in a fresh isolated prefix. Formal v0.4.2 release gates
still require passing CI, signed tag provenance, checksums and assets.
Installation and rollback
- Back up the existing configuration and state before changing live services.
- Download the published
synrex-0.4.2.tgzandSHA256SUMSfrom this tag
after publication. Verify the archive digest. - Run
node deploy/portable-install.mjs --stage --version 0.4.2with an
isolated--prefix. A successful stage now verifies the final CLI path. - Run
--activate --version 0.4.2only after testing. Activation changes
the portable launcher pointer but never restarts a live service. - Run
--rollbackto switch back to the previous verified portable version
if required. Owner production deployment follows its separate audited path.
Do not move or overwrite v0.4.1's immutable tag or GitHub assets.
v0.4.1
Synrex v0.4.1 — security and release-integrity update
These are the release notes for the v0.4.1 security patch. The exact release archive, tag and verification evidence are authoritative; a document alone does not establish publication.
This patch is intended for self-hosted single-owner installations. Linux remains the primary supported production platform; macOS and Windows receive native packaging and portable installation acceptance, but are not guaranteed to match all Linux shell and sandbox behavior.
Changes
- Refresh vulnerable direct and transitive dependencies, including the MCP SDK/server/client packages, HTTP proxy/IP handling,
undici,zod,node-forge, and parser dependencies. - Add blocking dependency-security and native macOS/Windows package-install checks before stable publication.
- Include the immutable pnpm dependency lock in release archives and machine-readable SBOM, plus archive checksums and build provenance.
- Document supported platforms, vulnerability reporting, setup, safe upgrade and rollback boundaries.
Compatibility
- Node.js >=22.19 and <27; Node 24 is used for native macOS/Windows acceptance.
- The
synrexCLI and legacydevspacealiases, single Owner OAuth identity, MCP URL, existing persistent SQLite and workspaces remain unchanged. - Existing experimental Windows peers and gateway nodes are not automatically upgraded. Keep exactly one writable Owner and avoid duplicate peer identities.
- No API/host-side automatic wake-up of ChatGPT reasoning is claimed after a terminated chat session.
Upgrade
- Back up Owner configuration, secrets and SQLite using a consistent online snapshot. Record active systemd
ExecStartand keep the previous immutable release. - Download the release archive and
SHA256SUMSfrom this exact tagged GitHub Release. Verify SHA-256 before using the portable staging command. - Stage in a new user-controlled prefix using
node deploy/portable-install.mjs --stage --version 0.4.1 --source ./synrex-0.4.1.tgz --sha256 SHA256_FROM_RELEASE. This does not replace a live service. - Test
--version,doctor, authenticated OAuth/MCP and, if applicable, independent Console health. Explicitly activate the portable pointer, or follow the pinned Owner promotion path documented indocs/platform/SINGLE_OWNER_SELF_HOSTED.md. - Verify the active production manifest, public OAuth discovery, authorized tools, backup integrity, and rollback procedure. Never change the public issuer or copy the Owner SQLite to another peer.
Rollback
- Portable launcher:
node deploy/portable-install.mjs --rollbackrestores the prior verified pointer if one exists; it does not automatically roll back running system services. - Pinned Linux Owner: follow the backed-up, guarded immutable-release activation process; restore the previous service manifest and compatible SQLite snapshot only when necessary and authorized.
- Do not delete or overwrite the old release during installation. A successful Git push or Release does not mean production has been updated.
Known limits
- Native Mac/Windows CI validates installation and package entrypoints, not every Linux-only sandbox, shell/TTY behavior or real physical peer.
- Windows legacy peer and offline gateway migration are separate live operations.
- The ordinary ChatGPT UI interruption/reconnect journey needs a real client session; the durable execution and workflow-checkpoint mechanism does not resume model inference on its own.
Verification
For release acceptance use the exact source SHA, main CI run, release workflow run, SHA256SUMS, SBOM, provenance attestation, native OS tests and pinned production manifest. Do not treat documentation or synthetic tests as substitutes for an observed live deployment.
v0.4.0
v0.3.0
v0.2.0
What's Changed
- release: establish DevSpace Verge 0.1.0 by @yuezhihuafou in #4
Full Changelog: https://github.com/yuezhihuafou/synrex/commits/v0.2.0
Synrex v0.1.0 - Public Preview
First public preview of Synrex, an independently maintained MIT-licensed derivative of Waishnav/DevSpace. Includes GPT-first MCP coding, durable execution, workflow checkpoints, multi-host support and an owner-authenticated read-only Console. Linux is the primary supported platform; self-hosting and personal OAuth configuration are required. This release tracks the source of the pinned swy1 production build 32436d4 plus public README changes. It does not bundle private configuration or runtime state. Known limits: Windows best effort; controlled end-to-end comparisons with upstream and comprehensive WAN fault testing remain open.
Synrex early access | 2026-10-22 pinned runtime
Early-access self-hosted preview matching the pinned swy1 owner runtime source eea07ec. Includes GPT-first MCP coding/execution, durable tasks, checkpoint recovery, multi-host peers, owner Console and diagnostics. Requires your own Linux host, authenticated MCP ingress and configuration; see README and docs/TRY_SYNREX.md on main. This is a source release, not a hosted service. No claim of proven end-to-end superiority over upstream DevSpace. Derived from Waishnav/devspace under MIT; attribution retained. In-progress development changes are excluded.