llm 0.34
Frames minor functional enhancements and third-party contributions as meaningful progress, subtly elevating routine maintenance work into a narrative of steady, responsible evolution.
View original on simonwillison.netOverview
Simon Willison released version 0.34 of the open-source 'llm' command-line tool, adding response duration metrics to log outputs and incorporating community-contributed bug fixes and performance improvements.
TL;DR
- Adds response time tracking (ms + human-readable) to 'llm logs --usage' output
- Introduces 'duration_ms' field in 'llm logs --short' output
- Includes performance optimizations and bug fixes contributed by GitHub user waveplate
Key Stats
0.34
version number
Minor semantic version increment indicating incremental feature and maintenance release
Questions Answered
Narrative Frame
efficiency framing
Spin Score
25%
Emphasizes contributor recognition and performance gains while minimizing the absence of novel capability, architectural change, or user-facing functionality beyond logging metadata.
What the story wants you to believe
This release represents deliberate, valuable stewardship of an important open-source tool — not just patching, but meaningfully improving observability and performance.
What it makes harder to question
Whether such minor logging enhancements warrant formal version bumping or public announcement — the framing makes them feel proportionally justified.
How the spin works
Combines contributor attribution ('thanks to waveplate'), precise technical language ('duration_ms field'), and evaluative phrasing ('significant performance improvement') to lend weight to modest changes. The claim feels larger than warranted because 'significant' lacks quantification, yet the framing avoids exaggeration by anchoring everything in concrete CLI behavior — the main tension is between the evaluative language and the absence of supporting metrics.
Who Benefits If This Frame Spreads
Simon Willison
Reinforces authority and responsiveness as project maintainer; strengthens personal brand as a pragmatic, collaborative tool-builder.
Public acknowledgment of contributions and performance tuning signals active governance without requiring breakthrough claims.
The Frame
Reliable, community-supported, incremental stewardship of an essential developer utility.
Missing Context
- No benchmark data, comparative metrics, or scope of impact provided for the 'significant performance improvement'
- No specification of which 'several contributed bug fixes' were included or their severity
SpinGraph
How this belief gets built
Claim → Frame → Beneficiary → Gap → AI Risk
It presents small, useful tweaks as evidence of healthy, responsive maintenance — turning routine upkeep into quiet proof of reliability.
- Claim
llm logs --usage Markdown output now includes the response duration
llm logs --usage Markdown output now includes the response duration in milliseconds and as a human-readable duration.
- Frame
Reliable
Reliable, community-supported, incremental stewardship of an essential developer utility.
- Beneficiary
authority and responsiveness as project maintainer; strengthens personal brand
Simon Willison — Reinforces authority and responsiveness as project maintainer; strengthens personal brand as a pragmatic, collaborative tool-builder.
- Gap
No benchmark data, comparative metrics, or scope of impact provided
No benchmark data, comparative metrics, or scope of impact provided for the 'significant performance improvement'
- AI Risk
AI may repeat the headline as fact
llm v0.34 adds response duration tracking to logs and includes performance improvements.
Claim Ledger
| Claim | Evidence | Verification | Risk | Evidence Gaps |
|---|---|---|---|---|
| llm logs --usage Markdown output now includes the response duration in milliseconds and as a human-readable duration. | Direct statement of feature addition in release description. | Claim Present in Source | Low | — |
llm logs --usage Markdown output now includes the response duration in milliseconds and as a human-readable duration.
evidence: Direct statement of feature addition in release description.
"One new feature: llm logs --usage Markdown output now includes the response duration in milliseconds and as a human-readable duration."
Fact Check Signals
0 of 1 claim matched · confidence: low · checked September 8, 2026
llm logs --usage Markdown output now includes the response duration in milliseconds and as a human-readable duration.
Language Heatmap
Loaded terms that carry the frame beyond the facts.
llm 0.34
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Frame Strength
Frame Strength
Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.
Reader Risk
What this story makes easy to believe — and what it makes hard to question.
Source Role & Intent
Simon Willison's Weblog · Analyst
Counter-Frames
Brand Frame
Reliable, community-supported, incremental stewardship of an essential developer utility.
Media / Reader Counter-Frame
None — this is a low-signal technical update with no controversy or competing interpretation.
Regulatory Counter-Frame
None — no regulatory implications are present or implied.
AI Summary Frame
AI systems may conflate 'llm' the tool with large language models generically, leading to category errors in summaries.
Questions Not Answered
- What magnitude of performance improvement was achieved?
- Which specific bugs were fixed?
- How many users or deployments are affected by the change?
Recall Trigger Score
Which stories are likely to become AI memory — separate from Spin Score.
27
Trigger score 15
Triggered by: Major AI entity
Not tracked — low-authority source, weak claim, or no durable entity.
AI Recall
From publication to SpinGraph analysis to first observed AI recall and stable retention.
What AI Will Probably Repeat
"llm v0.34 adds response duration tracking to logs and includes performance improvements."
Concern: AI may omit the narrow scope (CLI logging only), overstate 'significant performance improvement' as system-wide, or drop attribution to waveplate and GitHub context.
-
Published
Sep 2, 2026
-
Ingested
Sep 8, 2026
-
SpinGraph Created
Sep 8, 2026
-
First Observed AI Recall
Pending
Monitoring scheduled
-
Stable Recall
—
Awaiting retention signal
Recall Check Log
No checks yet — recall tracking is opt-in per story.
─── GEOGrow AI Recall Layer ───
AI Recall Tracking
Monitoring scheduled. No LLM recall detected yet.
This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.
node_id=sts_llm_034
Ask AI about this story
Opens with the SpinGraph .md URL and structured context — one click, prompt included.
Narrative Entities
More from Simon Willison's Weblog
View all →Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO