fix(proxy): traceparent/baggage fallback must not override caller metadata by devin-ai-integration[bot] · Pull Request #43688 · BerriAI/litellm

devin-ai-integration · 2026-09-29T09:01:37Z

REVIEWER MUST KNOW BEFORE APPROVING

Review loop converged at 250b1a50d2: Greptile 5/5 with no findings (the P1 audit-cell finding fixed in 6b4e3198cf, the P2 comment finding in 250b1a50d2), Bugbot clean, no veria on this repo, all review threads resolved
Follow-up fix 99cf509980 repairs three P2 regressions the first cut introduced versus the merge base, found by a fresh base-vs-head validation run on 2026-10-04: equal ids in headers and metadata now stamp the root ids again (spend session had become a fresh uuid4 per call), a non-string metadata.session_id no longer suppresses the baggage fallback (sandbox-reuse consumers need a str), and a usable caller session on Responses/Messages now lands on the root session field instead of leaving it unset. All steering tests from the first cut still pass
Carries @fandujar's fix from fix(proxy): traceparent/baggage fallback must not override caller metadata #43020 unchanged (their 6 commits keep their authorship), plus a merge of main, test-only commits (incl. the audit cells below), and one follow-up fix so missing_session_id: generate on Responses and Messages derives the session from the caller's metadata.trace_id (found by Greptile, confirmed live)
Moved to an internal litellm_ branch so the CircleCI integration shards run on it; fix(proxy): traceparent/baggage fallback must not override caller metadata #43020 gets closed as superseded with a pointer here
A caller that sets metadata.trace_id / metadata.session_id now keeps them over traceparent / baggage: intended, it is the ticket, but it changes which id wins for those callers

TLDR

Problem this solves:

An explicit metadata.trace_id gets replaced by the traceparent header's trace id
Same for metadata.session_id and the baggage header, on chat, Responses and Messages
With missing_session_id: reject, a Responses or Messages call with metadata.session_id gets a 400

How it solves it:

The header fallback only runs per field when the caller left that field empty
On Responses and Messages, ids the proxy promotes from metadata count as caller set
With missing_session_id: generate, a Responses or Messages call that only sets metadata.trace_id gets that trace as its session id, same as chat, instead of a fresh uuid per call
New integration test drives a real proxy against a scripted upstream and a local Langfuse sink

Intentional product change: callers who send their own trace or session id through metadata now see those in Langfuse, spend logs and session-based routing instead of the W3C header ids

User Flow

Before: a caller behind a load balancer that injects W3C trace headers loses the session id they set

They send POST https://litellm-domain/v1/chat/completions (or /v1/responses, /v1/messages) with "metadata": {"trace_id": "my-trace-id", "session_id": "my-session-id"}
The load balancer adds traceparent and baggage: session.id=baggage-session-42, and the call comes back 200
In Langfuse the call sits under the header's 32 hex trace id in session baggage-session-42, not theirs
With missing_session_id: reject, the same /v1/responses or /v1/messages call without baggage comes back 400 "Request has no session id"

After: the same requests keep the ids the caller chose

They send the same POST https://litellm-domain/v1/chat/completions (or /v1/responses, /v1/messages) with the same metadata
The load balancer adds the same headers, and the call comes back 200
In Langfuse the call sits in session my-session-id under the trace for my-trace-id
With missing_session_id: reject, the /v1/responses or /v1/messages call without baggage comes back 200; a call with no session id anywhere is still 400

Relevant issues

Supersedes #43020 (fix by @fandujar)

Affected release

Regression in v1.98.0, where #34418 added the traceparent / baggage fallback without checking caller metadata. Confirmed live on v1.97.1, v1.98.0 and this head, see Regression check below

Linear ticket

Resolves LIT-8561

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

I have added meaningful tests
The handful of test files covering my change pass locally, e.g. uv run pytest tests/unit/<your_test_file>.py -v. Leave the suites (make test-unit-*, make test-unit) to CI: it finishes in ~15 minutes where a laptop takes an hour or more
My PR passes all required CI/CD checks (e.g., lint, schema.d.ts sync check, etc.)
My PR's scope is as isolated as possible; it only solves 1 specific problem
I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review (Greptile reviews automatically once the PR is opened; only comment @greptileai to re-request a review after pushing changes)

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

Screenshots / Proof of Fix

Latest run at head 250b1a50d2 (audit pass, 2026-10-04). Real OpenAI gpt-4o-mini on every call, real Postgres per proxy, real Redis, Langfuse OTLP export into a local wire-faithful OTLP recorder sink (disclosed substitute for a cloud Langfuse: same OTLP/HTTP protocol, records every exported span). Four proxies from the tip: default policy with request_correlation_in_logs: true, correlation off, missing_session_id: generate, and missing_session_id: reject. Spend rows are read back per request id; OTLP spans per session attribute.

Before (`4d3940c`, prior head; the merge base `85dc7cb` already behaved like After)

equal ids in headers and metadata (chat)

curl /v1/chat/completions with traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-... + baggage: session.id=matching-session-42 and "metadata":{"trace_id":"4bf92f3577b34da6a3ce929d0e0e4736","session_id":"matching-session-42"}
HTTP 200; pre-call probe: root litellm_trace_id=None, root litellm_session_id=None
Spend log session: a fresh uuid4 on every call (merge base and the fix below: 4bf92f3577b34da6a3ce929d0e0e4736)

non-string metadata session_id with baggage (chat)

Same curl with baggage: session.id=header-session-42 and "metadata":{"session_id":4815162342}
HTTP 200; probe: root litellm_session_id=None (merge base: header-session-42), metadata.session_id stays the int

header-free generate on /v1/responses (missing_session_id: generate)

curl /v1/responses with no trace headers, body "litellm_trace_id":"root-trace-42","metadata":{"session_id":"caller-session-42"}
HTTP 200; probe: root litellm_session_id=None (merge base and the fix: set)

After (`250b1a5`)

equal ids in headers and metadata (chat, and /v1/responses)

Same curls as Before
HTTP 200; spend log session 4bf92f3577b34da6a3ce929d0e0e4736 on both endpoints, byte-identical to the merge-base legs; the header-only control matches on all sides; OTLP span trace 4bf92f35..., session matching-session-42

non-string metadata session_id with baggage (chat; also list, bool, nested object in unit tests)

Same curl as Before
HTTP 200; spend session 4bf92f35... (trace preferred with correlation on), OTLP span session baggage-session-audit - the baggage fallback fires again, exactly like the merge base; under generate the unusable value falls through to generation (root root-trace-42, marked generated)

header-free generate on /v1/responses (missing_session_id: generate)

Same curl as Before
HTTP 200; root litellm_session_id=caller-session-42 (the caller's own id, so session consumers keep one stable id), spend session root-trace-42, OTLP session caller-session-42; a generate call with only metadata.trace_id still derives the session from the caller trace (caller-trace-42, kept from the first cut)

full audit matrix at the tip (all `HTTP 200` unless stated, one real provider call per cell)

Precedence on chat, /v1/responses and /v1/messages: caller trace/session win verbatim (incl. 5 KB ids) at OTLP; equal ids stamp the W3C ids; empty, null, int, list and absent values each fall back per-field; malformed traceparent is ignored while baggage still supplies the session
Streaming chat with caller ids: full stream consumed (7 chunks), span exported with the caller session
Policies: generate (caller session, caller trace, and no ids at all), reject (caller session 200, no ids 400 with the session message in the body, baggage session 200)
Correlation off: caller session se-* and baggage bag-session-audit land in the spend session column directly (session-first ordering), equal ids land match-sess
Sad: unauthenticated 401; unknown model 400 with a failure spend row that keeps the caller session; provider 401 surfaces
Edge: 3 identical requests log 3 spend rows and export 3 spans, one per request, same session, no duplicates
Chaos: 30 concurrent mixed-endpoint requests (some streaming) all 200, 30 spans, 30 distinct spend rows exactly once; OTLP sink killed mid-burst: 20/20 requests still 200, spend rows still exactly-once (59 distinct request ids), sink restarted: the exporter re-delivered 17 of the 20 buffered spans and the next call exported immediately (3 buffered spans dropped by the exporter's bounded retry - pre-existing SDK behavior, spend unaffected)
Multi-worker: the integration suite's worker-SIGKILL cell (2-worker proxy) is green at this tip

integration suite at the tip

tests/integration/observability/test_langfuse_delivery.py: 92 passed locally at 250b1a50d2 against the real rig (own proxy per module, scripted upstream, OTLP sink, Postgres, Redis), after the audit cells were fixed in 6b4e3198cf (the six non-string cells pinned the old suppression and were rewritten to assert the concrete header outcome; verified failing on the prior head, passing on the fix). CircleCI owns this suite in CI; its pipelines have been stalled org-wide since ~09:30 today (five unrelated PRs pushed after that also show zero CircleCI statuses), so the branch's CircleCI columns are empty - GitHub Actions is fully green at 250b1a50d2 and the local run above is the substitute until the org queue recovers

UI evidence

Bundled dashboard at the audited proxy (login admin + master key), Logs page showing the audited requests under the W3C-correlated trace/session, and the request detail:

Animated flow (4 steps):

Full screen recording of the flow (login, Logs, request detail): audit_recording.webm

Type

🐛 Bug Fix
✅ Test

Caveats (if any)

Low

For these callers the Langfuse trace and the OTel request span now use different trace ids
- The OTel span stays parented on traceparent, Langfuse follows the caller's trace_id
A non-string metadata.session_id (e.g. 456) never counts as caller-supplied: baggage wins when present, and generate derives from the trace otherwise (merge-base behavior, pinned by 99cf509980)

Final Attestation

The tests check the right things, including the edge cases, and regressions in the respective real-world customer use-cases are not possible after this PR

Link to Devin session: https://app.devin.ai/sessions/e9f90c2f75c14ded84f606aa00756857
Open in Devin Desktop: https://app.devin.ai/desktop/session/e9f90c2f75c14ded84f606aa00756857?variant=devin
Requested by: @yucheng-berri

…adata The W3C traceparent/baggage fallback in add_litellm_metadata_from_request_headers documents itself as last-resort: Lower priority than everything above - only fires when neither the explicit litellm headers nor the Anthropic-metadata path found anything But it guards on the top-level `litellm_trace_id` / `litellm_session_id` body keys and never checks `metadata`, which is the documented way callers set trace_id / session_id (`metadata: {"trace_id": ...}` on /chat/completions). A caller that explicitly sets metadata.trace_id has it silently replaced by the header value, so the implementation contradicts its own stated precedence. This is not a corner case on managed platforms: GCP's front end injects a traceparent into every inbound request, so the fallback fires on traffic whose caller never sent the header. The request still returns 200 and the trace still reaches the logging backend, just under an id the caller never chose, so any caller correlating by its own id silently fails to find its trace. Guard both fallbacks on the caller's request-body metadata as well. Deliberately narrow: - x-litellm-trace-id still outranks the body (documented priority #1) - a request that steers neither field still adopts traceparent/baggage exactly as before - steering is per-field: setting only trace_id still lets session_id come from baggage - litellm_metadata is checked too, for LITELLM_METADATA_ROUTES (/v1/responses, /v1/messages, batches, files) Also corrects the comment, which understated the guard. 4 new tests; each fails without the source change. The existing traceparent and baggage tests are unchanged and still pass.

… values Addresses review. The first version treated any value in either `metadata` or `litellm_metadata` as caller steering. On LITELLM_METADATA_ROUTES the body `metadata` is provider-facing and is only promoted later, so a session_id there suppressed baggage before apply_missing_session_id_policy ran, and a request with a usable baggage session id got a 400 under `missing_session_id: reject`. An empty session_id did the same, since the policy treats "" as absent Now only the active metadata container counts, and only a truthy value, which matches how apply_missing_session_id_policy decides a session id is present. The helper takes a typed `object` rather than a bare dict Adds regression tests for both cases, including the end to end reject path, and drops the test docstrings

Addresses review. On LITELLM_METADATA_ROUTES the proxy promotes the caller's trace control fields (trace_id, session_id, ...) from `metadata` into `litellm_metadata`, but only after the header fallback runs. Checking only `litellm_metadata` let traceparent and baggage fill those fields first, and the promotion then skipped them because they were already set, so the trace was recorded under the header ids The check now also reads `metadata` for fields in LITELLM_TRACE_CONTROL_METADATA_FIELDS on those routes, and apply_missing_session_id_policy uses the same check, so `reject` no longer refuses a request whose session id is about to be promoted The earlier test asserting that a session_id in `metadata` must not block baggage on /v1/responses had the premise wrong, since that value is promoted. It is replaced by tests that assert the promoted caller ids win on /v1/responses and /v1/messages, with no policy, reject, and generate

…oted one Addresses review. Promotion copies a trace control field from `metadata` into `litellm_metadata` only when the key is absent, so a key that is present but empty in `litellm_metadata` wins and the `metadata` value is never used. The check still looked at `metadata` in that case, which let `missing_session_id: reject` accept a request that ends up with an empty session id, and let an empty trace_id or session_id block the headers The check now follows the same rule as promotion. If the active container has the key, its value decides. Only when the key is absent does the promoted `metadata` value count. This makes the conflicting-bucket cases behave exactly as on main

The type-discipline gate failed: this branch added 4 unsuppressed `cast()` calls and LIT006 was already at its limit. Each cast now carries a `# cast-ok` reason. The two in the helper follow an `isinstance` check that proves the Mapping. The two at the call sites stay because the method's `data` parameter is a bare `dict`, and dropping those casts adds basedpyright unknown-type errors instead. No behavior change

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

devin-ai-integration · 2026-09-29T09:01:41Z

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

Disable automatic comment, CI, and merge conflict monitoring

greptile-apps · 2026-09-29T09:05:34Z

Confidence Score: 5/5

[Medium risk] Fixes trace metadata fallback logic in the proxy request handler.

The PR appears safe to merge based on this review; no new issue or outstanding previous finding remains.

Summary

The PR makes caller-supplied trace and session metadata take precedence over W3C header fallbacks and adds coverage for session policies and observability.

The latest change removes redundant wording from a session-handling comment without changing product code.

_{Reviews (9) · Last reviewed commit: "style(proxy): trim the session promotion..."}

devin-ai-integration · 2026-09-29T09:12:19Z

Real UI check on main vs this branch: caller session ids now show in Admin Logs and Langfuse, header-only calls unchanged

Before (main)	After (this PR)

Session

codspeed · 2026-09-29T09:15:53Z

Merging this PR will not alter performance

✅ 31 untouched benchmarks

_{Comparing litellm_lit8561_w3c_fallback_precedence (250b1a5) with main (b4fcc5c)}

codecov · 2026-09-29T09:17:33Z

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

devin-ai-integration · 2026-09-29T09:33:59Z

@greptileai

devin-ai-integration · 2026-09-29T09:34:01Z

bugbot run

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

devin-ai-integration · 2026-09-29T09:43:31Z

@greptileai

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

devin-ai-integration · 2026-09-29T16:02:34Z

@greptileai

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

yucheng-berri · 2026-09-29T17:04:18Z

bugbot run

cursor

Stale Bugbot comment from a previous run.

…cedence upstreams Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

devin-ai-integration · 2026-09-30T04:50:40Z

@greptileai

…ller values The _caller_trace_field gating added for caller-metadata precedence was presence-aware, which regressed three pre-call behaviors versus main: - Equal ids in W3C headers and body metadata suppressed the traceparent/baggage branch entirely, leaving the root litellm_trace_id/litellm_session_id unset so router fallbacks minted a fresh uuid4 per request. The header branch now also fires when the caller value equals the header-derived id, so equal ids stamp the root fields exactly like main. - A truthy but non-string metadata value (e.g. session_id 4815162342) counted as caller-supplied and suppressed the baggage fallback, so downstream str-only consumers (code interpreter sandbox reuse) got a new sandbox per turn. _caller_trace_field now counts only non-empty string values, and the generate policy falls through to generation when the caller value is not usable. - On litellm_metadata routes a usable caller session id suppressed the missing_session_id policies while never landing on the root field, so the root session stayed unset. The policy now promotes the caller's usable session id to litellm_session_id instead of leaving it stranded.

…allback_precedence Main renamed tests/test_litellm/proxy/test_litellm_pre_call_utils.py to tests/unit/proxy/test_litellm_pre_call_utils.py; the branch's test additions (caller-metadata precedence steering plus the equal-ids, agentic-route generate and non-string session regression cases) carry onto the new path.

yucheng-berri · 2026-10-04T08:45:29Z

@greptileai review latest head

yucheng-berri · 2026-10-04T08:45:36Z

bugbot run

cursor

Stale Bugbot comment from a previous run.

yucheng-berri · 2026-10-04T08:50:45Z

@greptileai please review the current head 7855fde (regression-fix commit 99cf509 plus a merge of main that only resolves the test-path rename)

yucheng-berri · 2026-10-04T08:50:46Z

bugbot run

cursor

Stale Bugbot comment from a previous run.

The audit cell compared a headers leg against a headerless leg for equality, which only held while a truthy non-string id suppressed the W3C fallback on both legs. With unusable values ignored again, the headers leg resolves to the header ids while the headerless leg cannot, so assert the headers leg's concrete outcome instead, mirroring the empty/null cell.

yucheng-berri · 2026-10-04T10:10:03Z

@greptileai please review the current head 6b4e319 — the audit cells you flagged are rewritten in test_audit_non_string_caller_ids_fall_back_to_w3c: non-string ids now assert the concrete W3C-header outcome (mirroring the empty/null cell) instead of comparing a headers leg against a headerless leg

yucheng-berri · 2026-10-04T10:10:04Z

bugbot run

cursor

Stale Bugbot comment from a previous run.

yucheng-berri · 2026-10-04T10:17:39Z

@greptileai please review the current head 250b1a5

yucheng-berri · 2026-10-04T10:17:41Z

bugbot run

cursor

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 250b1a5. Configure here.}

fandujar and others added 7 commits September 24, 2026 15:48

Merge remote-tracking branch 'origin/main' into litellm_lit8561_pr43020

7e04a23

test(proxy): cover caller metadata precedence over W3C trace headers

5baeb9e

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

devin-ai-integration Bot requested a review from a team September 29, 2026 09:01

devin-ai-integration Bot assigned yucheng-berri Sep 29, 2026

devin-ai-integration Bot mentioned this pull request Sep 29, 2026

fix(proxy): traceparent/baggage fallback must not override caller metadata #43020

Closed

6 tasks done

greptile-apps Bot reviewed Sep 29, 2026

View reviewed changes

Comment thread litellm/proxy/litellm_pre_call_utils.py Outdated

fix(proxy): generated session uses promoted caller trace id

d656a4f

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

greptile-apps Bot reviewed Sep 29, 2026

View reviewed changes

Comment thread tests/test_litellm/proxy/test_litellm_pre_call_utils.py Outdated

test(proxy): move test context into assertion messages

6f27b56

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

yucheng-berri and others added 2 commits September 29, 2026 15:11

test(integration): audit cells for w3c fallback precedence

46eac14

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

test(integration): tighten audit chaos cells

fb94af8

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

style(test): drop stray blank lines

b481774

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

cursor Bot reviewed Sep 29, 2026

View reviewed changes

yucheng-berri added the run-ci label Sep 29, 2026

test(integration): ignore body-less model-info probes in langfuse pre…

4d3940c

…cedence upstreams Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

mateo-berri removed the run-ci label Sep 30, 2026

yucheng-berri added 2 commits October 4, 2026 01:28

cursor Bot reviewed Oct 4, 2026

View reviewed changes

greptile-apps Bot reviewed Oct 4, 2026

View reviewed changes

Comment thread tests/integration/observability/test_langfuse_delivery.py Outdated

cursor Bot reviewed Oct 4, 2026

View reviewed changes

greptile-apps Bot reviewed Oct 4, 2026

View reviewed changes

Comment thread litellm/proxy/litellm_pre_call_utils.py Outdated

style(proxy): trim the session promotion comment to the non-obvious why

250b1a5

cursor Bot reviewed Oct 4, 2026

View reviewed changes

yucheng-berri approved these changes Oct 8, 2026

View reviewed changes

yucheng-berri merged commit 02b8b5c into main Oct 8, 2026
105 checks passed

yucheng-berri deleted the litellm_lit8561_w3c_fallback_precedence branch October 8, 2026 02:24

Conversation

devin-ai-integration Bot commented Sep 29, 2026 • edited by yucheng-berri Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

REVIEWER MUST KNOW BEFORE APPROVING

TLDR

User Flow

Relevant issues

Affected release

Linear ticket

Pre-Submission checklist

Delays in PR merge?

Screenshots / Proof of Fix

Before (4d3940c, prior head; the merge base 85dc7cb already behaved like After)

equal ids in headers and metadata (chat)

non-string metadata session_id with baggage (chat)

header-free generate on /v1/responses (missing_session_id: generate)

After (250b1a5)

equal ids in headers and metadata (chat, and /v1/responses)

non-string metadata session_id with baggage (chat; also list, bool, nested object in unit tests)

header-free generate on /v1/responses (missing_session_id: generate)

full audit matrix at the tip (all HTTP 200 unless stated, one real provider call per cell)

integration suite at the tip

UI evidence

Type

Caveats (if any)

Low

Final Attestation

Uh oh!

devin-ai-integration Bot commented Sep 29, 2026

Uh oh!

greptile-apps Bot commented Sep 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Confidence Score: 5/5

Summary

Uh oh!

Uh oh!

devin-ai-integration Bot commented Sep 29, 2026

Uh oh!

codspeed Bot commented Sep 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merging this PR will not alter performance

Uh oh!

codecov Bot commented Sep 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

devin-ai-integration Bot commented Sep 29, 2026

Uh oh!

devin-ai-integration Bot commented Sep 29, 2026

Uh oh!

Uh oh!

devin-ai-integration Bot commented Sep 29, 2026

Uh oh!

devin-ai-integration Bot commented Sep 29, 2026

Uh oh!

yucheng-berri commented Sep 29, 2026

Uh oh!

cursor Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

devin-ai-integration Bot commented Sep 30, 2026

Uh oh!

yucheng-berri commented Oct 4, 2026

Uh oh!

yucheng-berri commented Oct 4, 2026

Uh oh!

cursor Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

yucheng-berri commented Oct 4, 2026

Uh oh!

yucheng-berri commented Oct 4, 2026

Uh oh!

cursor Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

devin-ai-integration Bot commented Sep 29, 2026 •

edited by yucheng-berri

Loading

Before (`4d3940c`, prior head; the merge base `85dc7cb` already behaved like After)

After (`250b1a5`)

full audit matrix at the tip (all `HTTP 200` unless stated, one real provider call per cell)

greptile-apps Bot commented Sep 29, 2026 •

edited

Loading

codspeed Bot commented Sep 29, 2026 •

edited

Loading

codecov Bot commented Sep 29, 2026 •

edited

Loading

cursor Bot left a comment •

edited

Loading

cursor Bot left a comment •

edited

Loading

cursor Bot left a comment •

edited

Loading

cursor Bot left a comment •

edited

Loading