# How to update models on LLM agents?

**URL:** <https://meta.discourse.org/t/how-to-update-models-on-llm-agents/409274>\
**Category:** Support\
**Tags:** ai, ai-bot\
**Created:** [August 4, 2026, 3:42pm UTC](https://meta.discourse.org/t/how-to-update-models-on-llm-agents/409274 "2026-08-04T15:42:44Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [August 4, 2026, 8:20pm UTC](https://meta.discourse.org/t/how-to-update-models-on-llm-agents/409274/6 "2026-08-04T20:20:35Z")

</div>

> [@Falco](#):
>
> What about the request logs for the actual PM completion on the ai api audit logs? Or clicking on the “Previous” button on the `info` modal.

I got tired of explaining this over and over both to colleagues as well as users, so here goes a fix

> <https://github.com/discourse/discourse/pull/42326>
>
> Previously, the AI debug modal loaded the newest audit log in the topic up to th…e clicked post; since title generation runs after the first bot reply and logs without a \`post\_id\`, debugging the first reply opened the titlebot request instead of the reply's own interaction, which confused users.
> 
> This change makes \`show\_debug\_info\` prefer the audit log belonging to the clicked post (falling back to the newest topic-scoped log only when the post has none), while topic-scoped logs such as title generation remain reachable via next/previous navigation.

---

_[View the full topic](https://meta.discourse.org/t/how-to-update-models-on-llm-agents/409274)._