feat: ephemeral one-shot keys (Story 2.5)#131
Merged
farovictor merged 1 commit intomainfrom Apr 5, 2026
Merged
Conversation
- Add OneShot + Used fields to VirtualKey model + migration 008 - Proxy rejects one-shot keys with 401 "key already used" after first use - Key is marked used before forwarding to prevent replay on upstream error - POST /v1/keys accepts one_shot: true (pass-through via struct decode) - MCP request_key tool accepts one_shot: true argument - one_shot and used fields appear in GET /v1/keys list - 4 new tests: used-once enforcement, list visibility, regular key unaffected, MCP one-shot flag propagation - Regenerate swagger spec Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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
one_shot: truesupport toPOST /v1/keysand therequest_keyMCP toolused: truebefore the upstream request is forwarded — prevents replay even if the upstream returns an error401 {"error":"key already used"}one_shotandusedfields are visible inGET /v1/keysexpires_atsource,one_shot,usedcolumns via migrations 007 + 008Test plan
TestOneShotKeyUsedOnce— first request 200, second 401 "key already used"TestOneShotKeyAppearsInList—one_shot: truevisible in listTestRegularKeyNotAffectedByOneShotLogic— regular key usable 3× without issueTestMCPRequestKeyOneShot— MCP-issued key hasone_shot: true🤖 Generated with Claude Code