Personal skill updates fail to save in ChatGPT Work (HTTP 500)

Summary

Updating an existing personal skill in ChatGPT Work succeeds locally and passes validation, but saving and synchronization repeatedly fail with HTTP 500. The remote skill remains unchanged.

Environment

• Product: ChatGPT Work
• Client: ChatGPT Android app
• Date: August 22, 2026
• Time zone: Asia/Muscat
• Skill type: Existing personal skill

Steps to reproduce

1. Update an existing personal skill.
2. Validate the skill successfully.
3. Attempt to save and synchronize the update.
4. Wait approximately 30–40 seconds.

Actual behavior

The save fails repeatedly with errors similar to:

RPC failed; HTTP 500
Unexpected disconnect while reading sideband packet
The remote end hung up unexpectedly

Verification shows that the remote skill remains on the previous version. When the skill is reloaded, the unsynchronized update is lost.

Expected behavior

The validated update should be saved to the user’s personal Skills and remain available across conversations.

Additional information

• The skill validation completes successfully.
• No permission-denied error is returned.
• No version conflict is reported.
• The update is small: three files with approximately 14 added lines.
• The issue was reproduced across multiple save attempts.

No repository file, test, or entry point is identified in the issue. Start by reproducing the save and synchronization flow for an existing personal skill on the Android client, then trace the HTTP 500 and disconnect logs; done means the validated three-file update saves remotely and remains available after reload.