Skip to content

fix: x402 fetch falls back to local signer config#21

Merged
PancheI merged 1 commit intomainfrom
fix/x402-fetch-read-local-signer-config
Mar 27, 2026
Merged

fix: x402 fetch falls back to local signer config#21
PancheI merged 1 commit intomainfrom
fix/x402-fetch-read-local-signer-config

Conversation

@PancheI
Copy link
Copy Markdown
Contributor

@PancheI PancheI commented Mar 27, 2026

Summary

  • agenta sub x402 fetch required AGENTA_API_SECRET and AGENTA_API_KEY env vars, even though the secret was already saved in ~/.agenta/signers/ from agenta sub create
  • SignerManager.getConfig() now checks env vars first (MCP/CI), then falls back to local signer config (CLI)
  • Matches how every other sub command already works (send, status, etc.)

Test plan

  • All existing tests pass (29 passed)
  • agenta sub x402 fetch <url> works without env vars (reads from ~/.agenta/signers/)
  • MCP tools still work with env vars set in MCP host config

SignerManager only read from env vars (AGENTA_API_SECRET, AGENTA_API_KEY),
which meant `agenta sub x402 fetch` failed unless env vars were set —
even though the secret was already saved in ~/.agenta/signers/.

Now: env vars take priority (for MCP/CI), local signer config is the
fallback (for CLI users). Matches how every other sub command works.
@PancheI PancheI merged commit 77678e5 into main Mar 27, 2026
1 check passed
@PancheI PancheI deleted the fix/x402-fetch-read-local-signer-config branch March 27, 2026 17:25
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