Docs
Add documents to Knowledge
Everything AgOS answers from lives in Knowledge. Here is how to fill it, and what makes a document easy to answer from.
What AgOS can read
Upload PDF, DOCX, PPTX, Markdown and plain text files, or write pages directly in Knowledge. Long documents are split into sections when they are indexed, so answers can cite the exact passage.
Spaces and pages
Knowledge is organized in spaces. Each space has members who can view, edit or administer it, and only members can see what is inside. A page can be restricted to named people, and the restriction carries down to the pages beneath it.
Pages keep their earlier versions. If a change turns out wrong, go back to the version before it.
Other ways in
- [GitHub](/integrations/github): connect a repository and its Markdown docs become pages, while issues, pull requests and wiki pages become sources AgOS can cite.
- [MCP clients](/integrations/mcp): Claude, ChatGPT and other MCP clients can save Markdown straight into Knowledge.
- From Notion or a wiki: export pages as Markdown and upload them.
What makes a good source
AgOS answers from what a document says, so documents that say things plainly give better answers:
- One topic per document or page, with headings for each part.
- Facts written out: "refunds within 30 days of the start date", not "see the usual terms".
- A date or version on anything that changes, such as price lists and policies.
- The current version only. When a policy changes, update the page rather than adding a second one.
When AgOS cannot answer a question, the question is recorded. The ones that keep coming up are grouped into suggestions for the page your team should write next.
Ask your company a question.
Create an account, add three to five documents, and ask.