v0.1.0-dev.61.1

Development build from 8121b6d. Discovered only by deployments explicitly configured with RELEASE_CHANNEL=dev; stable deployments ignore this Pre-release.

Changes in this candidate

• Add browser-bound, self-service first setup and forgotten-login recovery at /admin, verified through the target Worker's runtime Variable or Secret.
• Guide first-time users to copy NAME=value into Cloudflare's Key field; existing entries copy only the value. Verification tolerates surrounding spaces and line breaks.
• Limit new or restarted requests to ten per Server per 60-second window. Resuming and verifying existing requests do not consume that allowance; password/passkey login has its own budget.

Updating from dev.60.1

Update the Server code and its matching public assets together, preserving the Worker, origin, SERVICE_ID, existing variables/secrets, DeviceHub and OAuth KV. No schema migration, browser-login reset, Codex re-enrollment or Personal Agent reauthorization is required. DOTX_ADMIN_CLAIM is optional and is written only when the user chooses self-service verification; do not prefill it during deployment. Wrangler-issued links remain available.

Desktop runtime behavior and wire 5 are unchanged by this candidate. Both packages include the updated browser-login guide. Refresh connected Personal Agent catalogs to receive the current instructions; keep the existing connection.

Installation and update requirements

0.1.0 requires a fresh native installation from 0.0.1; no owner keys, device tokens or OAuth grants are migrated. Preserve native Codex accounts, projects and conversations. Install the Server, connect the first Codex and then connect each Personal Agent using its own access code. Updates within the 0.1.0 development series preserve the account, Worker, origin, SERVICE_ID, browser login methods and DO/KV resources; point both main and assets.directory at this release. Loaded Desktop instances automatically pick up complete first-time configuration; verify the actual owner and connection without a routine app restart. If a newly installed plugin's tool is missing, keep trying normal host loading/refresh while offering a convenient user restart; when needed, arrange a new ordinary Codex Desktop conversation on the same Mac, not a subagent. See the bundled plugin-loading guide. Desktop updates still require refreshing every host retaining old plugin instances and verifying the actual owner version. Refresh each Personal Agent catalog when remote_catalog is true. This release uses wire 5; 0.0.1 uses wire 4. Product versions may differ; wire versions must match. Report component completion separately from link recovery.

Browser administration uses a DotX password or passkey; Wrangler management and Personal Agent MCP OAuth remain independent. For self-service first setup or recovery, open /admin, start a request and write its verification value to DOTX_ADMIN_CLAIM in the target Worker’s Cloudflare Production settings. Both Variable and Secret work. Save and deploy, then return to the same browser to set a password or passkey. The request lasts 24 hours and can resume after closing the page. No CF OAuth client or API-token handoff is required. An authorized Wrangler user can still issue a setup or reset-login link. Browser setup may be deferred while installation continues through Wrangler. Successful recovery replaces browser credentials and signs out previous browser sessions; device and Personal Agent access is preserved. Earlier dev CF browser sessions require one password/passkey setup after upgrading; obsolete CF_OAUTH_CLIENT_ID/CF_OAUTH_CLIENT_SECRET bindings and only their dedicated retired OAuth client may then be removed. Subsequent password/passkey releases preserve saved login methods.

Apply the target Server template's assets.run_worker_first routing array: ["/", "!/assets/", "!/branding/*"]. Keep html_handling and not_found_handling set to "none", and deploy public/_headers with the assets. Public JS/CSS/branding files are served directly by Cloudflare; API and explicit page routes still run through the Worker, with no automatic HTML fallback for unknown API paths.

Server now automatically removes durable request receipts, answer deduplication and response routes after RECORD_RETENTION_DAYS (default 30). Preserve any chosen value in the actual Worker configuration. Existing development receipts keep their creation dates; old interaction records without timestamps start at adoption. Reducing retention applies to remaining records and can make them immediately eligible for deletion. After deletion, old request IDs no longer deduplicate; inspect native state before retrying unknown work. Native Codex tasks and conversations are not deleted. Existing subscription/retry lifecycle cleanup is unchanged. See the version-matched bundled docs for executable steps.

v0.1.0-dev.60.1

Development build from 25dde21. Discovered only by deployments explicitly configured with RELEASE_CHANNEL=dev; stable deployments ignore this Pre-release.

Installation and update requirements

0.1.0 requires a fresh native installation from 0.0.1; no owner keys, device tokens or OAuth grants are migrated. Preserve native Codex accounts, projects and conversations. Install the Server, connect the first Codex and then connect each Personal Agent using its own access code. Updates within the 0.1.0 development series preserve the account, Worker, origin, SERVICE_ID, browser login methods and DO/KV resources; point both main and assets.directory at this release. Loaded Desktop instances automatically pick up complete first-time configuration; verify the actual owner and connection without a routine app restart. If a newly installed plugin's tool is missing, keep trying normal host loading/refresh while offering a convenient user restart; when needed, arrange a new ordinary Codex Desktop conversation on the same Mac, not a subagent. See the bundled plugin-loading guide. Desktop updates still require refreshing every host retaining old plugin instances and verifying the actual owner version. Refresh each Personal Agent catalog when remote_catalog is true. This release uses wire 5; 0.0.1 uses wire 4. Product versions may differ; wire versions must match. Report component completion separately from link recovery.

Browser administration now uses a DotX password or passkey; Wrangler management and Personal Agent MCP OAuth remain independent. After deploying this Server, run admin.mjs setup and give the private link to the user. They choose a password or passkey directly on their Worker; no CF OAuth client or API-token copying is required. Browser setup may be deferred while installation continues through Wrangler. Preserve DeviceHub and OAuth KV. Earlier dev CF browser sessions no longer work: set up the new login once, then remove obsolete CF_OAUTH_CLIENT_ID/CF_OAUTH_CLIENT_SECRET bindings and only the CF OAuth client dedicated to that retired login. Do not recreate the DO, device identities or Personal Agent connections. Subsequent password/passkey releases preserve the saved login methods. A forgotten browser login can be recovered through admin.mjs reset-login; successful reset clears only browser credentials and sessions.

Apply the target Server template's assets.run_worker_first routing array: ["/", "!/assets/", "!/branding/*"]. Keep html_handling and not_found_handling set to "none", and deploy public/_headers with the assets. Public JS/CSS/branding files are served directly by Cloudflare; API and explicit page routes still run through the Worker, with no automatic HTML fallback for unknown API paths.

Server now automatically removes durable request receipts, answer deduplication and response routes after RECORD_RETENTION_DAYS (default 30). Preserve any chosen value in the actual Worker configuration. Existing development receipts keep their creation dates; old interaction records without timestamps start at adoption. Reducing retention applies to remaining records and can make them immediately eligible for deletion. After deletion, old request IDs no longer deduplicate; inspect native state before retrying unknown work. Native Codex tasks and conversations are not deleted. Existing subscription/retry lifecycle cleanup is unchanged. See the version-matched bundled docs for executable steps.

v0.1.0-dev.59.1

Development build from 45201aa. Discovered only by deployments explicitly configured with RELEASE_CHANNEL=dev; stable deployments ignore this Pre-release.

Installation and update requirements

0.1.0 requires a fresh native installation from 0.0.1; no owner keys, device tokens or OAuth grants are migrated. Preserve native Codex accounts, projects and conversations. Install the Server, connect the first Codex and then connect each Personal Agent using its own access code. Updates within the 0.1.0 development series preserve the account, Worker, origin, SERVICE_ID, browser login methods and DO/KV resources; point both main and assets.directory at this release. Loaded Desktop instances automatically pick up complete first-time configuration; verify the actual owner and connection without a routine app restart. If a newly installed plugin's tool is missing, try normal host loading/refresh or a new local conversation before coordinating an app restart. Desktop updates still require refreshing every host retaining old plugin instances and verifying the actual owner version. Refresh each Personal Agent catalog when remote_catalog is true. This release uses wire 5; 0.0.1 uses wire 4. Product versions may differ; wire versions must match. Report component completion separately from link recovery.

Browser administration now uses a DotX password or passkey; Wrangler management and Personal Agent MCP OAuth remain independent. After deploying this Server, run admin.mjs setup and give the private link to the user. They choose a password or passkey directly on their Worker; no CF OAuth client or API-token copying is required. Browser setup may be deferred while installation continues through Wrangler. Preserve DeviceHub and OAuth KV. Earlier dev CF browser sessions no longer work: set up the new login once, then remove obsolete CF_OAUTH_CLIENT_ID/CF_OAUTH_CLIENT_SECRET bindings and only the CF OAuth client dedicated to that retired login. Do not recreate the DO, device identities or Personal Agent connections. Subsequent password/passkey releases preserve the saved login methods. A forgotten browser login can be recovered through admin.mjs reset-login; successful reset clears only browser credentials and sessions.

Apply the target Server template's assets.run_worker_first routing array: ["/", "!/assets/", "!/branding/*"]. Keep html_handling and not_found_handling set to "none", and deploy public/_headers with the assets. Public JS/CSS/branding files are served directly by Cloudflare; API and explicit page routes still run through the Worker, with no automatic HTML fallback for unknown API paths.

Server now automatically removes durable request receipts, answer deduplication and response routes after RECORD_RETENTION_DAYS (default 30). Preserve any chosen value in the actual Worker configuration. Existing development receipts keep their creation dates; old interaction records without timestamps start at adoption. Reducing retention applies to remaining records and can make them immediately eligible for deletion. After deletion, old request IDs no longer deduplicate; inspect native state before retrying unknown work. Native Codex tasks and conversations are not deleted. Existing subscription/retry lifecycle cleanup is unchanged. See the version-matched bundled docs for executable steps.

v0.1.0-dev.58.1

Development build from e56718d. Discovered only by deployments explicitly configured with RELEASE_CHANNEL=dev; stable deployments ignore this Pre-release.

Installation and update requirements

0.1.0 requires a fresh native installation from 0.0.1; no owner keys, device tokens or OAuth grants are migrated. Preserve native Codex accounts, projects and conversations. Install the Server, connect the first Codex and then connect each Personal Agent using its own access code. Updates within the 0.1.0 development series preserve the account, Worker, origin, SERVICE_ID, browser login methods and DO/KV resources; point both main and assets.directory at this release. Loaded Desktop instances automatically pick up complete first-time configuration; verify the actual owner and connection without a routine app restart. If a newly installed plugin's tool is missing, try normal host loading/refresh or a new local conversation before coordinating an app restart. Desktop updates still require refreshing every host retaining old plugin instances and verifying the actual owner version. Refresh each Personal Agent catalog when remote_catalog is true. This release uses wire 5; 0.0.1 uses wire 4. Product versions may differ; wire versions must match. Report component completion separately from link recovery.

Browser administration now uses a DotX password or passkey; Wrangler management and Personal Agent MCP OAuth remain independent. After deploying this Server, run admin.mjs setup and give the private link to the user. They choose a password or passkey directly on their Worker; no CF OAuth client or API-token copying is required. Browser setup may be deferred while installation continues through Wrangler. Preserve DeviceHub and OAuth KV. Earlier dev CF browser sessions no longer work: set up the new login once, then remove obsolete CF_OAUTH_CLIENT_ID/CF_OAUTH_CLIENT_SECRET bindings and only the CF OAuth client dedicated to that retired login. Do not recreate the DO, device identities or Personal Agent connections. Subsequent password/passkey releases preserve the saved login methods. A forgotten browser login can be recovered through admin.mjs reset-login; successful reset clears only browser credentials and sessions.

Apply the target Server template's assets.run_worker_first routing array: ["/", "!/assets/", "!/branding/*"]. Keep html_handling and not_found_handling set to "none", and deploy public/_headers with the assets. Public JS/CSS/branding files are served directly by Cloudflare; API and explicit page routes still run through the Worker, with no automatic HTML fallback for unknown API paths.

Server now automatically removes durable request receipts, answer deduplication and response routes after RECORD_RETENTION_DAYS (default 30). Preserve any chosen value in the actual Worker configuration. Existing development receipts keep their creation dates; old interaction records without timestamps start at adoption. Reducing retention applies to remaining records and can make them immediately eligible for deletion. After deletion, old request IDs no longer deduplicate; inspect native state before retrying unknown work. Native Codex tasks and conversations are not deleted. Existing subscription/retry lifecycle cleanup is unchanged. See the version-matched bundled docs for executable steps.

v0.1.0-dev.57.1

Development build from aae4067. Discovered only by deployments explicitly configured with RELEASE_CHANNEL=dev; stable deployments ignore this Pre-release.

Installation and update requirements

0.1.0 requires a fresh native installation from 0.0.1; no owner keys, device tokens or OAuth grants are migrated. Preserve native Codex accounts, projects and conversations. Install the Server, connect the first Codex and then connect each Personal Agent using its own access code. Updates within the 0.1.0 development series preserve the account, Worker, origin, SERVICE_ID, browser login methods and DO/KV resources; point both main and assets.directory at this release. Loaded Desktop instances automatically pick up complete first-time configuration; verify the actual owner and connection without a routine app restart. If a newly installed plugin's tool is missing, try normal host loading/refresh or a new local conversation before coordinating an app restart. Desktop updates still require refreshing every host retaining old plugin instances and verifying the actual owner version. Refresh each Personal Agent catalog when remote_catalog is true. This release uses wire 5; 0.0.1 uses wire 4. Product versions may differ; wire versions must match. Report component completion separately from link recovery.

Browser administration now uses a DotX password or passkey; Wrangler management and Personal Agent MCP OAuth remain independent. After deploying this Server, run admin.mjs setup and give the private link to the user. They choose a password or passkey directly on their Worker; no CF OAuth client or API-token copying is required. Browser setup may be deferred while installation continues through Wrangler. Preserve DeviceHub and OAuth KV. Earlier dev CF browser sessions no longer work: set up the new login once, then remove obsolete CF_OAUTH_CLIENT_ID/CF_OAUTH_CLIENT_SECRET bindings and only the CF OAuth client dedicated to that retired login. Do not recreate the DO, device identities or Personal Agent connections. Subsequent password/passkey releases preserve the saved login methods. A forgotten browser login can be recovered through admin.mjs reset-login; successful reset clears only browser credentials and sessions.

Apply the target Server template's assets.run_worker_first routing array: ["/", "!/assets/", "!/branding/*"]. Keep html_handling and not_found_handling set to "none", and deploy public/_headers with the assets. Public JS/CSS/branding files are served directly by Cloudflare; API and explicit page routes still run through the Worker, with no automatic HTML fallback for unknown API paths.

Server now automatically removes durable request receipts, answer deduplication and response routes after RECORD_RETENTION_DAYS (default 30). Preserve any chosen value in the actual Worker configuration. Existing development receipts keep their creation dates; old interaction records without timestamps start at adoption. Reducing retention applies to remaining records and can make them immediately eligible for deletion. After deletion, old request IDs no longer deduplicate; inspect native state before retrying unknown work. Native Codex tasks and conversations are not deleted. Existing subscription/retry lifecycle cleanup is unchanged. See the version-matched bundled docs for executable steps.

v0.1.0-dev.56.1

Start a fresh installation

Give your installation Agent the version-matched Agent guide. Use this Release’s Server and Desktop attachments together. The Agent should install the Server, connect the first Codex, then connect the chosen Personal Agent and verify each stage.

This build replaces the previous dev browser-login setup with password or passkey on your own Worker. No Cloudflare OAuth client or API-token copying is required for browser login. Passwords are required but have no DotX length or composition policy. Browser sessions renew on authenticated management requests and expire after 30 days of inactivity. Wrangler administration and Personal Agent MCP OAuth remain independent.

Development build from 57d6249. Discovered only by deployments explicitly configured with RELEASE_CHANNEL=dev; stable deployments ignore this Pre-release.

Installation and update requirements

0.1.0 requires a fresh native installation from 0.0.1; no owner keys, device tokens or OAuth grants are migrated. Preserve native Codex accounts, projects and conversations. Install the Server, connect the first Codex and then connect each Personal Agent using its own access code. Updates within the 0.1.0 development series preserve the account, Worker, origin, SERVICE_ID, browser login methods and DO/KV resources; point both main and assets.directory at this release. After Desktop configuration or update, refresh every loaded host MCP configuration and verify the actual owner version. Refresh each Personal Agent catalog when remote_catalog is true. This release uses wire 5; 0.0.1 uses wire 4. Product versions may differ; wire versions must match. Report component completion separately from link recovery.

Browser administration now uses a DotX password or passkey; Wrangler management and Personal Agent MCP OAuth remain independent. After deploying this Server, run admin.mjs setup and give the private link to the user. They choose a password or passkey directly on their Worker; no CF OAuth client or API-token copying is required. Browser setup may be deferred while installation continues through Wrangler. Preserve DeviceHub and OAuth KV. Earlier dev CF browser sessions no longer work: set up the new login once, then remove obsolete CF_OAUTH_CLIENT_ID/CF_OAUTH_CLIENT_SECRET bindings and only the CF OAuth client dedicated to that retired login. Do not recreate the DO, device identities or Personal Agent connections. Subsequent password/passkey releases preserve the saved login methods. A forgotten browser login can be recovered through admin.mjs reset-login; successful reset clears only browser credentials and sessions.

Apply the target Server template's assets.run_worker_first routing array: ["/", "!/assets/", "!/branding/*"]. Keep html_handling and not_found_handling set to "none", and deploy public/_headers with the assets. Public JS/CSS/branding files are served directly by Cloudflare; API and explicit page routes still run through the Worker, with no automatic HTML fallback for unknown API paths.

Server now automatically removes durable request receipts, answer deduplication and response routes after RECORD_RETENTION_DAYS (default 30). Preserve any chosen value in the actual Worker configuration. Existing development receipts keep their creation dates; old interaction records without timestamps start at adoption. Reducing retention applies to remaining records and can make them immediately eligible for deletion. After deletion, old request IDs no longer deduplicate; inspect native state before retrying unknown work. Native Codex tasks and conversations are not deleted. Existing subscription/retry lifecycle cleanup is unchanged. See the version-matched bundled docs for executable steps.

v0.1.0-dev.55.1

Development build from cb07159. Discovered only by deployments explicitly configured with RELEASE_CHANNEL=dev; stable deployments ignore this Pre-release.

Installation and update requirements

0.1.0 requires a fresh native installation from 0.0.1; no owner keys, device tokens or OAuth grants are migrated. Preserve native Codex accounts, projects and conversations. Install the Server, connect the first Codex and then connect each Personal Agent using its own access code. Updates within the 0.1.0 development series preserve the account, Worker, origin, SERVICE_ID, CF OAuth client/secret and DO/KV resources; point both main and assets.directory at this release. After Desktop configuration or update, refresh every loaded host MCP configuration and verify the actual owner version. Refresh each Personal Agent catalog when remote_catalog is true. This release uses wire 5; 0.0.1 uses wire 4. Product versions may differ; wire versions must match. Report component completion separately from link recovery.

New installations configure browser login through the Worker setup page after deployment: run admin.mjs setup, give the returned link to the user, and verify setup-status plus browser login. The page preselects OAuth Client Write; set a one-hour custom token expiry manually in Cloudflare, then paste the temporary token only into the DotX page. The Worker stores its private CF login client in DeviceHub. No CF client ID/secret handling or extra deployment is needed. Existing dev installations retain their CF_OAUTH_CLIENT_ID/CF_OAUTH_CLIENT_SECRET bindings or stored client configuration; do not reinitialize or replace their DO.

Apply the target Server template's assets.run_worker_first routing array: ["/", "!/assets/", "!/branding/*"]. Keep html_handling and not_found_handling set to "none", and deploy public/_headers with the assets. Public JS/CSS/branding files are served directly by Cloudflare; API and explicit page routes still run through the Worker, with no automatic HTML fallback for unknown API paths.

Server now automatically removes durable request receipts, answer deduplication and response routes after RECORD_RETENTION_DAYS (default 30). Preserve any chosen value in the actual Worker configuration. Existing development receipts keep their creation dates; old interaction records without timestamps start at adoption. Reducing retention applies to remaining records and can make them immediately eligible for deletion. After deletion, old request IDs no longer deduplicate; inspect native state before retrying unknown work. Native Codex tasks and conversations are not deleted. Existing subscription/retry lifecycle cleanup is unchanged. See the version-matched bundled docs for executable steps.

v0.1.0-dev.53.1

Development build from cd21410. Discovered only by deployments explicitly configured with RELEASE_CHANNEL=dev; stable deployments ignore this Pre-release.

Installation and update requirements

0.1.0 requires a fresh native installation from 0.0.1; no owner keys, device tokens or OAuth grants are migrated. Preserve native Codex accounts, projects and conversations. Install the Server, connect the first Codex and then connect each Personal Agent using its own access code. Updates within the 0.1.0 development series preserve the account, Worker, origin, SERVICE_ID, CF OAuth client/secret and DO/KV resources; point both main and assets.directory at this release. After Desktop configuration or update, refresh every loaded host MCP configuration and verify the actual owner version. Refresh each Personal Agent catalog when remote_catalog is true. This release uses wire 5; 0.0.1 uses wire 4. Product versions may differ; wire versions must match. Report component completion separately from link recovery.

Apply the target Server template's assets.run_worker_first routing array: ["/", "!/assets/", "!/branding/*"]. Keep html_handling and not_found_handling set to "none", and deploy public/_headers with the assets. Public JS/CSS/branding files are served directly by Cloudflare; API and explicit page routes still run through the Worker, with no automatic HTML fallback for unknown API paths.

Server now automatically removes durable request receipts, answer deduplication and response routes after RECORD_RETENTION_DAYS (default 30). Preserve any chosen value in the actual Worker configuration. Existing development receipts keep their creation dates; old interaction records without timestamps start at adoption. Reducing retention applies to remaining records and can make them immediately eligible for deletion. After deletion, old request IDs no longer deduplicate; inspect native state before retrying unknown work. Native Codex tasks and conversations are not deleted. Existing subscription/retry lifecycle cleanup is unchanged. See the version-matched bundled docs for executable steps.

v0.0.1

0.0.1 (2026-10-22)

Installation and availability

This is the first non-Pre-release of DotX, published for internal testing. GitHub will mark it Latest, and deployments using the default stable channel can discover it.

For a new installation, start with INSTALL.md in local Codex. Set up the first Mac and Cloudflare service with setup; add other Macs independently with join. Use the matching Desktop and Server attachments from this release. The Server attachment includes the branding assets used for ChatGPT plugin setup.

Upgrading from 0.0.1-rc.5

The runtime code and update guidance are unchanged from the verified rc.5 source. Follow the target-version Desktop update skill or Remote update skill.

• Update each Mac from the Desktop attachment and deploy the Server attachment to the existing service. Move the Worker entry point and static-assets directory together.
• Preserve existing installation identities, configuration, enrollment, OAuth authorization and stored state. Brief disconnections during activation or deployment are expected; reconcile current state without resending unknown work.
• Follow the skills for normal activation, retiring confirmed old DotX processes, waiting and rechecking. A host restart remains the final fallback.
• Refresh the existing ChatGPT plugin catalog after Server deployment, as indicated by remote_catalog=true. The coordinating agent should arrange this through an executor with permitted browser access, asking for manual help only when a concrete blocker remains.
• No data migration or configuration change is required from rc.5. Wire protocol remains 4. All three change flags are true because this is the first stable baseline, not because every component changed since rc.5.

Features

• add opt-in dev release discovery (986da52)
• expose DotX usage instructions as a tool (bb9039b)
• initialize DotX desktop and self-hosted MCP service (17f51a7)
• load MCP guidance by task goal (7659c34)
• prepare Personal Agent onboarding and product branding (965af00)
• simplify authorization pages and grant full DotX access (1b0e38e)

Bug Fixes

• clarify native activation and support RC prereleases (7f6af94)
• coordinate update permissions before delegating work (54db915)
• describe opt-in discovery in prerelease notes (0ef49d3)
• keep one active desktop connector per installation (4f8f3f9)
• link update guidance to web-readable release source (876a532)
• preserve native fetch receiver in Workers discovery (f5d1071)
• retire stale connector routes and clarify invocation guidance (7a144b2)
• scope event subscriptions to a single native turn (9810ad8)
• validate generated releases and upload correct asset types (89077d9)

v0.0.1-rc.5

0.0.1-rc.5

Release candidate for explicit installation and upgrade testing. This is a Pre-release; stable and dev discovery do not select RC builds.

Changes since rc.4

Desktop and Remote update guidance now allows time for connector loading and registration after old processes exit, with spaced checks of process state and current connections. A closed MCP handle in the executing conversation does not by itself mean the device is offline. The coordinator reconciles current state before requesting a host restart and assigns the ChatGPT catalog Refresh to an available browser-capable executor.

Upgrade requirements

• Before planning or executing this upgrade, read the target-version Remote update skill and Desktop update skill. Installed rc.4 guidance does not yet contain these corrections.
• Install the Desktop attachment on each Mac and deploy the Server attachment to the existing Cloudflare service. Keep the deployed Worker entry point and static assets from the same package. Do not create a replacement service or repeat device enrollment/OAuth.
• Brief connection interruptions during activation or deployment are expected. Preserve installation identities, configuration, authorization and existing state; reconcile current state after reconnecting instead of resending work. Follow the activation and recheck sequence in the skills; restarting the host remains the final fallback.
• Refresh the existing ChatGPT plugin catalog after Server deployment because Remote update guidance changed. Assign this webpage operation to the coordinator or a local executor with permitted browser access; report a concrete access or capability blocker before asking the user to do it.
• No data migration or configuration change is required. Wire protocol remains 4. The three release change flags remain relative to the declared stable baseline (currently none), not a diff against rc.4.

Source: f20eb6886560992077fcd29b4316fe7731515f35.