Documentation

Generate and maintain living documentation for your project — AI-assisted, richly formatted, indexed into the knowledge graph, and exportable in six formats.

Overview

Click 📚 Documentation in the sidebar to open the Documentation view. Forage maintains two independent documents per workspace:

Document	Audience	Typical content
👤 User Documentation	End users / business stakeholders	Plain-language features, benefits, and how-tos — no code or implementation detail
🔧 Technical Documentation	Developers	Architecture, key components, data models, APIs/interfaces, configuration, reference architecture

Switch between the two with the tabs at the top of the view. Each has its own content, its own AI generation, and its own export.

Generating with AI

Click Generate with AI on either tab to have Forage write a first draft from scratch. It builds context directly from your project's knowledge graph — the project summary (if you've generated one), file list, classes, functions, and graph statistics — so the draft reflects your actual codebase rather than a generic template.

User and Technical documentation use different system prompts under the hood:

User Documentation — written as a technical writer producing customer-facing docs: plain language, markdown headers, short paragraphs, focused on features and how-to.
Technical Documentation — written as a senior engineer: Overview, Architecture, Key Components, Data Models, APIs/Interfaces, Configuration, and Reference Architecture sections.

Generating replaces the current content for that document type. Generate early, then refine by hand or with the docs chat rather than regenerating repeatedly.

Editing

Both documents use a rich-text editor with a formatting toolbar: bold, italic, underline, heading levels and block formats, font, text color, and background color. Edit directly — there's no separate "edit mode," what you see is what gets saved and exported.

Asking the AI to edit

Each document has its own AI chat panel — "Ask the AI to edit or improve this document." Unlike Generate, this works with your existing content: ask it to expand a section, tighten the language, add a missing topic, or restructure part of the document, and it edits in place rather than replacing everything.

Exporting

Use the export menu to download either document as:

Format	Notes
TXT	Plain text, formatting stripped
Markdown (.md)	Converted from the rich-text content
HTML	Standalone file with styling included
DOCX	Opens directly in Microsoft Word
PDF	Print-formatted output
Google Docs	Creates a new Google Doc directly in your Drive

TXT, Markdown, HTML, DOCX, and PDF export entirely locally — no network request leaves your machine. Google Docs export is the exception: it requires a one-time Google OAuth setup. See Configuration → Google to enable it.

Knowledge graph integration

Whenever a document is saved or generated, its content is chunked and ingested into the knowledge graph as nodes with CONTAINS, NEXT_CHUNK, and REFERENCES edges. That means your documentation becomes part of what the AI chat and MCP ask tool can draw on when answering questions — a documented convention or decision is retrievable context, not a file nobody queries.

Documentation is also directly readable and writable by any connected MCP agent via two dedicated tools:

MCP tool	What it does
`get_documentation`	Fetch the User and/or Technical documentation for a workspace as plain text.
`update_documentation`	Replace a document's full content (Markdown in, rendered and re-ingested automatically).

This lets an external agent (AgentOS, Claude Code, Cursor, or any MCP client) keep your documentation up to date as part of its own workflow — e.g. "update the technical docs to reflect the new payment module" — without you switching to the Forage UI. See API Reference for the full tool list.