Skip to content

feat(workers): support two split workers and resilient browser wake - #530

Merged
chadbyte merged 2 commits into
mainfrom
feat/vendor-neutral-worker-efficiency
Sep 18, 2026
Merged

chadbyte merged 2 commits into
mainfrom
feat/vendor-neutral-worker-efficiency

Conversation

@chadbyte

Copy link
Copy Markdown
Owner

Enable one Driver to manage up to two visible Workers, with vendor-neutral runtime selection, explicit Worker targeting, independent task and permission state, durable result isolation, and authoritative configuration cards. The Driver stays on the left while Workers stack on the right; membership changes preserve unchanged iframe browsing contexts.

Targeted close validates the exact owner, group, origin and generation. Failed persistence preserves live work, and unproven close preparations remain non-deliverable instead of fabricating completion.

Fix browser reconnect watchdogs so hiding or freezing a page retires stale timers without closing its socket. Resuming starts a fresh bounded liveness check; real dead-socket recovery, authentication, handshake and retry policy remain intact.

Validation: independently ran the full suite (2,441 passed, 1 skipped, 0 failed), focused connection regressions, and diff checks. Earlier mocked browser checks covered stacked layouts and iframe preservation.

Limits: actual Arc Space-switch behavior and live provider execution remain unverified. V2 scheduled Driver continuation remains unsupported. A crash between structural close persistence and outcome finalization remains uncertain. No daemon restart or deployment was performed.

Add vendor-neutral delegation guidance, exact Worker targeting, and
transactional role persistence with durable result isolation. Enable
project configuration cards and stacked panes that preserve unchanged
iframe contexts.

Authorize targeted Worker close through the Driver and retain uncertain
close preparations without inferring completion from missing membership.
Retain the socket while hidden or frozen and start a fresh bounded
liveness probe on resume. Fence queued timer callbacks by generation
without changing authentication, handshake, or reconnect backoff.
@chadbyte
chadbyte merged commit a5d02cf into main Sep 18, 2026
2 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

This issue has been resolved in version 4.3.0-beta.6 (main).

To update, run:

npx clay-server@4.3.0-beta.6

-- Clay Deploy Bot

Build anything, with anyone, in one place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant