π Karpathy LLM Wiki v1.27.0 β released 2026-08-27 #555
green-dalii
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
v1.27.0 is out β three things you might actually want to know about
Hey everyone π
The v1.27.0 MINOR release shipped today (2026-08-27). If you only read one paragraph, read this one: nothing about your existing wiki changes by default. Every new setting has been carefully scoped to behave exactly like v1.26.4 unless you opt in. So the upgrade is genuinely "click Update in Obsidian and forget."
But if you do poke around, there's a lot to play with this cycle. Here are the bits I'm personally most excited about:
πͺ¨ AWS Bedrock with SSO is finally here. If you've been holding off on Bedrock because the API-key-only flow didn't fit your org's auth setup β that's over. v1.27.0 adds SSO via AWS IAM Identity Center (the standard "log in with your work account" flow), plus an IAM-key path for CI / programmatic users. Both ship with zero AWS SDK β the signing is hand-rolled, the binary cost is about 10 KB. The SSO path is fully wired in the UI: you'll see a new "Auth method" dropdown in the Bedrock provider settings. One real-AWS E2E is still pending before we flip the green light on all three modes end-to-end, but the api-key path is solid today. (huge thanks to @DocTpoint for the design review on this one β it's been a months-long thread)
π MinerU joins the conversion backend. Until now you had one choice for PDF conversion: the local native path. v1.27.0 adds an online alternative β MinerU's Precise parser β that handles PDF and images and Office documents (DOCX/PPTX/XLSX) in one go. If your vault has a mix of formats and you've been bouncing between tools to convert them, give the new backend a try. Settings β PDF conversion β backend switch. Thanks @XEurekaX for landing this one β it's a sizeable contribution.
π©Ή Fix Dead Links stops creating empty pages. This one is small but very pleasant in daily use: if your source mentions something the wiki can't resolve, the plugin used to silently create a stub page. Now it doesn't (default behaviour). If you actually want the stubs back, the setting is
fixDeadLinksCreateStub. Opt-in, opt-out, your call.A few more things worth knowing about, briefly:
npm auditwent from 1 HIGH vulnerability to 0, by pinning the actual upstream package that npm's lockfile was leaving under-pinned. No user-visible change, but worth a mention since I know some of you track this.Full release notes (much more detail than this post): v1.27.0 release.
How to get it
If you're already on a recent version of the plugin, this release appears as a one-click update in Obsidian β Settings β Community plugins. Click Update and you're done β your wiki, settings, and history carry over automatically.
If you're new: Obsidian β Settings β Community plugins β Browse β search "Karpathy LLM Wiki" β Enable. Or grab it from the Community Plugin page (the "Add to Obsidian" button handles the install).
Things I'd love your feedback on
A few items I'd genuinely like to hear about as you start using v1.27.0:
leave_itdefault for Fix Dead Links β we picked this as default after seeing several users get noise from stub spam, but it's a real behaviour change. If your workflow depended on the stubs, the setting to flip it is one checkbox.task=mode[:thinking]per step). If anyone finds this confusing, I'd like to know what UI would actually help vs. raw text.Acknowledgements
This cycle was unusually community-heavy β 5 distinct external contributors shipped PRs:
:variants visible in the catalog (fix(ui): keep OpenRouter model variants in the catalogΒ #538)And of course @DocTpoint β architect-level contributor with 18 PRs this cycle covering the long-running v1.25.x β v1.27.0 ingest-reliability work. If you've been running the plugin for a while and things "just work" lately, much of that is DocTpoint.
If you're using the plugin and find something broken, missing, or surprising β please file an Issue. The bug reports that include a reproduction (vault type, file extension, provider, what you saw vs. what you expected) are the ones I can actually act on.
Happy to answer questions in the comments below π
All reactions