Skip to content

fix(deploy): forbid deploy_files fallback and blind retry on upload failure - #27

Merged
gp42-ops merged 1 commit into
mainfrom
guardrails
May 13, 2026
Merged

gp42-ops merged 1 commit into
mainfrom
guardrails

Conversation

@gp42-ops

Copy link
Copy Markdown
Member

When a deploy_create_upload PUT fails with a network/DNS/sandbox/proxy error, the agent must not fall back to deploy_files (whose payload cap is by definition exceeded) and must not retry the PUT blindly. It must stop, surface the per-sandbox allowlist snippet, and retry only after the user confirms the egress rule. Adds the guardrail in both the deploy_create_upload tool description and the cross-tool SERVER_INSTRUCTIONS "Deploying content" section so the agent reads it before picking a deploy tool.

…UT failure

When a deploy_create_upload PUT fails with a network/DNS/sandbox/proxy
error, the agent must not fall back to deploy_files (whose payload cap
is by definition exceeded) and must not retry the PUT blindly. It must
stop, surface the per-sandbox allowlist snippet, and retry only after
the user confirms the egress rule. Adds the guardrail in both the
deploy_create_upload tool description and the cross-tool SERVER_INSTRUCTIONS
"Deploying content" section so the agent reads it before picking a
deploy tool.
@gp42-ops
gp42-ops merged commit c700e60 into main May 13, 2026
6 checks passed
@gp42-ops
gp42-ops deleted the guardrails branch May 13, 2026 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant