feat: add --proxy-only flag for stateless proxying#99
Merged
Conversation
…ording Proxy unmatched requests to upstream providers without writing fixtures to disk or caching them in memory. Every unmatched request always hits the real provider — useful for demos and live environments where stale recorded responses are undesirable.
commit: |
jpr5
changed the title
jpr5
added a commit
that referenced
this pull request
Jul 15, 2026
## Summary - Add `--proxy-only` CLI flag that proxies unmatched requests to upstream providers without saving fixtures to disk or caching them in memory - Every unmatched request always hits the real provider — no stale recorded responses - Matched fixtures still work normally - Adds `proxyOnly` field to `RecordConfig` type for programmatic usage ## Use case Demo/live environments where aimock sits in front of real LLM providers with local fixtures for known scenarios, but unmatched traffic should always go upstream rather than getting cached after the first call. ## Files changed - `src/types.ts` — `proxyOnly?: boolean` on `RecordConfig` - `src/cli.ts` — `--proxy-only` flag parsing and help text - `src/recorder.ts` — skip disk write + memory push when `proxyOnly` is set - `src/__tests__/proxy-only.test.ts` — 8 tests covering proxy-only and contrast with record mode ## Test plan - [x] 8 new tests covering all proxy-only behaviors - [x] All 2214 tests pass - [x] Build passes 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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
--proxy-onlyCLI flag that proxies unmatched requests to upstream providers without saving fixtures to disk or caching them in memoryproxyOnlyfield toRecordConfigtype for programmatic usageUse case
Demo/live environments where aimock sits in front of real LLM providers with local fixtures for known scenarios, but unmatched traffic should always go upstream rather than getting cached after the first call.
Files changed
src/types.ts—proxyOnly?: booleanonRecordConfigsrc/cli.ts—--proxy-onlyflag parsing and help textsrc/recorder.ts— skip disk write + memory push whenproxyOnlyis setsrc/__tests__/proxy-only.test.ts— 8 tests covering proxy-only and contrast with record modeTest plan
🤖 Generated with Claude Code