Build knowledge from your files

Start with a file you have questions about. Find an answer, check the evidence, and save what you learn as a note you can build on.

Before you start

Bring a short PDF or Markdown file to Mempipe. A Space is where you keep related files and notes together.

This walkthrough uses the in-app agent. You’ll need an API key from one of the offered providers, who charges for model usage. You can also read and search the file yourself, then write your own Markdown note.

Explore a question and save what you learn

1. Open a Space and add your file.

   Open an existing Space, or choose New space… from the workspace switcher in the top bar. In Files, choose Upload file or drag your document into the file list. Processing continues after upload; wait until the file is ready to search.

2. Set up the agent.

   Open the right-hand Agent panel. Choose your provider, then open Model & API key in the chat composer to enter your model and matching key.

3. Ask a question.

   Replace the filename and question with your own:

   Read my-document.pdf. What deadline does it give for submitting a response? Cite the supporting passage. If the document does not say, tell me instead of guessing.

   Keep the Space open while the agent works.

4. Check the answer.

   Open a citation and read the passage in context. For a PDF, check the original view when the layout matters. Ask a follow-up, such as “Are there exceptions to this deadline?”, and check that evidence too.

5. Save what matters.

   Choose a new filename and ask:

   Save the deadline and exceptions we checked in response-notes.md. Include the source citations and open questions. Ask before changing an existing note. Keep the original file unchanged.

   Open the saved note in Files and check its contents and citations. You can also write a Markdown note yourself and upload it.

Find evidence yourself

Open Search and enter a distinctive word or phrase from your file. Open a result and read the surrounding passage to check a claim or explore something your note has not answered.

Build on the note

Return to the same note when another question comes up. Edit it yourself or ask the agent:

Read response-notes.md and the original file. Does the deadline change if a submission needs corrections? Cite the evidence, then update the note. Preserve useful findings and keep unanswered questions visible.

Review the saved changes. You now have a starting point for your next question.

If something gets in the way

• No note appears: ask the agent to save it to the filename you chose, then check Files.
• Processing, search-readiness, or stale-result message: wait and try again. If processing failed, check Pipeline → Space Activity and include the filename and error when asking for help.
• Search finds nothing: check the Space and filters, then try a phrase you can see in the file. No results does not prove there is no answer.
• Provider or key error: check Model & API key. Never paste your key into chat or a support request.
• Missing or unsupported citation: ask for the exact source passage. Treat the claim as unverified until you find evidence.

Keep going

Build and maintain a wiki as related notes grow, or connect your own agent to use what you know in another tool.