"We talked about this. Where?"
You remember the decision. Someone said the invoice export should skip refunded orders, and everybody agreed. It was three months ago. Was it in a task description? A comment under the bug? A note you wrote after the call?
You open the project manager, search the task titles, find nothing. You open your notes app, search there, find half of it. Ten minutes later you're re-deciding something that was already decided.
Knowledge lives in three places
In a small team, what you know about a project is scattered across three kinds of text:
- Tasks — the title and the description, where the intent was written down.
- Comments — where the real discussion happened, and where the "actually, let's not do that" got buried.
- Notes — the decisions, context and meeting write-ups that aren't an action to take.
Most tools keep these apart. Tasks and comments live in the project manager, notes live in another app, and no single search sees all of them.
Notes next to the work
ProWoDo has notes built in. They're plain markdown, tied to a company or to a specific project, and they sit next to your tasks instead of in a separate workspace. The notes page lets you browse them by project and by tag, like a small vault.
But the part that changes the workflow isn't the page. It's that Claude can search all of it at once.
One question, three sources
ProWoDo's MCP server has a search_knowledge tool. It runs a full-text search across task titles and descriptions, task comments and notes in a single call, and returns the best matches first, each with a short snippet and a pointer to where it lives.
So you can just ask:
"Where did we decide how to handle refunded orders in the invoice export?"
Claude searches, finds a comment on the export bug and a note from the planning call, and tells you what each one says. If you want the full text, it opens the note or the task. You get the answer and the source, not a guess.
A few other things that work the same way:
"What do we know about the Stripe webhook retries?" — pulls the task, the comment thread and the note that mention it.
"Did I already write something about onboarding emails?" — before you create a duplicate note.
You can narrow any of these to a single project when the whole company is too noisy.
From a task to something you'll find later
Closed tasks are where knowledge goes to disappear. When a task has a discussion worth keeping, ask Claude to turn it into a note: it reads the task and its comments, writes a clean summary, and creates the note linked back to the original task. The decision now lives somewhere you'll actually search.
What it doesn't do
We'd rather tell you now than have you find out:
- The search is full-text, not semantic. It matches the words you use, so "refund" won't find a note that only says "chargeback". If a search comes back empty, try another word.
- Support tickets and their comments are not included.
- Snippets are short. For the full text, Claude opens the note or the task.
- Promoting a task to a note goes through Claude; there's no button for it in the app yet.
- The search bar on the notes page itself only searches notes. For the combined search across tasks, comments and notes, ask Claude.
Try it
Connect Claude to ProWoDo (about two minutes, see the MCP connector docs), write a note about a decision you made this week, then ask Claude where you decided it. If you use Claude Code, the prowodo-tasks plugin already knows how to search and write notes.
If you're weighing ProWoDo against a notes-first tool, our ProWoDo vs Notion comparison covers where each one fits.