Rich block editor for developers
A block editor with Markdown and slash commands
Write anything without fighting the editor.
Everything debugging sessions and design discussions throw at you fits in one note: headings, checklists, tables, images and PDFs, with slash commands instead of menus.
Headings, lists, checklists, quotes, tables and dividers
Pasted Markdown that arrives as formatted text, and export back out to it
Images, audio and PDFs dropped straight into the note
Slash commands, drag handles and note to note links
Read the PDF where you write about it
Page through a document and take notes on it in the same place.
Structure without the menu hunt
Slash commands drop a table, a checklist or a divider where the cursor is.
Nothing is ever really deleted
Version history keeps earlier drafts of every note you write.
Every paragraph is a block
Move a section somewhere else without selecting a single word.
Markdown in and Markdown out
Paste it and it arrives formatted, export it and it leaves the same way.
Link one note to another
Mention a note as you write and both ends of the link stay live.
// results
Three bugs in the workflow, closed
No feature tour. What changes when your runbooks can be queried instead of grepped.
1.
You fixed this bug in March and are debugging it again from scratch.
Stop solving the same bug twice
Describe the symptom in search and get the note where you already worked it out.
2.
The decision lives in a Slack thread that scrolled away.
Keep decisions where you can defend them
Ask what you decided about a service and get the note, the date and the reasoning.
3.
The AI tool wants your notes on its server, and you want them on disk.
Point the AI at your own stack
Bring your own key, or run a local model through Ollama, and keep the workspace on disk.
// usage
What that looks like for developers
Three points in a sprint where the tool earns its slot.
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.
// faq
Questions Before You Install It
The rest of them live in the help center.
- Can I run the AI locally?
- Yes. Grape connects to Ollama and LM Studio as well as OpenAI, Anthropic, Google, Groq, DeepSeek, Grok and OpenRouter, and you can add any OpenAI compatible endpoint yourself.
- How does it handle technical notes?
- Inline code, tables, checklists, Markdown paste that keeps formatting, and export back out to Markdown when you want the note somewhere else.
- What is Grape, in one paragraph?
- Grape is a note app for Mac, Windows, Linux, iPhone and Android with AI built into the middle of it rather than bolted on the side. You write, record and collect things the normal way, and then you can search by meaning, ask questions about your own notes, and turn any note into a summary, a set of flashcards, a quiz or a mind map.
- What makes it different from other note apps?
- Most note apps treat AI as an extra panel. In Grape the agent works on your workspace: it can read, create, edit, move, tag and delete notes, and every answer points back to the note it came from. Semantic search, voice transcription, flashcards, quizzes, mind maps and the drawing canvas all live inside the editor rather than in separate tools.
- Where do my notes actually live?
- On your device, in a local database, and you can choose where that file sits. Nothing needs to leave your machine for the app to work. If you turn on sync with a Sync or Pro plan, your notes are also stored in the cloud so your devices can stay in step. On Lifetime they sync through your own Dropbox or Google Drive instead, and Grape never sees them.
- Do I need an account to use it?
- No. Download the app and start writing. You only need an account for the paid plans, which is where cross device sync and built in AI come in.
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.