Skip to content

refactor(api-rs): stop injecting tool placeholder env vars into sandboxes#534

Open
mslipper wants to merge 1 commit into
mainfrom
refactor/drop-tool-placeholder-env
Open

refactor(api-rs): stop injecting tool placeholder env vars into sandboxes#534
mslipper wants to merge 1 commit into
mainfrom
refactor/drop-tool-placeholder-env

Conversation

@mslipper

Copy link
Copy Markdown
Collaborator

Tool-fragment secrets no longer contribute NAME=NAME placeholder env vars to sandbox or workflow-host env. They were redundant: the SDK's StubBackend returns the key name when the env var is absent, which is exactly the placeholder value iron-proxy matches on, and the cloudwatch tool already signs with embedded throwaway SigV4 credentials so the aws_auth env seeding was dead weight. Placeholder env now comes only from the infra/harness fragments, whose consumers (codex, claude-code, git/gh, harness CLIs) read credentials directly from the environment.

Also fixes the docsend and archiver browser-use clients, which rejected the stub key name and re-read the env var — they would have returned an empty key once the env var disappeared. They now trust the stub, which the proxy swaps in the query string.

…oxes

Tool secrets never needed NAME=NAME env vars: the SDK's StubBackend
already returns the key name iron-proxy matches on, and the cloudwatch
tool embeds its own throwaway SigV4 credentials for boto3. Sandbox
placeholder env now comes from the infra/harness fragments only, whose
consumers (codex, claude, git/gh) read credentials straight from the
environment. The docsend/archiver browser-use clients drop their env
fallback that rejected the stub and would have returned an empty key.
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