Web clipper for Chrome for developers
Clip the page. Keep it as a note.
A page worth keeping goes into Grape as a note, with the images and the source line, filed next to a pile of runbooks and notes. Ask it questions later the way you would ask anything else you wrote.
1Clip it where you are reading
2It is filed before you switch windows
Article, selection or bookmark, chosen from one panel
Title, folder and tags corrected before you save
Images downloaded into the note, so the clip outlives the page
A keyboard shortcut and a right click menu for clips that never open the panel
Three ways to take a page
The readable article, only the part you highlighted, or just the title and the link.
Filed before it lands
Pick the folder and the tags in the panel, or set a default once and never see it again.
The pictures come too
Grape downloads every image into the note, so it reads offline and after the page is gone.
It says where it came from
Site, author and date on one line under the title, with the original a click away.
Two keys and it is saved
One shortcut clips the page, another clips the selection, with no panel in between.
Nothing passes through a server
The page goes from the browser to the app on your machine, and nowhere else.
Results
Three things that stop being a problem
Feature lists are easy to write and hard to care about. This is what changes for developers.
Stop solving the same bug twice
Describe the symptom in search and get the note where you already worked it out.
Keep decisions where you can defend them
Ask what you decided about a service and get the note, the date and the reasoning.
Point the AI at your own stack
Bring your own key, or run a local model through Ollama, and keep the workspace on disk.
In practice
What that looks like for developers
A few moments in a normal week where the app earns its place.
Debugging
Write the symptom, the theory and the fix in one note, with the log you kept attached.
Architecture review
Record the conversation and keep the decision log next to the diagram.
New project
Keep the setup steps in a runbook that actually gets found again.
The rest of the app
What Else Grape Does
Every part of the app is built around the same idea: keep what you write, and hand it back when you need it.
AI Agent
Chat that reads your library and can act on it
Open
Memory
The agent remembers what you tell it
Open
Semantic search
Search that works on what you meant
Open
Voice and transcription
Meetings and lectures become searchable text
Open
Share to Grape
A page from the share sheet becomes a note
Open
Flashcards
Decks built from the notes you wrote
Open
Find it next time it breaks.
Runbooks, architecture decisions and the fix you worked out at midnight, in a local library you can search by meaning and keep offline.