Add support for agent cloud create and agent cloud claim commands - #119
Merged
Conversation
Claimable Clouds are temporary clouds whose credentials work immediately, with media delivery restricted to an IP allow-list, disabled after ~24h unless a human claims them. `agent cloud create` provisions one and saves it as a named configuration along with the claim URL, which the server returns exactly once and cannot be looked up again. Delivery IPs are forwarded verbatim: the server owns the count, routability and CIDR rules, and rejects bad input with a 400 that does not consume creation quota. `agent cloud claim` opens (or prints) the stored claim URL. `--print` and `--json` never launch a browser, so headless and agent callers get the URL on stdout. Config metadata is carried as query params on the saved cloudinary:// URL: claim_url, expires_at, delivery_ips, account_id and cloud_email. `config -ls` gains a STATUS column and `config -s` a header flag, both showing an expiry countdown; JSON output carries raw timestamps plus claimable_cloud and expired flags. Extract parse_expiry, is_expired and expires_in_hint into utils, shared by the OAuth epoch expiry and the ISO-8601 cloud expiry. Document both commands in the README, and split Requirements into an agent path and a human path so Claimable Clouds are the documented way for an agent to get an account. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The test read row [0] and assumed it was the saved cloud. An ambient CLOUDINARY_URL adds an "(environment)" row ahead of it, which carries no expires_at, so the assertion raised KeyError. Co-Authored-By: Claude Opus 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
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.
Claimable Clouds are temporary clouds whose credentials work immediately, with media delivery restricted to an IP allow-list, disabled after ~24h unless a human claims them.
agent cloud createprovisions one and saves it as a named configuration along with the claim URL, which the server returns exactly once and cannot be looked up again. Delivery IPs are forwarded verbatim: the server owns the count, routability and CIDR rules, and rejects bad input with a 400 that does not consume creation quota.agent cloud claimopens (or prints) the stored claim URL.--printand--jsonnever launch a browser, so headless and agent callers get the URL on stdout.Config metadata is carried as query params on the saved cloudinary:// URL: claim_url, expires_at, delivery_ips, account_id and cloud_email.
config -lsgains a STATUS column andconfig -sa header flag, both showing an expiry countdown; JSON output carries raw timestamps plus claimable_cloud and expired flags.Extract parse_expiry, is_expired and expires_in_hint into utils, shared by the OAuth epoch expiry and the ISO-8601 cloud expiry.
Document both commands in the README, and split Requirements into an agent path and a human path so Claimable Clouds are the documented way for an agent to get an account.
Brief Summary of Changes
What does this PR address?
Are tests included?
Reviewer, please note:
Checklist: