Thingy
An AI librarian that answers questions about everything I have published, with citations back to the original posts and issues.
Ask the archive, get the sources.
- Status
- Active Being built or operated.
- Dates
- Started May 7, 2026 (Launched May 2026)
- Where
- thingy.thingelstad.com/
- Topics
- Agents MCP The open web Archives
- Page views
- 1,317 in the twelve months to Sep 30, 2026
- Latest evidence
- Latest commit, Oct 23, 2026
Thingy is an AI librarian for my public archive. You ask it a question, such as when I first wrote about Ethereum or what I was reading in 2019, and it finds the posts and issues that answer it, quotes them, and links to the originals. It knows only what I have published. Weekly Thing subscribers sign in with their email, and Supporting Members get larger daily budgets.
I previewed it in Weekly Thing 346 and launched it with the new Weekly Thing website on May 7, 2026. A month later, Thingy Evolved gave it its own site and three archives to search, the newsletter, the blog, and the podcast, along with saved conversations, curiosity maps, voice input, and memory. In September I added photos and shared conversations and called it complete. In October it got a new design, with Claude Sonnet for subscribers and Claude Opus for Supporting Members.
Behind Thingy is Librarian, a private archive API with no front end of its own. It holds working copies of every Weekly Thing issue, the blog posts pulled from Micro.blog, and the Another Thing episodes with their transcripts, and it builds the search indexes Thingy answers from. Its repository began as Studio, my earlier publishing system. When publishing moved to WT Builder, what was left became Librarian. It also indexes this registry of things I have built.
The same tools Thingy uses are offered as an MCP server at librarian.thingelstad.com/mcp. Weekly Thing subscribers can connect Claude, ChatGPT, or another AI to it and sign in with their email, with no password. The AI can then search the newsletter, blog, links, photos, and podcast, and link back to each source it uses. As described on Thingy’s about page, an AI agent spent eight review rounds trying to break the tools when the MCP server launched, and what it found shaped how matching works.
Since Weekly Thing 350, Thingy also writes two sections of each issue: Supporting Membership and Echoes, which connects the week’s topics to earlier issues.
The build
- A static React app built on assistant-ui, served from a private S3 bucket behind CloudFront.
- It calls Librarian, its private archive API, streams answers over server-sent events, and renders citations and inline photos.
- Librarian's Python corpus pipeline builds chunked, embedded indexes of every source, and a Node API on AWS Lambda answers from them.
- Retrieval is hybrid. TF-IDF lexical search and semantic embeddings are fused with reciprocal-rank fusion, then reranked.
- An agent loop running Claude on Amazon Bedrock plans tool calls, gathers evidence, and writes cited answers.
- The same tools are published as an MCP server with OAuth 2.1 sign-in, and a suite of more than 850 fixtures runs on every deploy.
- Sign-in is by email, and the session lives in an HttpOnly cookie.
- While a reader is signed in, the chat page also offers the archive tools to agents in the browser through WebMCP, in beta.
React assistant-ui Python Node AWS Lambda Amazon Bedrock MCP Amazon S3 Amazon CloudFront
Activity
1,428 commits (921 with Claude, 194 with another agent, 313 by me), the first on Apr 7, 2026.
The latest weeks with activity
-
Week of Oct 19, 2026 36 commits, all with Claude
- Blog round: the 2014-12-21 posts have their own addresses now
- Blog round: writes on (plan step 5)
- Accept the abandoned status from Things I've Built (#83)
33 more commits
-
Week of Oct 12, 2026 34 commits (14 with Claude, 14 with another agent, 6 by me)
- Corpus gate: things resolve as thing-<id>, members links are a floor
- Ingest Things I've built from thingelstad.xyz
- Verify routing receipts across CloudFront key normalization
31 more commits
-
Week of Oct 5, 2026 42 commits (41 with Claude, 1 by me)
- Move Thingy's fast model to Haiku 5.5 (#75)
- Prettier: wrap the Fresh posts blurb (#34)
- Sync MCP surface 2.6.0: fetch_page reads only Jamie's sites (#33)
39 more commits
-
Week of Sep 28, 2026 184 commits (172 with Claude, 11 with another agent, 1 by me)
- Archive issue 352 from WT Builder
- Fix redesign QA findings in sign-in, citations, and accessibility
- Merge the Felt & Tangerine static pages
181 more commits
All activity, week by week. Who made each commit is from its author and co-author lines.
Sources and evidence
Observed daily from GitHub, sitemaps, feeds, the Internet Archive, and Tinylytics. Evidence never sets a status.
-
jthingelstad/thingy.thingelstad.com implementation
Thingy — the standalone web home for Jamie Thingelstad's archive agent: a query surface over the Studio corpus, with a web app and a Discord bridge.
- Repository created Jun 3, 2026 (a development record, not a launch date)
- TypeScript, JavaScript, CSS
- Latest commit Oct 22, 2026; 199 commits on main between Jul 1, 2026 and Oct 23, 2026
- Observed Oct 23, 2026
-
jthingelstad/librarian-thing implementation
Studio — the brain behind Jamie Thingelstad's publishing: capture, research, the editorial source of truth, the production pipeline, and the authoring agents. Downstream surfaces (blog, newsletter, podcast, Thingy) consume what it produces.
- Repository created Jun 3, 2026 (a development record, not a launch date)
- Python, TypeScript, JavaScript
- Latest commit Oct 23, 2026; 292+ commits on main between Jul 1, 2026 and Oct 23, 2026
- Observed Oct 23, 2026
-
thingy.thingelstad.com/ website
- First archived Oct 12, 2026 by the Internet Archive (existence evidence, not a launch date)
- Sitemap: 4 pages
- 1,317 page views from Oct 1, 2025 to Sep 30, 2026, counted by Tinylytics
- Observed Oct 18, 2026
-
thingy.thingelstad.com/about/ reference
-
thingy.thingelstad.com/connect/ reference
-
www.thingelstad.com/2026/06/07/thingy-evolved.html reference
Commits and publications per month, last twelve months.
Connections
-
Thingy answers from Weekly Thing
Thingy launched with the new Weekly Thing website in May 2026 and answers from every issue of the newsletter. Source
-
Thingy answers from Jamie Thingelstad blog
In June 2026 I built a semantic archive of my blog so Thingy could search it alongside the newsletter. Source
-
Thingy answers from Another Thing
Thingy searches the Another Thing podcast and its transcripts. Source
-
Thingy indexes Things I’ve built
Librarian snapshots the registry’s things.json into the Weekly Thing corpus, so Thingy and MCP clients can answer questions about my projects (sources thing-<id> and thing-index). Source
-
Thingy receives issues from WT Builder
After each issue publishes, WT Builder commits the issue text into the Librarian repository so Thingy can retrieve and cite it. Source
-
Things I’ve built publishes a catalog for Thingy
The registry is published as things.json and llms.txt so Thingy can answer questions about my projects without this site running a model. Source
-
Weekly Thing GPT was succeeded by Thingy
When Thingy launched in May 2026, I compared the two. The GPT “was grade school level. Thingy is much smarter!” Source
History
-
milestone
Thingy called complete
I call Thingy complete after adding photos and shared conversations. Source
-
milestone
Thingy Evolved
Thingy moves to its own site and learns my blog and Another Thing as well as the Weekly Thing. Source
-
development
Thingy: recorded development begins
The earliest commit in this repository is a development record; the project or idea may predate it. Source
-
launch
New Weekly Thing site and Thingy
I build a new Weekly Thing website that puts all nine years and 345 issues of the archive on show, with Thingy as its librarian. Source
-
development
Librarian: recorded development begins
The earliest commit in Librarian, the archive API behind Thingy, is a development record; the project or idea may predate it. Source