Skip to content

[RELEASE] OpenExecutive as the 32nd runtime (carries #5921) #5924

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vivekchand merged 1 commit into from
Sep 12, 2026
Merged

[RELEASE] OpenExecutive as the 32nd runtime (carries #5921) #5924

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@
- **Also fixed:** `muse_code` was missing from `sync._RUNTIME_PREFIXES` and app.js `_CM_RT_PREFIXES`, so its sessions were bucketed as openclaw there.
- **Verified:** `tests/test_openexecutive_runtime_wiring.py` (13 tests, in CI), and the adapter against a store written by OpenExecutive's own storage code at upstream 8b2a9a7.
- **Carries:** #5921.
- **Released:** carries #5921 (merged as `e0537a0fbc`). The adapter ships in clawmetry-pro 0.7.26, already served by the cloud (clawmetry-cloud #2424); 0.7.27 (clawmetry-pro #247) follows with the zero-usage honesty fix found by a real end-to-end turn.

### Fixed: a correct emailed code dropped you back on "Sign in to open the dashboard" (2026-09-12)
- **Why:** a paying customer reported it after reinstalling: enter the email, enter the code from the email, and the local dashboard shows the sign-in card again, every time. The login wall accepts only the gateway token. Email sign-in succeeded against the cloud but handed the page no credential: it cleared the signed-out marker and reloaded, relying on zero-click `/api/auth/detected-token`. That endpoint refuses unless every strict loopback check passes (client address, Host header, no proxy headers, loopback bind). Wherever one of them fails, zero-click fails on every load, so a correct code reloaded into the same wall forever.
Expand Down
Loading