Skip to content

fix(piebald): use per-message model instead of chat-level model#112

Merged
mike1858 merged 2 commits intomainfrom
fix/use-actual-model-versus-stated-model-in-piebald-analyzer
Feb 6, 2026
Merged

fix(piebald): use per-message model instead of chat-level model#112
mike1858 merged 2 commits intomainfrom
fix/use-actual-model-versus-stated-model-in-piebald-analyzer

Conversation

@mike1858
Copy link
Member

@mike1858 mike1858 commented Feb 6, 2026

This affects Piebald users only.

Summary by CodeRabbit

Release Notes

  • Improvements
    • Enhanced message model attribution to accurately identify and track which model generated each individual message within a conversation, with automatic fallback to the conversation-level model for backward compatibility with previously recorded messages.

Query and use the model field from individual messages rather than
always using the chat-level model. This ensures the actual model that
generated each response is recorded, falling back to chat-level model
for older messages that may lack the per-message field.
@coderabbitai
Copy link

coderabbitai bot commented Feb 6, 2026

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review
📝 Walkthrough

Walkthrough

Added per-message model tracking to PiebaldMessage with optional model field. Updated SQL query to retrieve the model column and modified assistant message handling to compute model_str using per-message model with fallback to chat-level model.

Changes

Cohort / File(s) Summary
Per-Message Model Tracking
src/analyzers/piebald.rs
Added optional model field to PiebaldMessage struct; updated SQL query to retrieve model column; modified conversion logic for assistant messages to use per-message model with fallback to chat-level model; updated comments to reflect new behavior.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 A message now carries its model within,
With fallback to chat when the model's been thin,
Per-message precision takes flight,
SQL queries fetch what's right,
Tracking gets richer—how clever! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the main change: adopting per-message model tracking instead of relying solely on chat-level models.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/use-actual-model-versus-stated-model-in-piebald-analyzer

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@mike1858 mike1858 merged commit 4d07acc into main Feb 6, 2026
6 checks passed
@mike1858 mike1858 deleted the fix/use-actual-model-versus-stated-model-in-piebald-analyzer branch February 6, 2026 20:51
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