Feature
Give each agent the documents it actually needs — and nothing else. Internal policies for the HR assistant. Product docs for the support drafter. Onboarding material for the customer guide.
The dream is obvious: give people a chat interface and let them ask useful questions about the information the organisation already has. Shared repositories, old conversations, investor context, CRM notes, policies.
The moment that gets real, the problem changes. Internal users should see one thing. External partners should see another. Some users should know that a file exists without being able to read it. "Please don't reveal confidential data" in a prompt is not a boundary — if the data is accessible, it leaks eventually.
Pinchy's knowledge base enforces the boundary before the model ever improvises: separate uploads, separate permissions, separate scopes. One agent, one scope, one job.
Pre-Built Templates
Every serious knowledge-base use case keeps coming back in customer calls. v0.4.0 ships them as agent templates — install one, point it at the right documents, give it to the right group.
The general-purpose document agent. Upload policies, guides, internal wikis — the agent answers, cites the source, and says so clearly when it doesn't know.
Reviews contracts and legal documents, extracts key clauses (termination, liability, indemnification, payment, renewal), flags unusual language, compares terms across agreements.
Screens applications against a role brief, ranks candidates, summarises qualifications. Cites the exact part of each CV it's drawing on.
Compares vendor proposals side-by-side. Scores against your requirements, highlights differences, pulls quoted language from each submission.
Checks documents against regulations or internal policy. Flags gaps, tracks which requirements are covered, cites the clause that made the call.
Walks new team members through internal docs, processes, and procedures. Scoped per group so each audience sees only what applies to them.
Templates are starting points — the tone, the instructions, the scope. Clone one, point it at a different document set, restrict it to another group, and you have a second agent without rebuilding anything.
Every knowledge-base entry is attached to one or more agents and governed by Pinchy's existing permission model. You don't maintain a second access-control system; it reuses the one you already configure for users, groups, and agents.
A document belongs to the agents that need it. The HR assistant and the support drafter don't share pools.
The same agent can behave differently for different user groups — internal vs external, team A vs team B — with the knowledge base scoped per group.
When an agent pulls from a document, the source is visible in the answer. No "the model told me so" — it's "page 3 of the onboarding guide said so".
Replace a document, and every agent referencing it picks up the new version. Policy rewrites don't need to touch the agent config.
Learn More