-
Notifications
You must be signed in to change notification settings - Fork 24
Closed
Description
Summary
When a model is explicitly configured (via --model flag or config), display it in the review output so users can see which model was used.
Current Behavior
Review (by claude-code)
------------------------------------------------------------
{review output}
Proposed Behavior
Review (by claude-code) # model empty/default - no change
Review (by claude-code, gpt-4) # model explicitly set
Implementation
The Review struct doesn't currently have a Model field - the model is stored on ReviewJob. Options:
- Add
Modelas a joined field onReview- populate when fetching from DB/API (similar to howVerdictis computed) - Include in
showReview()display when non-empty
Context
This follows up on PR #126 which added --model support to all agents. The model is stored in the database and visible in job listings (roborev jobs), but not shown in the review output itself.
Files to modify
internal/storage/models.go- addModelfield toReviewstructinternal/storage/reviews.go- populateModelwhen fetching reviews (join withreview_jobs)cmd/roborev/main.go- updateshowReview()to display model when non-emptycmd/roborev/run.go- updateshowPromptResult()similarly
Metadata
Metadata
Assignees
Labels
No labels