Use cases
One place for everything you’d otherwise lose.
Twinkle fits wherever you already save things. Three kinds of people get the most out of it. Everything below is what the product does today, and there’s a plain list of the ways in that aren’t built yet.
Builders & AI engineers
The repo you starred in spring, back when you need it.
You save the good stuff as you build: repos, threads, docs, a decision you know you’ll want to justify later. Then you’re mid-task in Cursor and that context is in a tab you closed, or in a starred list four hundred items long that you have never once reopened.
- Reads the readme, the issue thread and the discussion. Not just a title and a favicon
- Links a repo to the post arguing against it, and the note you left yourself
- Answers “what have I got on X?” by meaning, not by keyword
- Connects to Claude Code, Cursor, VS Code and Windsurf over MCP, to search and to save
search_knowledge("our auth flow")
ADR: switch to PKCE
GitHub: auth middleware
HN: thread on refresh tokens
answered from your saved knowledge
Researchers & writers
Thirty sources in, still knowing which one said it.
Articles, a couple of papers, a few threads, two long interviews. Each one made sense at the time. A month later you remember the claim perfectly and have no idea which source it came from.
- Summarises every save and links them by the people and ideas inside
- Answers “what have I read about X?” with the sources attached
- Runs a deep dive on any subject and files the result back into your library
- Surfaces things you saved weeks apart and had stopped connecting
ggml-org/llama.cpp
GitHubThe local LLM ecosystem doesn’t need Ollama
ArticleWalk home — the thing about evals
Voice memo4 saves connected by 1 shared subject
Collectors & curators
Taste, navigable — without filing any of it.
A lineup you saved to work out the clashes. A review you kept for one paragraph. A channel rather than a set. It adds up faster than any folder structure survives, and tags are a second job you did not want.
- Pulls the artists, labels, venues and works out of what you save
- Makes a vague memory findable — the thing about the AI-generated film at Tribeca
- Groups a subject without you naming it, and lets you rename it when it guesses wrong
- Keeps the whole thing private by default
Boiler Room
Saved the channel rather than a set, which turned out to be the right call.
From the transcript
Recorded live in Peckham
Set opens on a Gqom edit
Track IDs in the description
The real world
Not everything worth keeping has a URL.
A poster on a wall, a track playing somewhere, a thought on the walk home. All of this works today.
Photograph a flyer
It reads the poster, spots that it’s an event, and pulls out the date, venue and lineup. The photo becomes searchable by what’s printed on it.
Record a few seconds of a track
It fingerprints the audio, identifies the song, retitles the save as the artist and track, and adds links to hear it on Spotify or Apple Music.
Photograph a product
Vision reads the brand and the model, then finds the official page and keeps that one: an explanation of the product, with a buy link alongside when there is one.
Leave yourself a voice note
Transcribed and searchable, on the phone or in the browser. In a recorded conversation or meeting it separates who said what.
Getting it in
Directly, or from whatever you’re already in.
Working now
- Paste or drop a link, a file, or a note in the web app
- Camera and photo library on your phone — a flyer, a product, a whiteboard
- Record a voice note on either, and get the transcript back
- Your AI assistant, over MCP — it can search your library and save into it
- Any of the three ingest endpoints, with a token
Not built yet
- iOS share sheet, so Safari and every other app can send straight to Twinkle
- Paste a screenshot directly into the web app
- A forwarding address, for the newsletters worth keeping
- A browser extension
So you know what’s missing before you sign up. It isn’t a promise with a date on it.
Who it’s for
Made for people who save too much.
Builders & AI engineers
Starred repos you’ve never reopened. The thread where something got decided.
Researchers & writers
Thirty sources deep and no longer sure which one actually said the thing.
Collectors & curators
Music, film, everything you meant to come back to. Too much of it to file.
Questions
Putting it to work.
Do I need to use Twinkle a specific way?
No. Most people carry on as they were: pasting links, snapping photos, recording a note. Twinkle does the organising. The three above are who it suits best, not rules for using it.
Can Twinkle handle a messy, mixed library?
That’s exactly what it’s for. One library holds repos, papers, festival lineups, voice memos and photographed flyers side by side, and search works across all of it. Worth knowing how the connections behave: they are dense within a subject and sparse between unrelated ones, so a mixed library reads as several tight clusters rather than one web.
How far back can I find something?
As far back as you’ve saved. Search is by meaning, so you can describe something vaguely from months ago and Twinkle will surface it, along with the related things you saved around the same time.
Is this useful for work, or just personal stuff?
Both, in the same library. Developers connect it to their editor over MCP so their assistant can search everything they’ve saved and file new findings back mid-session.
What happens when I save something Twinkle doesn’t recognize?
It still captures the content, writes a summary and makes it searchable. The platform-specific extractors add extra detail for known sources, but anything with a URL, or any image, audio or note, is handled.