In beta testing

Answers from
your own files

Create a bloom: a small knowledge base for one project, team or product, built from folders on your computer. Ask about it in Claude Desktop and every answer shows the file it came from.

See how it works About the beta

No technical setup. If you can pick a folder, you can make a bloom.

Apollo program

Indexed
Updated 4 min ago
In Claude DesktopWhat did we commit to for the Apollo test schedule?

Integration testing finishes before the design review, using the dates in the current test plan.

1test-plan.docxp. 4
SyncingQ4 proposal
Cited in your answertest-plan.docx, p. 4

How it works

From download to your first cited answer in a few minutes.

  1. Step 1

    Install

    A one-click installer for macOS, with Windows to follow. Knowledge Bloom adds itself to your desktop assistant, so there's nothing to set up.

  2. Step 2

    Pick your folders

    Name a bloom in your own words, like "Apollo program" or "Q4 proposal", and pick the folders that belong to it. It updates as your files change.

  3. Step 3

    Ask

    Ask your assistant about the project. Each answer names the file it came from, and when nothing matches, Knowledge Bloom says so.

More answers, less searching

Company-wide search is too broad, and building your own takes a developer. A bloom holds one project's files, so your assistant looks only where the answer is.

Scoped

One bloom per project, team or product. Search covers what's relevant, not everything you've saved.

Local

Your files stay on your computer, and so does everything built from them. Nothing is uploaded to index them.

Nothing to set up

Install it, pick your folders and start asking. No technical skills needed.

Portable

Built for Claude Desktop, with ChatGPT desktop support planned. One bloom, whichever assistant you use.

Who it's for

People who juggle several bodies of work, like programs, clients or studies. Each one gets its own bloom, however many folders its files are spread across.

  • Engineers and product managers

    A bloom for each program

    Specs, test plans and meeting notes for each program in its own bloom, so an answer about one program doesn't draw on another.

    You ask

    “What's still open before the Atlas design review?”

    The answer

    Two items: the load test results and sign-off on the alerting plan. Both are due the week before the review.

    1review-notes.docxp. 2
  • Consultants

    A bloom for each client

    Proposals, contracts and working notes stay with the client they belong to. Ask about one client and the others' files stay out of it.

    You ask

    “What did Northwind agree to in the scope change?”

    The answer

    Adding its two regional offices to the audit, with the final report moved to 15 March.

    1scope-change-v3.pdfp. 1
  • Researchers

    A bloom for each study

    Papers, protocols and lab notes for each study in one place, found by what they say, not only by their file names.

    You ask

    “Which papers in the sleep study used wrist trackers?”

    The answer

    Three of them. The review lists each one with how long participants wore the tracker.

    1actigraphy-review.pdfp. 6

Your files stay on your computer

Your files, and everything Knowledge Bloom builds from them, stay on your computer. When you ask a question, the few excerpts that answer it are sent to Anthropic or OpenAI as part of your chat, the same as text you paste in yourself.

  • Encrypted at restA lost laptop doesn't expose what you've indexed.
  • No usage data unless you opt inTelemetry is off until you turn it on.
  • Read-onlyKnowledge Bloom reads your folders. It never changes or moves a file.
  • Delete means deleteRemove a bloom and all of its data in one step.

In beta testing

Knowledge Bloom is being tested by a small group of invited testers on macOS. It isn't available to download yet, and there's no sign-up for now.

Questions? Write to hello@knowledgebloom.ai.