Skip to content

fix(agent): don't require an API key for agent docker commands - #64

Merged
radim10 merged 1 commit into
masterfrom
fix/agent-docker-no-api-key
Oct 9, 2026
Merged

radim10 merged 1 commit into
masterfrom
fix/agent-docker-no-api-key

Conversation

@radim10

@radim10 radim10 commented Oct 9, 2026

Copy link
Copy Markdown
Member

Summary

  • agent docker build asked for a Stashbase API key even though it only builds a local image. The same was true of agent docker status, cleanup, doctor and shell: AgentSubcommand::Docker was missing from requires_api_key, so it fell through to the default. All five only touch local Docker resources; build --profile reads a local profile.
  • Found on a fresh Linux VM with an egress-only profile: agent run worked without a key, but the sandbox image it needs couldn't be built.

Test plan

  • Unit test: all five agent docker subcommands (and build --profile) don't require an API key
  • cargo fmt --check and full cargo test pass
  • Checked by hand on a Linux (aarch64) VM with no key: stashbase agent docker build runs instead of failing with "API key is required"

`agent docker build`, `status`, `cleanup`, `doctor` and `shell` only
touch local Docker resources (and `build --profile` reads a local
profile), but they fell through to the default and asked for a
Stashbase API key. On a machine with no key, such as a fresh Linux box
running an egress-only profile, the sandbox image couldn't be built even
though `agent run` itself works without one.
@radim10 radim10 self-assigned this Oct 9, 2026
@radim10
radim10 merged commit 7670d56 into master Oct 9, 2026
3 checks passed
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