Build knowledge agents without embeddings

Most knowledge agents start the same way. You pick a vector database, then build a chunking pipeline. You choose an embedding model, then tune retrieval parameters.

Weeks later, your agent answers a question incorrectly, and you have no idea which chunk it retrieved or why that chunk scored highest.

We kept seeing this pattern internally and for teams building agents on Vercel. The embedding stack works for semantic similarity, but it falls short when you need a specific value from structured data. The failure mode is silent: the agent confidently returns the wrong chunk, and you can't trace the path from question to answer.

That's why we tried something different. We replaced our vector pipeline with a filesystem and gave the agent . Our went from ~$1.00 to ~$0.25 per call, and the output quality improved. The agent was doing what it already knew how to do: read files, run , and navigate directories.bashgrepsales call summarization agent

So we open-sourced the , a production-ready version of this architecture built on Vercel.Knowledge Agent Template

The Knowledge Agent Template is an open source, file-system-based agent you can fork, customize, and deploy. Plug any source: GitHub repos, YouTube transcripts, documents (e.g., markdown files), or custom APIs. Ship it as a web chat app, a GitHub bot, a Discord bot, or all three at once.

The template is built on , , and . Deploy to Vercel in a single click, configure your sources, and start answering questions.Vercel SandboxAI SDKChat SDK

No vector database. No chunking pipeline. No embedding model.

Your agent uses , , and inside of isolated .grepfindcatVercel Sandboxes

Here's how it works:

Results are deterministic, explainable, and fast. When the agent gives a wrong answer, you open the trace and see: it ran , read , and pulled the wrong section. You fix the file or adjust the agent's search strategy. The whole debugging loop takes minutes.grep -r "pricing" docs/docs/plans/enterprise.md

Compare that to vectors. If the agent returns a bad chunk, you have to determine which chunk it retrieved, then figure out why it scored 0.82 and the correct one scored 0.79. The problem could be the chunking boundary, the embedding model, or the similarity threshold. With filesystem search, there is no guessing why it picked that chunk and no tuning retrieval scores in the dark. You're debugging a question, not a pipeline.

LLMs already understand filesystems. They've been trained on massive amounts of code: navigating directories, grepping through files, managing state across complex codebases. If agents excel at filesystem operations for code, they excel at them for anything. That's the insight behind the .filesystem and bash approach

You're not teaching the model a new skill; you're using the one it's best at. No embedding pipeline to maintain or vector DB to scale. Add a source, sync, and search.

Your agent has one knowledge base, one codebase, and one source of truth. Yet your engineers are scattered across Slack, your community spread across Discord, your bug reports buried in GitHub. A single agent that understands all three.

Chat SDK connects your knowledge agent to every platform your users are on. Import the adapters you need, point each one to the same agent pipeline, and your agent is live on any Chat SDK-supported platform.

Chat SDK Knowledge Agent example

Each adapter handles platform-specific concerns (e.g., authentication, event formats, messaging) while the agent itself stays unchanged. fires whenever the bot is mentioned, regardless of platform. The agent receives the message text, streams a response through the same filesystem-backed pipeline, and posts back to the thread.onNewMention

The template ships with GitHub and Discord adapters out of the box, and Chat SDK already supports Slack, Microsoft Teams, Google Chat, and more. See the for a full list of official and community adapters, or .adapter directorybuild your own adapter

The package provides tools that connect any AI SDK-powered agent or app to your knowledge base. Import the tools, point the client to your instance URL, and pass the tools to your agent to establish the connection.@savoir/sdk

If you plan to extend the SDK's capabilities and publish it, customize the package name from to your own.@savoir/sdk

The template also includes a smart complexity router. Every incoming question is classified by complexity and routed to the right model. Simple questions go to fast, cheap models. Hard questions go to powerful ones. Cost optimization happens automatically, with no manual rules.

Compatible with any AI SDK model provider via .Vercel AI Gateway

The template includes a full admin interface: usage stats, error logs, user management, source configuration, and content sync controls. No external observability needed.

There's also an AI-powered admin agent. You can ask it questions like: "what errors occurred in the last 24 hours", or "what are the common questions users ask". It will use internal tools (, , , and ) to provide answers directly. You debug your agent an agent.query_statsquery_errorsrun_sqlchartwith

You don't need a vector database, an embedding model, or a chunking pipeline to build a working knowledge agent. You need a filesystem, bash, and a way to put your agent where your users already are. Those are the primitives.

The Knowledge Agent Template wires them together so you can focus on what your agent knows rather than how it retrieves insights.

Read more

What the template does

File-based search with Vercel Sandbox

Chat SDK: one agent, every platform

Deep integration with AI SDK

Built-in admin tools

Get started

1. You add sources through the admin interface, and they're stored in Postgres

2. Content syncs to a snapshot repository via Vercel Workflow

3. When the agent needs to search, a Vercel Sandbox loads the snapshot

4. The agent's and tools execute file-system commandsbashbash_batch

5. The agent returns an answer with optional references