fix: x402 fetch falls back to local signer config#21
Merged
Conversation
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.
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.
Summary
agenta sub x402 fetchrequiredAGENTA_API_SECRETandAGENTA_API_KEYenv vars, even though the secret was already saved in~/.agenta/signers/fromagenta sub createSignerManager.getConfig()now checks env vars first (MCP/CI), then falls back to local signer config (CLI)subcommand already works (send, status, etc.)Test plan
agenta sub x402 fetch <url>works without env vars (reads from~/.agenta/signers/)