DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build a local knowledge base for team reference with Open Vetta

Put team documents into a local knowledge base the agent can use in later tasks.

Who it is forA team lead or researcher who keeps internal procedures, notes, and reference files and wants an agent to answer from them without sending them to a hosted service.

The problemOrganizational knowledge is spread across files, and general chat models do not know the team's own procedures.

The outcomeA local knowledge base the agent can draw on, with the source files kept in the local workspace.

What you need first

  • Download the desktop app for macOS, Windows, or Linux, or run from source with Bun 1.3+ and Node.js 20+
  • An API key for a supported provider, an OpenAI-compatible endpoint, or a local inference server (BYOK)
  • A local project folder or documents to work on

Steps

  1. Install the desktop app or run from source, then open a workspace for the team's documents.
  2. Create a local knowledge base and add the reference files that the team uses most.
  3. Ask the agent a question that depends on one of those files and check that its answer cites or matches the source.
  4. Install a reusable skill or scenario for the team's recurring method if one applies.

Prompt for your agent

Use the Open Vetta repo (openvetta/open-vetta) to create a local knowledge base from the files in <document-folder>. Ask it one question that only those files can answer and report the answer and the file it came from. Verify the answer against the source file by reading that file directly.

Caveat. The README confirms local knowledge bases but does not describe how they index files, so test retrieval accuracy on your own documents before depending on it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page