TandemVector Labs | Remote Commander Core v0.10.25 | UNSIGNED Preview

Remote Commander Core v0.10.25 — TandemVector Labs | UNSIGNED Preview

Project brand / publishing organization: TandemVector Labs (Usefull-Skills on GitHub).

Principal author and lead release maintainer: Dr. Aliakbar Emadoddin (@GOD13emad).

Supporting source maintainer: MMZ (@mohammadmohammadzadeh19960-code).

Canonical public source: https://github.com/GOD13emad/ChatGPTRemoteCommander — MIT license.

Release channel: public prerelease / Preview, NOT Stable. Browser v0.8.1 remains an independently versioned Stable product. This preview does not change Stable automatic update defaults.

Windows installer: UNSIGNED — explicit v0.10.25-only release consent

On 2026-10-20, the user explicitly requested UNSIGNED public distribution of v0.10.25 because a trusted Authenticode certificate is not currently available in Iran. This is a separate, version-specific exception, not a carry-over from v0.10.24. Windows may display Unknown publisher; SmartScreen or Smart App Control may warn or block. GitHub project names, checksums and GitHub attestation do not replace Authenticode. Do not disable or bypass operating-system security features to execute the installer.

The project brand and attribution describe the GitHub organization and source authorship. They do not establish registration of a legal company or a trusted Windows software-publisher signature. This notice does not claim the named author personally reviewed or signed this build.

Included Core scope

Cross-platform MCP/Router, user-authorized capability profiles, durable operations/workflows, independent multi-profile routes and bounded noninteractive execution. The updater checks exact GitHub release origin and refuses ambiguous version/status and unsafe downgrade, preserves explicitly configured Linux Runner policy, and uses candidate-first verification and rollback. The integrated source CI retains fixed Windows fixture deadlines and full test coverage.

Experimental GUI/broker designs, Browser CEF shell changes, speculative agents and native Control Center releases remain outside this Core Preview. No existing uncertain GUI event is replayed or cleared.

Verify before using

1. Verify annotated Git tag v0.10.25 and its exact peeled source commit.
2. Check all 20 release files against the attached SHA256SUMS.txt including the final Remote-Commander-Setup-v0.10.25.exe binary.
3. Independently verify GitHub Sigstore provenance / GitHub attestation using the exact tag, source digest and .github/workflows/release-sync.yml signer workflow. Provenance proves the workflow origin/integrity, not Windows publisher trust.
4. Independently read the Windows setup Authenticode status; an UNSIGNED result is expected. No OS security safeguards should be bypassed.
5. On any explicit future opt-in to install, preserve profiles, browser user data, workflow SQLite/journals and one tested rollback; existing live developer 0.10.25 commits are not interchangeable with the published tag.

Acceptance boundary

The final integrated candidate passed hosted Windows/Ubuntu CI, Windows NoPromote, Server Canary, and dedicated Windows/Linux isolated promotion/rollback. These passes do not establish human visual GUI acceptance or fleet-wide installed rollback. User-owned desktop/session state and versioned rollback are preserved. This Preview is not eligible for unattended Stable rollout.

See the version-scoped policy file UNSIGNED_WINDOWS_RELEASE_POLICY_0.10.25.json and original historical v0.10.24 policy, along with PUBLISHER_AND_MAINTAINERS.md.

TandemVector Labs | Remote Commander v0.10.24 | UNSIGNED Preview

Remote Commander Core v0.10.24 — TandemVector Labs official preview

Project brand: TandemVector Labs (GitHub organization Usefull-Skills).

Primary repository and release maintainer: Aliakbar Emadoddin (@GOD13emad).

Supporting collaborator: MMZ (@mohammadmohammadzadeh19960-code).

Repository: https://github.com/GOD13emad/ChatGPTRemoteCommander — MIT license.

Channel: official public prerelease for evaluation. Stable Core remains v0.10.20, while v0.10.23 remains a separate pre-existing Draft. The Browser stable v0.8.1 is independently released and not implicitly updated.

Features included

• PR #221: Router status bootstrap restricted to owned loopback/port/path with redirects forbidden; bounded security audit history streaming.
• PR #222: HTTP fixture readiness validates exact server config and a bounded timeout.
• PR #223: Coucou native hook isolates its working directory to avoid inherited private project path; remains opt-in.
• PR #226: Control Center reports healthy only when Router, profile, version, commit, config hash and backend match.
• Cross-platform Core and native management/source qualification, rollback and installer contracts.

Windows installer: UNSIGNED — explicitly approved for this version only

The owner authorized a Windows UNSIGNED release on 2026-10-16 because a trusted Authenticode signing certificate was unavailable. An Unknown publisher warning or refusal from Microsoft SmartScreen or Smart App Control is possible. The project brand and GitHub attestation plus SHA256 do not replace Authenticode. This release does not instruct users to disable or bypass Windows safeguards.

Verify the SHA256 of every downloaded asset against the release SHA256SUMS manifest, then verify GitHub Sigstore provenance against the exact annotated v0.10.24 tag, source commit and release-sync signer workflow. Source provenance is not an OS publisher signature.

What is verified and what remains open

The versioned source passed Windows Emad, Linux Emad and MMZ isolated source checks. Hosted R170 Linux and R173 Windows real promotion/rollback, R34 native Control Center, unified R39 UI, R32/R35 GTK, Server Canary on both systems, and latest R157 NoPromote CI succeeded in isolated runners. The original unsuccessful R157 attempt is retained as evidence; root cause remains unproven.

NOT FINAL: owner-native CEF login and session preservation, RTL and HiDPI end-user visual acceptance, historical J01 uncertain GUI input, authenticated same-chat Work ACK and Runner, Saeid Windows private R478, four-host Mesh power-loss and serial production rollout. No unattended Stable upgrade or modification to user installations is authorized by this preview.

Attribution: Project coordination under TandemVector Labs brand; lead release maintainer Aliakbar Emadoddin; supporting maintainer MMZ. This is attribution to public project GitHub identities, not an attested business registration, Authenticode certificate or legal warranty.

See publisher and maintainers and version-specific unsigned release policy.

Remote Commander v0.10.20

Remote Commander v0.10.20

v0.10.20 is a narrow successor to immutable v0.10.19. It does not change the accepted Browser v0.8.1 dependency or general Core execution policy.

GNOME 50 in-session upgrade fallback

v0.10.19 introduced the fresh chatgpt-remote-commander-linux-safe-v2@god13emad UUID to avoid stale GJS module reuse. Live GNOME Shell 50.1 evidence showed that a brand-new local UUID is not dynamically discoverable in the already-running Wayland Shell session: the files and enabled setting existed, but GetExtensionInfo was empty, EnableExtension returned false, and ReloadExtension is explicitly unsupported. No logout/reboot was permitted.

v0.10.20 keeps the v2 path, but when that UUID is not discoverable it may reuse the previously-known chatgpt-remote-commander-linux-safe@god13emad backend only if its exact GNOME-50 compatibility SHA-256 pair matches the accepted migration bytes. The fallback is never synthesized or modified in place, and the pre-safe legacy UUID remains quarantined. Fresh installations with no exact known-safe fallback remain fail-closed and persist v2 for the next Shell session.

Live evidence on mmz-LOQ-15IRX9: exact fallback extension SHA-256 084c6c1244b25b4a714b0978d7f59b0b02fa8dbce45a962bff6cda6d18a17caa, metadata SHA-256 71375ff9ff21387355de83275be8a4b42361626208bcc120e7e41e6ffb08688e; activation produced a real org.gnome.Shell.Extensions.ChatGPTRemoteCommander bridge and gui_status reported Wayland with screenshot/cursor/window-list/mouse/keyboard/focus all available.

Windows qualification harness stabilization

On the loaded Emad Windows host, the exact v0.10.19 runtime passed hosted Windows CI but the full local qualification intermittently exceeded two short test-harness windows: async continuation recovery (3 s) and the first delayed terminal read (2 s). The two affected tests then passed three consecutive isolated runs on the same host with zero product mutation.

v0.10.20 changes only those test harnesses: continuation recovery gets an 8 s bounded evidence window, and delayed terminal output uses the existing accumulating bounded-read helper for up to 5 s instead of assuming the first read contains the marker. Production terminal/continuation implementation and user-facing command timeouts are unchanged.

Preserved safety

• no reboot, shutdown or logout path is added;
• no GNOME Shell replacement or kill is permitted;
• no raw Clutter/virtual-input injection is introduced;
• mouse/keyboard transport remains org.gnome.Mutter.RemoteDesktop;
• exact fallback hashes are mandatory;
• Browser v0.8.1 remains pinned by immutable SHA-256;
• candidate-first update, rollback, drain and idempotency gates are unchanged.

Remote Commander v0.10.19

Remote Commander v0.10.19

v0.10.19 completes the cross-platform monitoring/control parity work on top of
immutable v0.10.18 and the merged GNOME 50 compatibility revision.

Changes:

• adds an owner-private short-lived Browser Companion live monitor snapshot;
• exposes exact Core identity, GUI readiness, background-browser readiness,
  durable workflow count, Agent Extension inventory count and operation/lock
  counters to the native Remote Commander Browser panel;
• keeps the Browser monitor read-only: no web-page bridge, command channel,
  credentials, cookie access or execution authority is added;
• records GUI/background-browser UNCERTAIN separately so uncertain backends are
  never rendered as READY;
• carries the GNOME 50 monitor/compositor compatibility fix from PR #138;
• moves the Linux GNOME bridge to the fresh
  chatgpt-remote-commander-linux-safe-v2@god13emad UUID so the corrected module
  can be loaded in the current GNOME session without reboot/logout while
  superseded UUIDs are quarantined;
• preserves Mutter RemoteDesktop as the only Linux mouse/keyboard injection
  path and preserves explicit takeover, fresh-frame and local-stop safety gates.

Pinned Browser dependency:

• Remote Commander Browser v0.8.1 is immutable/non-prerelease at commit 39258bc8e143aa666465e0ad63c4f277b075fcf3.
• Windows Setup Remote-Commander-Browser-Setup-v0.8.1.exe SHA-256 is dcf4c5bc5d0ca8788f803e469246512af3745c81f578411dbabf6ce2a97feca2.
• v0.10.19 release/build must fetch that exact immutable version and hash; v0.8.0 remains rollback history.

Release acceptance requires exact-head Windows/Linux qualification, hosted CI,
release-sync/server-canary/security gates, candidate-first live rollout and
post-rollout Browser monitor plus GUI readback. v0.10.18 remains immutable
rollback history.

Remote Commander v0.10.18

Remote Commander v0.10.18

v0.10.18 is a bounded Linux rollout-readiness hotfix on top of immutable v0.10.17.

The Linux updater retains /readyz=ready as its direct tunnel readiness fast path. If /readyz is non-ready, the updater requires both /healthz=live and a positive commands_poll_last_successful_timestamp_seconds metric whose age is within the bounded REMOTE_COMMANDER_TUNNEL_STALE_SECONDS window (90 seconds by default). Missing, zero, stale metrics and non-live health remain failures. The gate remains before CUTOVER_COMMITTED=1.

The change closes a reproduced false-negative on saeed-emad-laptop: its local /readyz OAuth-discovery subcheck reported connection refused while the same tunnel was actively forwarding Remote Commander calls and exposed a zero-second-old successful control-plane poll. Candidate v0.10.17 doctor, hardware selftest, qualification and schema-continuity had already passed; the route was preserved because the old gate failed before cutover.

Remote Commander Browser v0.8.0 remains the same immutable stable dependency. No browser login/profile behavior, credential authority, filesystem/model authority, tunnel credential/process ownership, automatic retry or safety/admission policy is widened.

Promotion requires exact-head Windows qualification/audit, exact-head Linux focused/live plus full qualification/audit, hosted CI/Release Sync/Server Canary, immutable tag publication, release-asset verification, and candidate-first live rollout/readback.

Remote Commander v0.10.17

Remote Commander v0.10.17

v0.10.17 is a bounded maintenance/finalization release on top of immutable v0.10.16.

The Windows updater now preserves stdout and stderr for every qualification gate in per-run files, records their paths before execution, and records SHA-256 digests after completion. This closes a diagnostics gap observed when an unattended exact-release qualification returned exit 1 but only its lifecycle JSON survived.

Safety semantics are unchanged: qualification still runs inside the existing owned Windows Job Object; nonzero child or runner exit remains failure; timeout, cleanup, backoff, candidate-first promotion, one-writer routing and fail-closed behavior are unchanged. No automatic retry is added and no failed gate is converted into success.

Remote Commander Browser v0.8.0 stable remains the separately versioned immutable stable Browser dependency pinned by the Windows Setup. v0.10.17 does not widen browser-profile reuse, saved-password access, foreground takeover, authentication, model or filesystem authority.

Promotion requires exact-head local Windows qualification/audit, hosted Windows+Ubuntu CI, clean Windows/Linux server canaries, Linux cross-host check/audit, immutable tag publication, release-asset verification and post-rollout live readback. The v0.10.16 tag and assets must not be moved or rewritten.

Remote Commander v0.10.16

Remote Commander v0.10.16

Purpose

v0.10.16 turns the Windows packaging surface into one product instead of several Start Menu utilities. It introduces a single-file Windows Setup bootstrap for fresh Windows systems, with explicit Core-only versus Control & Monitoring installation modes and post-install multi-profile onboarding.

Change

• Windows Start Menu now publishes one Remote Commander application. Profiles & Access, Operations Monitor, and Admin Runtime stay inside the product shell instead of appearing as separate applications.
• The Windows desktop icon asset is rebuilt as a standards-compliant multi-size ICO and is used consistently by the product shell and Setup.
• The new Inno Setup bootstrap installs Commander on a fresh x64 Windows system, installs verified machine prerequisites when missing, and keeps per-user Commander/profile state in the original user context.
• Setup offers Commander Core or Commander + Control & Monitoring. A desktop shortcut remains optional.
• Setup accepts one or more profile names and launches a dedicated post-install profile enrollment UI. Runtime API keys are passed in memory and are never placed on a child-process command line.
• Profile enrollment retains the existing fail-closed tunnel validation and DPAPI persistence boundary.
• The release workflow builds the single-file Setup on a pinned Windows runner toolchain, adds its SHA-256 to the release checksum manifest, and publishes it together with the existing immutable release assets.
• The Windows Setup bundles the qualified Remote Commander Browser v0.8.0-rc.8 as an optional component. Release CI downloads that immutable Browser release asset and verifies its pinned SHA-256 before the Commander Setup is compiled.

Browser boundary

Remote Commander Browser v0.8.0-rc.8 remains a separately versioned product, but its qualified standalone Windows Setup is now an immutable, hash-pinned dependency of the v0.10.16 Windows Setup. Selecting the Browser component runs that bundled installer silently without changing or automating the user's ChatGPT sign-in session. Commander discovers the Browser at its per-user Remote Commander Browser\\current install path. The Commander's existing Chromium/CDP automation backend remains a separate backend and is not replaced by the CEF Browser.

Release discipline

v0.10.15 remains immutable. v0.10.16 may be promoted only after exact-head Windows qualification, hosted CI and Windows Server canary PASS, Linux laptop and Amirreza Server exact-head acceptance, immutable tag/release publication, and post-release live readback. The single-file Setup is a release asset only after those gates pass.

Signing

The build records Authenticode status. If no organization-controlled code-signing certificate is available at release time, the Setup remains functionally installable but Windows may show an Unknown Publisher/SmartScreen warning. A self-signed certificate is not treated as production signing evidence.

Known non-goals

This release does not change browser session/login automation policy, scheduler semantics, physical reboot/AC-loss behavior, Linux GUI architecture, or tunnel credential authority. Physical power-return validation remains a separate hardware/operations gate.

Remote Commander v0.10.15

Remote Commander v0.10.15

Purpose

v0.10.15 is a narrow hotfix release on top of the immutable v0.10.14 merge/tag. It closes the remaining Windows interactive-terminal readiness race found by independent hosted Windows CI and Windows Server canary execution.

Change

• Windows interactive terminals with an initial command launch PowerShell using -NoExit -Command <validated command>.
• The initial command is no longer written to redirected stdin before shell readiness.
• Follow-up send_terminal input continues through the same stdin pipe.
• Linux interactive-shell behavior is unchanged.
• Lifecycle regression reads successive bounded terminal chunks until the expected marker or a fixed readiness deadline.
• Release/runtime/install/server/plugin identities advance to 0.10.15.

Release discipline

v0.10.14 remains immutable. v0.10.15 may be promoted only after exact-head Windows qualification, hosted CI and server canary, Linux laptop acceptance, Amirreza server acceptance, merge, immutable tag/release publication, and post-release install/readback evidence.

Known non-goals

This hotfix does not change scheduler semantics, browser session/login handling, tunnel credentials, desktop takeover policy, or Linux GUI architecture.

Remote Commander v0.10.14

Remote Commander v0.10.14

This candidate closes multiple Linux post-cutover maintenance gaps observed across the v0.10.11–v0.10.13 history and reproduced during a live v0.10.14 candidate rollout. Historical CR-at-EOL drift prevented safe control promotion on recovery, the personal Work/Codex projection could remain stale, and—more importantly—a manual updater launched through a Commander terminal could be killed when that same old backend was retired. Successful completion also had no durable last-update.json receipt even though the path was defined.

Linux control promotion

The Linux updater now applies the same fail-closed distinction already proven on Windows:

• any staged tracked change blocks promotion;
• any substantive unstaged tracked change blocks promotion;
• CR-at-EOL-only working-tree drift is tolerated and logged as CONTROL_EOL_DRIFT_TOLERATED;
• the exact fetched commit is verified after forced detached checkout and logged as CONTROL_PROMOTION_PASS.

The post-commit ERR trap remains active through maintenance, so failures after route cutover are classified instead of disappearing between CUTOVER_COMMIT and durable updater completion.

Commander-owned invocation isolation

When auto-update-linux.sh is invoked from a process tree owned by a managed Commander backend, it now detects that ancestry through a bounded /proc walk before taking the update lock. It re-executes the exact original arguments under nohup setsid -f with a one-shot REMOTE_COMMANDER_AUTO_UPDATE_DETACHED=1 guard, logs AUTO_UPDATE_SELF_DETACH_REQUESTED, and lets the caller exit. Normal supervisor-launched updates and --self-test do not detach. Missing setsid fails closed.

This prevents drain_previous_once / old-backend retirement from terminating the updater that is still responsible for control promotion, plugin synchronization, cleanup and durable PASS recording.

Durable Linux update receipt

Before logging AUTO_UPDATE_PASS or AUTO_UPDATE_MAINTENANCE_PASS, the updater atomically writes a mode-0600 last-update.json receipt containing schema, Linux platform, pass type, exact version, exact 40-hex commit, bounded source ref and UTC completion timestamp. The write uses a same-directory temporary file plus atomic rename; invalid identity fails closed and does not replace the prior receipt.

Work plugin projection sync

When the personal Remote Commander Work/Codex plugin is already installed, the updater now synchronizes its source projection from the exact staged release plugin-template in both the same-version maintenance-recovery path and the normal post-cutover path.

The operation is intentionally narrow:

• absence of the personal projection is a safe no-op;
• the existing .app.json must be a regular file with a valid app-id shape;
• the staged portable and native manifests must both match the candidate version;
• the private app binding is never logged and is preserved byte-for-byte;
• a prestate copy is retained under the commit-specific updater backup root;
• a fresh candidate copy is prepared off-path, personalized exactly as the Work installer does, and atomically swapped into place;
• swap or post-verification failure rolls back to the prior projection;
• portable/native versions, app references, personal display metadata and the app-binding SHA-256 are verified before WORK_PLUGIN_SOURCE_SYNC_PASS.

Qualification

Focused Linux updater/installer/schema regressions after self-detach + durable-receipt hardening: 24 pass / 0 fail / 1 platform skip.

check:qualification: 270 total / 264 pass / 0 fail / 6 platform skips.

test:qualification: 516 total / 510 pass / 0 fail / 6 platform skips.

Supplementary GUI contract 77/77, Linux GUI, filesystem safety, headless launch policy, Windows runtime contract, source integrity and schema continuity 9/9 all pass. SECURITY_AUDIT_PASS.

Linux-only deployment scope

Current owner direction limits this milestone to Linux and Linux-specialized functionality. v0.10.14 is therefore qualified and deployable as an exact-commit Linux candidate on the current Linux host, but it must not be treated as a general cross-platform release or merged/tagged as such until a separate Windows scope is explicitly resumed. Windows CI/canary results are informational and out of the current acceptance boundary.

Acceptance

v0.10.13 remains the repository-wide accepted stable release. For the current Linux-only scope, v0.10.14 acceptance requires Linux qualification plus exact-commit rollout and post-cutover evidence on this host. Repository-wide merge/tag publication is deferred. Rollout acceptance specifically requires one first-pass invocation from inside Commander to log AUTO_UPDATE_SELF_DETACH_REQUESTED, continue independently through cutover without a second recovery invocation, promote control to the exact candidate commit, synchronize the personal Work/Codex projection and managed cache to v0.10.14 with the same preserved binding, write the durable last-update.json PASS receipt, and finish with AUTO_UPDATE_PASS.

Remote Commander v0.10.13

Remote Commander v0.10.13

This candidate is a narrow observability follow-up to v0.10.12. The scoped Codex plugin refresh itself is working, but post-rollout validation found an unresolved mismatch between the canonical linux-project-skills source (1.4.13) and Codex plugin/list reporting 1.4.12. v0.10.12 intentionally reduced the Codex response to bounded metadata, but omitted the already-available PluginSummary.source field needed to prove which concrete source path Codex is listing.

Bounded source diagnostics

codex_plugin_refresh now includes a compact source object for each returned plugin and for the requested target. It supports the Codex 0.157.1 protocol source kinds:

• local: bounded local path;
• git: bounded URL/path/ref/SHA;
• npm: bounded package/version/registry; and
• remote: type only.

No arbitrary app-server response is returned. Each textual source field is capped by the existing 512-character field limit, and the existing JSONL frame, marketplace-count and plugin-count bounds remain unchanged.

Authority boundary

There is no delegation-policy expansion. The tool still requires explicit current-request confirmation plus authorized Full Power shell/process authority, still launches only codex app-server, still sends only initialize, initialized, and local-only plugin/list(forceRefetch=true), and still strips API/token credentials from the sidecar environment.

Acceptance

v0.10.12 remains accepted stable until v0.10.13 passes focused regressions, full qualification, hosted Windows/Ubuntu CI, Linux/Windows Server install canaries, immutable release publication, exact-ref rollout, and a live diagnostic refresh that identifies the concrete linux-project-skills source responsible for the 1.4.12 listing.