Repository navigation
Align Data Use and Object Store docs with Terms section 2.6 - #2763
Merged
AlexCatarino merged 1 commit intoOct 8, 2026
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the Data Use page, the data-export skill, the Object Store introduction and download pages, and the Get Object Store File API description in line with section 2.6 of the Terms of Service.
The main correction: Data Use called saving data to the Object Store an export. Section 2.6(b) allows storing and caching data in the cloud, and only downloading or otherwise removing it counts as an export. Data Use also now covers the termination penalty, the full list of extraction methods, and agent responsibility.
Test plan
bundle-skills.pybuilds without errors🤖 Generated with Claude Code