fix: Populate model_tier when creating channels from session data

[xinquiry]

Summary

• Fixed TierSelector always showing "STANDARD" due to missing model_tier state management
• Added model_tier field when creating ChatChannel objects from session data in all relevant locations

Changes

• fetchChatHistory: populate model_tier when loading channels from session list
• activateChannel: include model_tier when creating channel from topic lookup
• activateChannelForAgent: add model_tier when creating channels for agent activation (2 locations)
• createDefaultChannel: include model_tier when creating new sessions/topics (3 locations)

Test plan

• Select a tier other than "standard" and verify it persists after page refresh
• Create a new chat session and verify tier selection works
• Switch between different chat sessions and verify correct tier is displayed

Fixes #170

🤖 Generated with Claude Code

Summary by Sourcery

确保在所有创建路径中，聊天频道都能正确从会话数据中继承模型层级（model tier）信息。

Bug 修复：

• 在加载聊天历史记录，以及从现有会话或主题激活频道时，保留已选择的模型层级。
• 修复在为智能体激活频道，以及为新会话或主题创建默认频道时，模型层级缺失的问题。
• 在根据会话数据创建新的默认聊天频道时，补上之前遗漏的 google_search_enabled 标志位。

Original summary in English

Summary by Sourcery

Ensure chat channels correctly carry over model tier information from session data in all creation paths.

Bug Fixes:

• Preserve the selected model tier when loading chat history and activating channels from existing sessions or topics.
• Fix missing model tier when activating channels for agents and when creating default channels for new sessions or topics.
• Include the previously omitted google_search_enabled flag when creating a new default chat channel from session data.

[sourcery-ai]

审阅者指南（在小型 PR 上折叠）

审阅者指南

通过所有代码路径将 session 数据中的 model_tier 字段传递到 ChatChannel 创建流程中，确保在加载、激活或创建聊天会话时，所选的模型等级（tier）能够被保留。

session 加载与刷新过程中 model_tier 持久化的时序图

sequenceDiagram
    actor User
    participant UI as TierSelector
    participant Store as ChatSlice
    participant Backend

    User->>UI: Select non_standard model_tier
    UI->>Store: createDefaultChannel(agentId, provider_id, model, model_tier)
    Store->>Backend: POST /sessions with model_tier
    Backend-->>Store: newSession(id, model_tier)
    Store->>Store: create ChatChannel with newSession.model_tier
    Store-->>UI: active ChatChannel(model_tier)
    UI->>UI: Display selected model_tier

    User->>UI: Refresh page
    UI->>Store: fetchChatHistory()
    Store->>Backend: GET /sessions
    Backend-->>Store: sessions list(with model_tier)
    Store->>Store: create ChatChannel per session including model_tier
    Store-->>UI: channels list with model_tier
    UI->>UI: Show correct tier for each channel

Loading

ChatChannel 与 session 之间 model_tier 传递的类图

classDiagram
    class Session {
      +string id
      +string topic_id
      +string agent_id
      +string provider_id
      +string model
      +string model_tier
      +bool google_search_enabled
    }

    class ChatChannel {
      +string id
      +string sessionId
      +string topicId
      +string agentId
      +string provider_id
      +string model
      +string model_tier
      +bool google_search_enabled
      +bool connected
      +string error
    }

    class ChatSlice {
      +ChatChannel[] channels
      +void fetchChatHistory()
      +void activateChannel(channelId)
      +void activateChannelForAgent(agentId)
      +void createDefaultChannel(agentId, provider_id, model, model_tier)
    }

    Session "1" --> "many" ChatChannel : source_for
    ChatSlice "1" --> "many" ChatChannel : manages
    ChatSlice --> Session : reads_model_tier_from

Loading

文件级变更

变更	详情	文件
在根据已有的 session 列表和 topic 查询结果创建 ChatChannel 对象时填充 model_tier，以便在 state 中保留所选择的 tier。	在 fetchChatHistory 中将 sessions 映射为 channels 时，在 channel 对象中加入 session.model_tier。 在 activateChannel 过程中，从匹配的 session 中追踪 sessionModelTier 并将其包含在构造的 channel 中。 在 activateChannelForAgent 中，从 session 数据创建 channel 时（包括已有 session 和新建 session），都要包含 model_tier。	web/src/store/slices/chatSlice.ts
确保新创建的 sessions/topics 也会在其对应的 ChatChannel 对象上设置 model_tier。	在 createDefaultChannel 中复用 existingSession 时，将 existingSession.model_tier 传入新建的 channel。 在处理 newSession 创建流程时，始终在 channel 对象中包含 newSession.model_tier。 在最终的 newSession 分支中，同时填充 google_search_enabled 与 model_tier，以保持 channel 状态与 session 一致。	web/src/store/slices/chatSlice.ts

针对关联 issue 的评估

Issue	目标	是否解决	说明
#170	在前端聊天（Zustand）state 中为 sessions/channels 存储并传播 model_tier 字段，使 tier 选择器能够反映实际选中的 tier，并在组件重新渲染后仍然保持。	✅
#170	将 model_tier 与后端 session 数据完全同步，包括加载已有 sessions 以及在创建新 session 时发送所选的 tier。	❌	该 PR 在从已有 session 数据和 newSession 响应创建 channel 时加入了 model_tier，覆盖了从后端同步到前端的方向。但目前没有改动显示在创建/更新后端 sessions 时会在请求体中包含 model_tier，因此尚不能明确保证在创建 session 时会将 tier 发送给后端。

可能相关的 issues

• Model tier: Frontend always shows STANDARD without proper state management #170：PR 将 model_tier 加入聊天 state / session 处理流程，使 tier 选择持久化，并保证 UI 显示正确的 tier。

---

技巧与命令

与 Sourcery 交互

• 触发新的审阅： 在 pull request 上评论 @sourcery-ai review。
• 继续讨论： 直接回复 Sourcery 的审阅评论。
• 从审阅评论生成 GitHub issue： 在审阅评论下回复并请求 Sourcery 从该评论创建 issue。你也可以直接回复 @sourcery-ai issue 来从该评论创建 issue。
• 生成 pull request 标题： 在 pull request 标题中任意位置写上 @sourcery-ai，即可随时生成一个标题。你也可以在 pull request 中评论 @sourcery-ai title 来（重新）生成标题。
• 生成 pull request 摘要： 在 pull request 正文任意位置写上 @sourcery-ai summary，即可在对应位置随时生成 PR 摘要。你也可以在 pull request 中评论 @sourcery-ai summary 来（重新）生成摘要。
• 生成审阅者指南： 在 pull request 中评论 @sourcery-ai guide，即可随时（重新）生成审阅者指南。
• 一次性解决所有 Sourcery 评论： 在 pull request 中评论 @sourcery-ai resolve，即可标记解决所有 Sourcery 评论。如果你已经处理完所有评论且不想再看到它们，这很有用。
• 忽略所有 Sourcery 审阅： 在 pull request 中评论 @sourcery-ai dismiss，即可忽略所有现有的 Sourcery 审阅。特别适用于你想从头开始新的审阅 —— 记得随后评论 @sourcery-ai review 来触发新的审阅！

自定义你的体验

前往你的 dashboard 可以：

• 启用或禁用审阅功能，例如 Sourcery 生成的 pull request 摘要、审阅者指南等。
• 更改审阅语言。
• 添加、删除或编辑自定义审阅说明。
• 调整其他审阅设置。

获取帮助

• 联系支持团队，以提出问题或反馈。
• 访问我们的文档，查看详细指南和信息。
• 通过关注我们的 X/Twitter、LinkedIn 或 GitHub 与 Sourcery 团队保持联系。

Original review guide in English

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Propagates the model_tier field from session data into ChatChannel creation across all code paths, ensuring the selected tier is preserved when loading, activating, or creating chat sessions.

Sequence diagram for model_tier persistence across session load and refresh

sequenceDiagram
    actor User
    participant UI as TierSelector
    participant Store as ChatSlice
    participant Backend

    User->>UI: Select non_standard model_tier
    UI->>Store: createDefaultChannel(agentId, provider_id, model, model_tier)
    Store->>Backend: POST /sessions with model_tier
    Backend-->>Store: newSession(id, model_tier)
    Store->>Store: create ChatChannel with newSession.model_tier
    Store-->>UI: active ChatChannel(model_tier)
    UI->>UI: Display selected model_tier

    User->>UI: Refresh page
    UI->>Store: fetchChatHistory()
    Store->>Backend: GET /sessions
    Backend-->>Store: sessions list(with model_tier)
    Store->>Store: create ChatChannel per session including model_tier
    Store-->>UI: channels list with model_tier
    UI->>UI: Show correct tier for each channel

Loading

Class diagram for ChatChannel and session model_tier propagation

classDiagram
    class Session {
      +string id
      +string topic_id
      +string agent_id
      +string provider_id
      +string model
      +string model_tier
      +bool google_search_enabled
    }

    class ChatChannel {
      +string id
      +string sessionId
      +string topicId
      +string agentId
      +string provider_id
      +string model
      +string model_tier
      +bool google_search_enabled
      +bool connected
      +string error
    }

    class ChatSlice {
      +ChatChannel[] channels
      +void fetchChatHistory()
      +void activateChannel(channelId)
      +void activateChannelForAgent(agentId)
      +void createDefaultChannel(agentId, provider_id, model, model_tier)
    }

    Session "1" --> "many" ChatChannel : source_for
    ChatSlice "1" --> "many" ChatChannel : manages
    ChatSlice --> Session : reads_model_tier_from

Loading

File-Level Changes

Change	Details	Files
Populate model_tier when creating ChatChannel objects from existing session lists and topic lookups so the selected tier is preserved in state.	When mapping sessions to channels in fetchChatHistory, include session.model_tier in the channel object. During activateChannel, track sessionModelTier from the matching session and include it in the constructed channel. Include model_tier when creating channels from session data in activateChannelForAgent for both existing and newly created sessions.	web/src/store/slices/chatSlice.ts
Ensure newly created sessions/topics also set model_tier on their corresponding ChatChannel objects.	When reusing an existingSession in createDefaultChannel, pass existingSession.model_tier into the new channel. When handling newSession creation flows, always include newSession.model_tier in the channel object. In the final newSession branch, also populate google_search_enabled alongside model_tier to keep channel state consistent with the session.	web/src/store/slices/chatSlice.ts

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#170	Store and propagate the model_tier field in the frontend chat (Zustand) state for sessions/channels so that the tier selector can reflect the actual selected tier and persist across component re-renders.	✅
#170	Fully sync model_tier with backend session data, including both loading existing sessions and sending the selected tier when creating new sessions.	❌	The PR adds model_tier to channel creation from existing session data and from newSession responses, which covers syncing from backend to frontend. However, there are no changes showing that model_tier is included in the payload when creating/updating sessions on the backend, so it does not clearly ensure the tier is sent to the backend on session creation.

Possibly linked issues

• Model tier: Frontend always shows STANDARD without proper state management #170: PR adds model_tier to chat state/session handling so tier selection persists and UI shows correct tier.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - 我在这里给了一些高层面的反馈：

• 现在有多个地方在把 session 对象映射成类似 ChatChannel 的结构（包括新的 model_tier 字段）；可以考虑抽取一个小的辅助函数来统一这部分映射逻辑，减少未来遗漏字段的风险。
• 在最后一个变更块里，你在创建新 channel 时开始设置 google_search_enabled（之前是省略的）；请再次确认这个行为变化是有意为之，并且不会与关于其默认状态的任何既有假设相冲突。

给 AI 代理的提示

Please address the comments from this code review:

## Overall Comments
- There are multiple places now mapping `session` objects into `ChatChannel`-like structures (including the new `model_tier` field); consider extracting a small helper to keep this mapping logic consistent and reduce the risk of future omissions.
- In the last hunk you also started setting `google_search_enabled` when creating the new channel (where it was previously omitted); double-check that this behavioral change is intentional and doesn’t conflict with any assumptions about its default state.

---

Sourcery 对开源项目是免费的——如果你觉得我们的 review 有帮助，欢迎分享 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮我变得更有用！请在每条评论上点 👍 或 👎，我会根据你的反馈改进后续的 review。}

Original comment in English

Hey - I've left some high level feedback:

• There are multiple places now mapping session objects into ChatChannel-like structures (including the new model_tier field); consider extracting a small helper to keep this mapping logic consistent and reduce the risk of future omissions.
• In the last hunk you also started setting google_search_enabled when creating the new channel (where it was previously omitted); double-check that this behavioral change is intentional and doesn’t conflict with any assumptions about its default state.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- There are multiple places now mapping `session` objects into `ChatChannel`-like structures (including the new `model_tier` field); consider extracting a small helper to keep this mapping logic consistent and reduce the risk of future omissions.
- In the last hunk you also started setting `google_search_enabled` when creating the new channel (where it was previously omitted); double-check that this behavioral change is intentional and doesn’t conflict with any assumptions about its default state.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!