Skip to content

docs: disclose AI Gateway reverse proxy accounting limits - #29727

Closed
pawbana wants to merge 2 commits into
pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9from
pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10
Closed

pawbana wants to merge 2 commits into
pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9from
pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10

Conversation

@pawbana

@pawbana pawbana commented Sep 22, 2026 •

Copy link
Copy Markdown
Collaborator

Document the unsafe reverse proxy experiment's missing token, model, content, and spend accounting, along with budget/backfill limitations, unsupported Bedrock routes, and actor-header restrictions. Explain that start recording must succeed before forwarding and end recording is asynchronous and best effort. Keep CLI help, configuration references, and generated API descriptions consistent.

Depends on #29726, which activates forwarding. This PR contains only disclosures, option descriptions, and generated outputs. The restack also corrects the AWS-authentication disclosure and distinguishes custom actor-header names from stripped actor-prefixed headers.

Scope and implementation decisions

Disclosures follow the synchronous-start lifecycle in #29726. Usage and spend are not backfilled; blank model or usage values are not evidence of zero provider spend. Turning off the experiment requires restarting every affected control plane replica and standalone gateway. No forwarding, recorder-schema, or identity changes belong to this slice.

The prerequisite stack is shared body capture (#30398) → provider wire forwarding and Router-owned transports (#30399) → existing key-pool failover (#30400) → terminal response observation (#30226) → lifecycle recording and activation (#29726). Validation and the passthrough nil-body sibling (#30401) are unchanged.

Generated by Coder Agents on behalf of @pawbana.

@linear-code

linear-code Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

AIGOV-615

AIGOV-791

@github-actions

github-actions Bot commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

Docs preview

Check off each page once it's been reviewed. If a page changes in a later push, its checkbox clears automatically so it gets a fresh look. Pages not yet wired into the docs navigation aren't listed here.

@pawbana pawbana removed their assignment Sep 22, 2026
@pawbana
pawbana added this pull request to stack #29736 September 22, 2026 16:14
@pawbana
pawbana removed this pull request from stack #29736 September 24, 2026 17:36
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch 7 times, most recently from fd534b6 to a5d87a9 Compare October 1, 2026 07:07
@pawbana pawbana changed the title feat: activate recorded AI Gateway reverse proxy routing docs: disclose AI Gateway reverse proxy accounting limits Oct 1, 2026
@pawbana

pawbana commented Oct 1, 2026

Copy link
Copy Markdown
Collaborator Author

/coder-agents-review

@coder-agents-review

coder-agents-review Bot commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Chat: Review posted | View chat
Requested: 2026-10-01 09:07 UTC by @pawbana

Review history
  • R1 (2026-10-01): 9 reviewers, 2 P2, 7 P3, 3 P4, COMMENT. Review
  • R2 (2026-10-01): 10 reviewers, 2 P2, 8 P3, 7 P4, COMMENT. Review

deep-review v0.13.0 | Round 2 | af4048c..0687c9e

Last posted: Round 2, 17 findings (2 P2, 8 P3, 7 P4), COMMENT. Review

Finding inventory

Findings

# Sev Status Location Summary Round Reviewer Posted
CRF-1 P3 Author fixed (d641f33) codersdk/deployment.go:5512 Experiment comment drops the MCP-configured fallback condition R1 Netero Yes
CRF-2 P3 Author fixed (d641f33) codersdk/deployment.go:2108 "reverse proxy mode" is undefined and not mapped to the experiment name R1 Netero Yes
CRF-3 P2 Author fixed (d641f33) codersdk/deployment.go:2108 "No effect" hides that proxy mode forwards client values at custom actor-header destinations R1 Pariston, Pen Botter, Mafuuu, Gon, Leorio, Razor, Mafu-san, Knov Yes
CRF-4 P2 Author fixed (d641f33); panel re-raised R2 docs/ai-coder/ai-gateway/monitoring.md:17 Provider disclosure omits AWS SigV4 Anthropic/Claude Platform 501s and Bedrock 404 outcome R1 Pen Botter P2, Leorio P3 Yes
CRF-5 P3 Author fixed (d641f33) docs/ai-coder/ai-gateway/monitoring.md:13 Warnings omit that MCP config keeps interception mode and how to see the active mode R1 Leorio, Pen Botter Yes
CRF-6 P3 Author fixed (d641f33) docs/ai-coder/ai-gateway/cost-controls.md:27 Experiment is read per process; restart instruction and audit path cover one process R1 Knov P3, Mafuuu P4 Yes
CRF-7 P3 Author fixed (d641f33) docs/ai-coder/ai-gateway/monitoring.md:13 "Records start and end" is false when the start record fails; request is still forwarded R1 Mafuuu Yes
CRF-8 P3 Author fixed (d641f33) docs/ai-coder/ai-gateway/cost-controls.md:22 "Bridged requests" and "interception mode" are undefined in user docs R1 Gon P3, Pen Botter P3, Leorio P4 Yes
CRF-9 P4 Author fixed (d641f33) docs/ai-coder/agents/platform-controls/spend-management.md:12 Spend-management warning scopes the limit to all routed traffic, not bridged requests R1 Pen Botter Yes
CRF-10 P4 Author fixed (d641f33) docs/ai-coder/ai-gateway/monitoring.md:16 Budget sentence duplicated from cost-controls.md R1 Pariston Yes
CRF-11 P4 Author fixed (d641f33); panel re-raised R2 codersdk/deployment.go:5512 Experiment comment repeats itself and uses undefined "unsafe" R1 Gon P2 Yes
CRF-12 P3 Author contested; panel closed R2 (1/1 accept) codersdk/deployment.go:2108 All 21 completed CI jobs fail at head with no explanation R1 Mafu-san P2 Yes
CRF-13 OOS Out of scope (body) aibridge/x/proxy/handler.go:100 Forwarding does not strip client values at configured actor-header destinations R1 Pariston, Pen Botter, Mafuuu, Leorio, Razor, Knov No
CRF-14 OOS Out of scope (body) aibridge/x/proxy/handler.go:153 Proxy mode forwards requests whose RecordInterception failed R1 Mafuuu No
CRF-15 OOS Out of scope (body) aibridge/x/proxy/handler.go:57 Forwarding never applies Claude Platform transport (workspace header) R1 Pen Botter No
CRF-16 OOS Out of scope (body) aibridge/x/proxy/router.go:70 Bedrock bridged routes return bare 404 with no cause R1 Leorio No
CRF-17 OOS Out of scope (body) aibridge/passthrough.go:82 Passthrough routes forward client X-AI-Bridge-Actor* headers in both modes R1 Leorio No
CRF-18 Note Dropped by orchestrator (merge commit subject does not reach main under squash merge; asks for no change) 9ce714f Merge commit subject is stack-specific R1 Leorio No
CRF-19 P4 Open codersdk/deployment.go:2109 CRF-3 fix says configured destinations are forwarded unchanged; default X-AI-Bridge-Actor destinations are stripped R2 Netero Yes
CRF-20 P4 Open codersdk/deployment.go:5514 "budgets cannot limit them" contradicts the budget check that still runs R2 Netero Yes
CRF-21 P3 Open docs/ai-coder/ai-gateway/monitoring.md:22 501 bullet cites removed CODER_AI_GATEWAY_BEDROCK_* settings R2 Leorio Yes
CRF-22 P4 Open docs/ai-coder/ai-gateway/cost-controls.md:22 "disables usage accounting" is undefined and contradicted by what the warning says is still recorded R2 Gon Yes
CRF-23 P4 Open docs/ai-coder/ai-gateway/monitoring.md:15 Recording limits and enforcement instruction duplicated across the three callouts R2 Zoro Yes
CRF-24 OOS Out of scope (body) docs/ai-coder/ai-gateway/reference.md:86 Actor-header reference section says values come from the account, false in reverse proxy mode R2 Zoro P3, Knov No

Contested and acknowledged

CRF-12 (P3, codersdk/deployment.go:2108) - All 21 completed CI jobs fail at head with no explanation

  • Finding: All 21 completed CI jobs were red at round 1 head 9ce714f, including gen, lint-docs, and changes, with no explanation in the PR; asked the author to find and fix the cause or explain it.
  • Author defense: The red entries came from superseded cancelled run 36835725519; run 36835726001 on the reviewed head completed successfully. Final-head CI is running after the new push.

CRF-12 panel closure (R2, 1/1)

  • Panel closure (R2, 1/1): Mafu-san, the agent that raised it, queried the public Actions API: run 36835726001 at head 9ce714f concluded success, run 36835725519 at the same head concluded cancelled, and at head 0687c9e the ci, docs-preview, and flake-go runs concluded success. No check failed on any reviewed head.

Law analysis

Not run. Effective additions 36 (threshold 1000).

Round log

Round 1

Round type: round 1, full panel (focused docs PR with one Go file). Panel: ging-go (trigger: .go changed), pen-botter (documentation), pariston, mafuuu (core), gon, leorio (floor), razor, mafu-san (agent-authored), knov (wildcard). Netero first pass: 2 P3, no P0.

Cross-check: the actor-header disclosure (CRF-3) converged across 8 reviewers; Pen Botter, Mafuuu, Leorio, Razor, Knov reproduced it with scratch tests; orchestrator confirmed prepareForwardingHeaders calls only PrepareClientHeaders (handler.go:100) while destination deletion lives in BuildUpstreamHeaders (headers.go:244). Kept at P2: the root fix is in aibridge/x/proxy, which this PR does not change, so it is listed out of scope; the in-PR consequence is a security-relevant disclosure that reads as harmless. Leorio's Bedrock 404 finding merged into CRF-4. Mafuuu's restart P4 merged into CRF-6 at Knov's P3. Leorio's P4 term finding merged into CRF-8.

Downgrades: CRF-11 Gon P2 to P4. Keep-argument: the comment is exported to swagger x-enum-comments, so redundant and undefined wording ships in the API contract. Downgrade reason: no reader misreads behavior from the redundancy; the behavioral gap at that line is CRF-1. CRF-12 Mafu-san P2 to P3. Keep-argument: gen and lint-docs back the PR's consistency claim and are red. Downgrade reason: Netero ran clidocgen, the golden tests, and markdownlint locally and all passed, and the changes path-filter job also failed, which supports a CI setup or base-branch cause rather than this content; logs unreadable (gh 401).

Reviewed against dfe3d87..9ce714f.

Round 2

Fix round (same 13 files, no renames or signature changes, effective additions +27). Churn guard PROCEED: CRF-1 to CRF-11 author fixed in d641f33, CRF-12 contested. Netero (advisory): CRF-19, CRF-20 new P4. Panel: mafu-san (dispute check-in, same agent), gon, leorio (floor; comments and doc text touched), pen-botter, mafuuu, pariston, razor, knov (raised CRF-3/4/6/7 whose text changed; same agents), ging-go (.go changed; same agent), zoro (wildcard, new agent).

Cross-check: CRF-12 closed 1/1. CRF-4 re-raised by Pen Botter with a reproduction (Claude Platform BYOK request reached upstream with an empty Anthropic-Workspace-Id). CRF-11 re-raised by Gon ("Unsafe:" and restated identifier kept; new clause is CRF-20). Leorio CRF-21 verified by orchestrator: cli/aibridged.go constructs the anthropic provider with a nil Bedrock config and no non-test Go file references AI_GATEWAY_BEDROCK; the round 1 CRF-4 comment had suggested naming those settings. Zoro's reference.md finding moved to out of scope: the file is not in the diff, Knov independently listed it as out of scope. Verified fixed: CRF-1, CRF-2, CRF-3 (residual is CRF-19), CRF-5 to CRF-10.

Reviewed against af4048c..0687c9e.

About deep-review

CRF = Coder Review Finding (P0-P4, Nit, Note)

Reviewer Focus
Bisky tests
Chopper ops/errors
Churn-guard change verification
Ging language modernization
Gon naming
Hisoka edge cases
Killua perf
Kite change integrity
Knov contracts
Knuckle SQL
Komugi flake/determinism
Kurapika security
Law decomposition
Leorio docs
Luffy product
Mafu-san process
Mafuuu contracts
Melody dispatch/pairing
Meruem structural
Nami frontend
Netero mechanical checks
Pariston premise testing
Pen-botter product gaps
Razor verification
Robin duplication
Ryosuke Go arch
Takumi concurrency
Zoro shape

🤖 Managed by Coder Agents.

@coder-agents-review coder-agents-review Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR adds operator warnings and option-text disclosures for the ai-gateway-reverse-proxy experiment; 2 P2, 6 P3, 3 P4. The budget, restart, Bedrock routing, and lifecycle-only recording claims match the code at head; the gaps are what the warnings leave out.

Out of scope (needs a ticket or explicit acceptance by a human):

  • aibridge/x/proxy/handler.go:100: forwarding does not delete client values at configured actor-header destinations, so with the experiment on, an upstream proxy that trusts those headers receives a client-chosen identity.
  • aibridge/x/proxy/handler.go:153: proxy mode forwards a bridged request even when RecordInterception fails, while interception mode returns 500 (aibridge/bridge.go:240-243), so a recorder outage produces unrecorded provider traffic.
  • aibridge/x/proxy/handler.go:57: the forwarding handler never installs the Claude Platform transport that sets Anthropic-Workspace-Id, so Claude Platform BYOK or pooled-key requests are likely sent without it (unverified against AWS).
  • aibridge/x/proxy/router.go:70: Bedrock bridged routes answer with Go's bare 404 page not found, which gives the client no cause to act on.
  • aibridge/passthrough.go:82: passthrough routes forward client X-AI-Bridge-Actor* headers in both modes, so "Client headers starting with X-AI-Bridge-Actor are always removed" is false for those routes.

🤖 This review was automatically generated with Coder Agents.

Comment thread codersdk/deployment.go Resolved
Comment thread codersdk/deployment.go Resolved
Comment thread codersdk/deployment.go Resolved
Comment thread docs/ai-coder/ai-gateway/monitoring.md Resolved
Comment thread docs/ai-coder/ai-gateway/monitoring.md Resolved
Comment thread docs/ai-coder/ai-gateway/monitoring.md Resolved
Comment thread codersdk/deployment.go Resolved
Comment thread codersdk/deployment.go Resolved
@pawbana

pawbana commented Oct 1, 2026

Copy link
Copy Markdown
Collaborator Author

/coder-agents-review

@coder-agents-review coder-agents-review Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Round 2 of the reverse proxy disclosure review: 1 P2, 1 P3, and 5 P4 open. The fixes for the MCP condition, the experiment name, the actor-header forwarding disclosure, per-process mode selection, best-effort recording, route terminology, spend scope, and the duplicated budget sentence match the code at 0687c9e331. The CI finding is closed: run 36835726001 at the round 1 head succeeded, and the red jobs came from the cancelled run 36835725519. The Claude Platform provider bullet is reopened, and the experiment comment cleanup is incomplete.

Out of scope (needs a ticket or explicit acceptance by a human):

  • docs/ai-coder/ai-gateway/reference.md:86: the actor-header forwarding section says AI Gateway uses account values, not client-supplied headers, which is false in reverse proxy mode for custom destination names, and setup.md:125 sends operators there without any link to the reverse proxy warning.
  • aibridge/x/proxy/handler.go:100: forwarding still does not delete client values at configured actor-header destinations (unchanged from round 1).
  • aibridge/x/proxy/handler.go:57: the forwarding handler still does not apply the Claude Platform transport, so intercepted requests carry no Anthropic-Workspace-Id (unchanged from round 1).

🤖 This review was automatically generated with Coder Agents.

Comment thread codersdk/deployment.go Outdated
"Client headers starting with X-AI-Bridge-Actor are always removed.",
"Client headers starting with X-AI-Bridge-Actor are always removed. " +
"When the ai-gateway-reverse-proxy experiment selects reverse proxy mode, this option has no effect on intercepted routes: " +
"AI Gateway adds no actor headers and forwards client-supplied values at configured actor-header destinations unchanged, " +

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P4 [CRF-19] "forwards client-supplied values at configured actor-header destinations unchanged" is false for the default destinations. (Netero)

The defaults are X-AI-Bridge-Actor-ID and X-AI-Bridge-Actor-Metadata-Username (codersdk/deployment.go:2078, :2088), and PrepareClientHeaders deletes every X-AI-Bridge-Actor* header (aibridge/headers/headers.go:215-219). Only custom names outside that prefix pass through, which is what monitoring.md already says. Use "custom actor-header destinations that don't start with X-AI-Bridge-Actor".

🤖

Comment thread codersdk/deployment.go
ExperimentWorkspaceCapableLicensing Experiment = "workspace-capable-licensing" // Counts only users holding the workspace-create permission toward the license seat limit.
ExperimentAIGatewaySeatExclusion Experiment = "ai-gateway-seat-exclusion" // Excludes AI Gateway (AI Bridge) usage from AI Governance seat consumption.
ExperimentAIGatewayReverseProxy Experiment = "ai-gateway-reverse-proxy" // Uses stateless reverse proxy routing when MCP injection is not configured.
ExperimentAIGatewayReverseProxy Experiment = "ai-gateway-reverse-proxy" // Unsafe: when no MCP servers are configured, uses reverse proxy routing that records no token usage or spend for intercepted routes, so budgets cannot limit them.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P4 [CRF-20] "so budgets cannot limit them" contradicts the budget check that still runs in reverse proxy mode. (Netero)

coderd/aibridged/http.go:165-179 calls IsBudgetExceeded and returns 403 before routing, so a user already over budget from other traffic is still refused; cost-controls.md says this correctly. This text ships in swagger x-enum-comments. Say these requests add no spend toward budgets, or drop the clause.

🤖

Comment thread docs/ai-coder/ai-gateway/monitoring.md Outdated
> Reverse proxy mode also changes how intercepted routes behave:
>
> - Requests to Amazon Bedrock providers return `404 page not found`.
> - Requests to Anthropic providers that would authenticate with AWS credentials, such as Claude Platform for AWS or the `CODER_AI_GATEWAY_BEDROCK_*` settings, return `501 Not Implemented`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3 [CRF-21] The 501 bullet names "the CODER_AI_GATEWAY_BEDROCK_* settings" as an AWS credential source, but those settings no longer configure any provider. (Leorio)

providers.md:22-23 says leftover provider environment variables are ignored and lists the CODER_AI_GATEWAY_BEDROCK_* variables for removal, and cli/aibridged.go builds the anthropic provider with a nil Bedrock config; no non-test Go file references AI_GATEWAY_BEDROCK. An operator with those variables still set reads the bullet as saying they are active. Name only Claude Platform for AWS here; the round 1 comment on this bullet suggested the removed settings, which was wrong.

🤖

- AI Gateway [enabled and configured](./setup.md) with at least one provider.

> [!WARNING]
> The unsafe `ai-gateway-reverse-proxy` experiment disables usage accounting for [requests to intercepted routes](./reference.md#supported-apis).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P4 [CRF-22] "disables usage accounting" is undefined, and the same warning then lists what is still recorded and checked. (Gon)

Lines 26 and 29 say start and end are still recorded and budget checks still include other spend, so a reader of line 22 cannot tell what stops. Name it, matching monitoring.md:15: "doesn't record token usage or accrue spend for requests to intercepted routes".

🤖

Comment thread docs/ai-coder/ai-gateway/monitoring.md Outdated
> [!WARNING]
> The unsafe `ai-gateway-reverse-proxy` experiment switches an AI Gateway process to reverse proxy mode when no MCP servers are configured.
> [AI Governance cost control](./cost-controls.md) explains when the experiment takes effect, how to confirm the mode, and how to turn it off.
> In reverse proxy mode, AI Gateway makes a best-effort record of only when each request to an intercepted route starts and ends.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P4 [CRF-23] The recording limits are written out twice (cost-controls.md:26-28 and monitoring.md:15-17), and the enforcement instruction is copied from cost-controls.md:30 to spend-management.md:14. (Zoro)

The code says model and token accounting are "not yet supported" (coderd/aibridged/aibridged.go:267), so this text is expected to change, and each change needs the same edit in two or three callouts. Keep the full description in cost-controls.md and keep only the page-specific consequence on the other two pages, with the existing link.

🤖

@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch from 0687c9e to 5f41412 Compare October 2, 2026 20:07
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch 2 times, most recently from 322862c to fc5048e Compare October 5, 2026 09:15
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch from 5f41412 to 69ebfc0 Compare October 5, 2026 09:15
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch from fc5048e to 7c37e31 Compare October 5, 2026 20:03
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch 2 times, most recently from 6a95d01 to e1fe6a1 Compare October 6, 2026 09:22
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch from 7c37e31 to e8e5a1f Compare October 6, 2026 09:22
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch from 998377f to fdb903b Compare November 3, 2026 10:47
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch from 79d997a to 609c5f7 Compare November 3, 2026 10:47
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch from fdb903b to c6f166c Compare November 3, 2026 11:19
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch 2 times, most recently from 6a99493 to 1ecb969 Compare November 3, 2026 13:42
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch 2 times, most recently from 1e82141 to f646a8e Compare November 3, 2026 14:11
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch from 1ecb969 to cc8820d Compare November 3, 2026 14:11
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch from f646a8e to e7a7633 Compare November 3, 2026 14:47
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch 2 times, most recently from 1807aff to 7f45457 Compare November 3, 2026 15:13
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch from e7a7633 to e2dae58 Compare November 3, 2026 15:13
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch from 7f45457 to 2c38889 Compare November 3, 2026 15:56
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch 2 times, most recently from 00195a8 to cabb446 Compare November 4, 2026 13:04
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch 2 times, most recently from 1aa60d0 to 6df3d59 Compare November 4, 2026 14:01
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch 2 times, most recently from 3d1ec95 to a071803 Compare November 4, 2026 14:08
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch 2 times, most recently from 8673318 to 8dfba0e Compare November 6, 2026 12:47
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch 2 times, most recently from bfb19c7 to e907262 Compare November 6, 2026 12:52
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch from 8dfba0e to 8b0c48b Compare November 6, 2026 12:53
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch from e907262 to e580bd7 Compare November 9, 2026 09:29
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10 branch 2 times, most recently from 7b69d45 to cbcb84b Compare November 9, 2026 10:57
@pawbana
pawbana force-pushed the pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-9 branch from e580bd7 to 4892f12 Compare November 9, 2026 10:57
…ecycle-and-key-9' into pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-10
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