llm 0.32rc2
Named practitioner synthesis
#1083
- Topic
- unassigned (set during synthesis)
- First seen
- 2026-07-31 08:04:26
- Last seen
- 2026-07-31 08:04:27
Source raw items (2)
- Blog / Newsletter2026-07-31 08:04:23llm 0.32rc2
<p><strong>Release:</strong> <a href="https://github.com/simonw/llm/releases/tag/0.32rc2">llm 0.32rc2</a></p> <p>Hot on the heels of <a href="https://simonwillison.net/2026/Jul/30/llm-rc1/">RC1</a>, this fixes a dependency issue and also adds two neat new features:</p> <blockquote> <ul> <li>The default model for users who have not set their own default is now <a href="https://developers.openai.com/api/docs/models/gpt-5.6-luna">GPT-5.6 Luna</a>. It was previously <a href="https://developers.openai.com/api/docs/models/gpt-4o-mini">GPT-4o mini</a>. Luna is a much better and more recent model, albeit slightly more expensive - $0.20 per million input tokens and $1.20 per million output tokens, compared to $0.15/$0.60 for 4o mini. You can switch back to 4o mini using <code>llm models default gpt-4o-mini</code>, or switch to <a href="https://developers.openai.com/api/docs/models/gpt-5-nano">GPT-5 nano</a>, an even cheaper default model ($0.05/$0.40), using <code>llm models default gpt
- Blog / Newsletter2026-07-31 08:04:23llm 0.32rc1
<p><strong>Release:</strong> <a href="https://github.com/simonw/llm/releases/tag/0.32rc1">llm 0.32rc1</a></p> <p>This RC for LLM 0.32 finishes the work that <a href="https://simonwillison.net/2026/Apr/29/llm/">started in LLM 0.32a0</a> - it adds a <a href="https://llm.datasette.io/en/latest/logging.html#the-message-store">new schema design</a> that does a much better job of capturing the details of the prompts and responses returned by the latest model families.</p> <p>The most important change is the use of content-addressable hash IDs for stored messages. This allows de-duplication in the database, and means that LLM can now represent trees of messages for forked conversations.</p> <p>Since it involves a significant schema change - new tables only, and old data should not be affected at all - it's worth running a backup of your existing <code>logs.db</code> before upgrading to the RC:</p> <pre><code>llm logs backup logs-backup.db </code></pre> <p>The RC also adds support for