The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 10, 2026 5:43am

PR Summary

Low Risk
Low risk: small change to agent response shaping that adds model to metadata for structured responses; minimal behavioral impact beyond an extra output field.

Overview
Agent responses now always include the provider model by moving it into createResponseMetadata, so structured (responseFormat) JSON outputs get the same metadata as standard outputs.

Tests were updated to assert model is present in structured response results.

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

Greptile Summary

This PR fixes a bug where the model field was absent from agent block outputs when a custom response format (responseFormat) was provided. The fix moves model: result.model from processStandardResponse into createResponseMetadata so it is emitted by both the standard and structured response code paths. A matching test assertion (model: 'mock-model') was added to verify the structured response path now includes the field.

Confidence Score: 5/5

Safe to merge — minimal, targeted bug fix with a matching test covering the previously untested code path.

The change is a single-field relocation with no behavioral regressions on the standard path and a clear fix for the structured response path. No P0 or P1 findings identified.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Agent Execute] --> B{responseFormat set?}
    B -- No --> C[processStandardResponse]
    B -- Yes --> D[processStructuredResponse]

    C --> E["return { content, ...createResponseMetadata }"]
    D --> F{Valid JSON?}
    F -- Yes --> G["return { ...extractedJson, ...createResponseMetadata }"]
    F -- No --> H[Fallback to processStandardResponse]

    E --> I["createResponseMetadata includes model ✓"]
    G --> I
    H --> I

_{Reviews (2): Last reviewed commit: "fix(agent): update test expectation for ..." | Re-trigger Greptile}

@greptile

@cursor review