@vercel/geistdocs 1.3.1 → 1.4.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (48) hide show
  1. package/dist/cli/index.js +1 -1
  2. package/dist/config.d.ts +6 -0
  3. package/dist/config.d.ts.map +1 -1
  4. package/dist/routes/agents.d.ts.map +1 -1
  5. package/dist/routes/agents.js +14 -29
  6. package/dist/routes/discovery.d.ts +14 -0
  7. package/dist/routes/discovery.d.ts.map +1 -0
  8. package/dist/routes/discovery.js +74 -0
  9. package/dist/routes/mcp.d.ts +26 -0
  10. package/dist/routes/mcp.d.ts.map +1 -0
  11. package/dist/routes/mcp.js +31 -0
  12. package/dist/source.d.ts +1 -1
  13. package/dist/source.d.ts.map +1 -1
  14. package/dist/source.js +4 -1
  15. package/docs/agents.md +44 -0
  16. package/docs/llms.txt +2965 -0
  17. package/docs/manifest.json +194 -0
  18. package/docs/pages/agent-readiness.md +141 -0
  19. package/docs/pages/ask-ai.md +143 -0
  20. package/docs/pages/configuration.md +278 -0
  21. package/docs/pages/deployment.md +53 -0
  22. package/docs/pages/edit-on-github.md +53 -0
  23. package/docs/pages/env.md +62 -0
  24. package/docs/pages/feedback.md +91 -0
  25. package/docs/pages/getting-started.md +116 -0
  26. package/docs/pages/index.md +99 -0
  27. package/docs/pages/internationalization.md +124 -0
  28. package/docs/pages/llms-txt.md +88 -0
  29. package/docs/pages/md.md +84 -0
  30. package/docs/pages/migration.md +376 -0
  31. package/docs/pages/open-in-chat.md +82 -0
  32. package/docs/pages/provider.md +76 -0
  33. package/docs/pages/proxy.md +180 -0
  34. package/docs/pages/rss.md +110 -0
  35. package/docs/pages/syntax.md +413 -0
  36. package/docs/pages/theme-aware-image.md +59 -0
  37. package/docs/pages/versioned-docs.md +230 -0
  38. package/docs/sitemap.md +25 -0
  39. package/package.json +12 -2
  40. package/styles.css +174 -0
  41. package/template/AGENTS.md +10 -3
  42. package/template/app/[lang]/.well-known/mcp.json/route.ts +8 -0
  43. package/template/content/docs/agent-readiness.mdx +44 -8
  44. package/template/content/docs/configuration.mdx +1 -0
  45. package/template/content/docs/index.mdx +1 -1
  46. package/template/content/docs/llms-txt.mdx +1 -1
  47. package/template/content/docs/migration.mdx +12 -2
  48. package/template/package.json +1 -1
@@ -0,0 +1,194 @@
1
+ {
2
+ "description": "Versioned Geistdocs documentation bundled with the @vercel/geistdocs package for offline agent use.",
3
+ "files": {
4
+ "agents": "agents.md",
5
+ "llms": "llms.txt",
6
+ "pages": "pages/*.md",
7
+ "sitemap": "sitemap.md"
8
+ },
9
+ "name": "@vercel/geistdocs",
10
+ "pages": [
11
+ {
12
+ "description": "Learn how Geistdocs packages the CLI, runtime, and template for documentation sites",
13
+ "path": "pages/index.md",
14
+ "source": "apps/template/content/docs/index.mdx",
15
+ "summary": "Geistdocs is a packaged documentation system for creating Next.js and Fumadocs sites with shared runtime features.",
16
+ "title": "Overview",
17
+ "type": "overview",
18
+ "url": "/docs"
19
+ },
20
+ {
21
+ "description": "Create a Geistdocs project and start writing documentation",
22
+ "path": "pages/getting-started.md",
23
+ "source": "apps/template/content/docs/getting-started.mdx",
24
+ "summary": "Create a Geistdocs project, run it locally, and edit your first documentation page.",
25
+ "title": "Getting Started",
26
+ "type": "guide",
27
+ "url": "/docs/getting-started"
28
+ },
29
+ {
30
+ "description": "Learn about the environment variables used in Geistdocs",
31
+ "path": "pages/env.md",
32
+ "source": "apps/template/content/docs/env.mdx",
33
+ "summary": "Environment variables required by Geistdocs for AI chat, proxy mode, and production URL configuration.",
34
+ "title": "Environment Variables",
35
+ "type": "reference",
36
+ "url": "/docs/env"
37
+ },
38
+ {
39
+ "description": "Learn how to deploy your Geistdocs site to Vercel",
40
+ "path": "pages/deployment.md",
41
+ "source": "apps/template/content/docs/deployment.mdx",
42
+ "summary": "Deploy your Geistdocs site to Vercel from the dashboard with the correct project settings.",
43
+ "title": "Deploy to Vercel",
44
+ "type": "guide",
45
+ "url": "/docs/deployment"
46
+ },
47
+ {
48
+ "description": "Migrate a Fumadocs or custom Geist docs site to package-backed Geistdocs",
49
+ "path": "pages/migration.md",
50
+ "source": "apps/template/content/docs/migration.mdx",
51
+ "summary": "Move an existing documentation site to @vercel/geistdocs while keeping local content, routing, middleware behavior, and AI-readable surfaces intact.",
52
+ "title": "Migration guide",
53
+ "type": "guide",
54
+ "url": "/docs/migration"
55
+ },
56
+ {
57
+ "description": "Configure a Geistdocs site through local adapter files and package APIs",
58
+ "path": "pages/configuration.md",
59
+ "source": "apps/template/content/docs/configuration.mdx",
60
+ "summary": "Configure site metadata, navigation, AI features, page actions, translations, and local adapters.",
61
+ "title": "Configuration",
62
+ "type": "reference",
63
+ "url": "/docs/configuration"
64
+ },
65
+ {
66
+ "description": "Learn about the supported markdown syntax and formatting options",
67
+ "path": "pages/syntax.md",
68
+ "source": "apps/template/content/docs/syntax.mdx",
69
+ "summary": "Supported MDX syntax including text formatting, code blocks, line highlighting, and Mermaid diagrams.",
70
+ "title": "Syntax",
71
+ "type": "reference",
72
+ "url": "/docs/syntax"
73
+ },
74
+ {
75
+ "description": "The root provider component that handles notifications, search and analytics",
76
+ "path": "pages/provider.md",
77
+ "source": "apps/template/content/docs/provider.mdx",
78
+ "summary": "The root provider component that wraps your application to handle toast notifications, search, and analytics.",
79
+ "title": "Geistdocs Provider",
80
+ "type": "reference",
81
+ "url": "/docs/provider"
82
+ },
83
+ {
84
+ "description": "Configure multiple documentation versions with package-backed source helpers",
85
+ "path": "pages/versioned-docs.md",
86
+ "source": "apps/template/content/docs/versioned-docs.mdx",
87
+ "summary": "Use createVersionedSources to configure stable, pre-release, or host-based documentation versions.",
88
+ "title": "Versioned docs",
89
+ "type": "guide",
90
+ "url": "/docs/versioned-docs"
91
+ },
92
+ {
93
+ "description": "Add custom request logic while keeping Geistdocs markdown negotiation in the package",
94
+ "path": "pages/proxy.md",
95
+ "source": "apps/template/content/docs/proxy.mdx",
96
+ "summary": "Configure createProxy with before and after hooks, markdown route mappings, and a static Next.js matcher.",
97
+ "title": "Proxy and markdown routes",
98
+ "type": "reference",
99
+ "url": "/docs/proxy"
100
+ },
101
+ {
102
+ "description": "Access documentation pages as raw Markdown by appending .md or .mdx to any URL",
103
+ "path": "pages/md.md",
104
+ "source": "apps/template/content/docs/md.mdx",
105
+ "summary": "Access any documentation page as raw Markdown by appending .md or .mdx to the URL for AI tool consumption.",
106
+ "title": ".md Extension",
107
+ "type": "conceptual",
108
+ "url": "/docs/md"
109
+ },
110
+ {
111
+ "description": "Expose agents.md and MCP discovery files that help AI agents discover and use your docs site",
112
+ "path": "pages/agent-readiness.md",
113
+ "source": "apps/template/content/docs/agent-readiness.mdx",
114
+ "summary": "Generate /agents.md and /.well-known/mcp.json from Geistdocs config so agents can find docs, Markdown surfaces, API specs, and MCP endpoints.",
115
+ "title": "Agent readiness",
116
+ "type": "guide",
117
+ "url": "/docs/agent-readiness"
118
+ },
119
+ {
120
+ "description": "An AI-powered chat assistant that helps users understand your documentation with context-aware responses",
121
+ "path": "pages/ask-ai.md",
122
+ "source": "apps/template/content/docs/ask-ai.mdx",
123
+ "summary": "An AI-powered chat assistant with context-aware search, persistent history, and suggested prompts for your documentation.",
124
+ "title": "Ask AI",
125
+ "type": "conceptual",
126
+ "url": "/docs/ask-ai"
127
+ },
128
+ {
129
+ "description": "Allow readers to contribute directly by editing documentation pages on GitHub",
130
+ "path": "pages/edit-on-github.md",
131
+ "source": "apps/template/content/docs/edit-on-github.mdx",
132
+ "summary": "A direct link on every documentation page that lets readers propose changes through GitHub pull requests.",
133
+ "title": "Edit on GitHub",
134
+ "type": "integration",
135
+ "url": "/docs/edit-on-github"
136
+ },
137
+ {
138
+ "description": "Collect user feedback with an interactive emotion-based widget that creates GitHub Issues",
139
+ "path": "pages/feedback.md",
140
+ "source": "apps/template/content/docs/feedback.mdx",
141
+ "summary": "An interactive feedback widget that collects user sentiment and creates structured GitHub Issues automatically.",
142
+ "title": "Feedback",
143
+ "type": "integration",
144
+ "url": "/docs/feedback"
145
+ },
146
+ {
147
+ "description": "Add multi-language support to your documentation site",
148
+ "path": "pages/internationalization.md",
149
+ "source": "apps/template/content/docs/internationalization.mdx",
150
+ "summary": "Serve documentation in multiple languages with automatic translation via the Geistdocs CLI and Fumadocs routing.",
151
+ "title": "Internationalization",
152
+ "type": "guide",
153
+ "url": "/docs/internationalization"
154
+ },
155
+ {
156
+ "description": "A single file containing all your documentation in plain text for AI consumption",
157
+ "path": "pages/llms-txt.md",
158
+ "source": "apps/template/content/docs/llms-txt.mdx",
159
+ "summary": "A single endpoint that returns all documentation as plain Markdown text following the llms.txt standard.",
160
+ "title": "llms.txt",
161
+ "type": "conceptual",
162
+ "url": "/docs/llms-txt"
163
+ },
164
+ {
165
+ "description": "Allow users to continue conversations in their preferred AI chat platform with a single click",
166
+ "path": "pages/open-in-chat.md",
167
+ "source": "apps/template/content/docs/open-in-chat.mdx",
168
+ "summary": "Transfer documentation context to AI chat platforms like ChatGPT, Claude, Cursor, and v0 with a single click.",
169
+ "title": "Open in Chat",
170
+ "type": "conceptual",
171
+ "url": "/docs/open-in-chat"
172
+ },
173
+ {
174
+ "description": "Keep users updated with an automatically generated RSS feed for your documentation",
175
+ "path": "pages/rss.md",
176
+ "source": "apps/template/content/docs/rss.mdx",
177
+ "summary": "An automatically generated RSS 2.0 feed that keeps users informed when documentation is published or updated.",
178
+ "title": "RSS",
179
+ "type": "conceptual",
180
+ "url": "/docs/rss"
181
+ },
182
+ {
183
+ "description": "Display different images based on the user's light or dark theme preference",
184
+ "path": "pages/theme-aware-image.md",
185
+ "source": "apps/template/content/docs/theme-aware-image.mdx",
186
+ "summary": "A component that swaps images based on the active theme, built on top of Next.js Image.",
187
+ "title": "Theme-Aware Image",
188
+ "type": "reference",
189
+ "url": "/docs/theme-aware-image"
190
+ }
191
+ ],
192
+ "source": "apps/template/content/docs",
193
+ "version": "1.4.1"
194
+ }
@@ -0,0 +1,141 @@
1
+ ---
2
+ title: Agent readiness
3
+ description: Expose agents.md and MCP discovery files that help AI agents discover and use your docs site
4
+ type: guide
5
+ summary: Generate /agents.md and /.well-known/mcp.json from Geistdocs config so agents can find docs, Markdown surfaces, API specs, and MCP endpoints.
6
+ url: /docs/agent-readiness
7
+ source: apps/template/content/docs/agent-readiness.mdx
8
+ related:
9
+ - /docs/llms-txt
10
+ - /docs/md
11
+ - /docs/proxy
12
+ ---
13
+
14
+ # Agent readiness
15
+
16
+ Geistdocs can generate `/agents.md` and `/.well-known/mcp.json` discovery files from your site config. These files tell AI agents where your docs live and which machine-readable integration surfaces your product declares.
17
+
18
+ Review this Geistdocs site's `/agents.md` and `/.well-known/mcp.json` files. Check whether they list the product description, documentation links, `llms.txt`, `sitemap.md`, OpenAPI specs, and MCP servers accurately.
19
+
20
+ ## What it provides
21
+
22
+ The generated `/agents.md` file gives agents a stable starting point before they crawl the rest of your documentation. The optional `/.well-known/mcp.json` route advertises configured MCP servers without running an MCP server inside Geistdocs.
23
+
24
+ It can include:
25
+
26
+ - Product name, description, category, audience, and use cases
27
+ - Human-readable docs entry points
28
+ - `/llms.txt` for full documentation context
29
+ - `/sitemap.md` for semantic navigation
30
+ - Page-level Markdown guidance for `.md` and `.mdx` URLs
31
+ - OpenAPI, authentication, scopes, rate limit, and error docs when configured
32
+ - MCP manifests and server URLs when configured
33
+ - Additional links and agent instructions
34
+
35
+ ## Add the route
36
+
37
+ Generated projects include a thin App Router adapter:
38
+
39
+ ```ts title="app/[lang]/agents.md/route.ts"
40
+ import { createAgentsRoute } from "@vercel/geistdocs/routes/agents";
41
+ import { config } from "@/lib/geistdocs/config";
42
+
43
+ export const { GET, generateStaticParams, revalidate } = createAgentsRoute({
44
+ config,
45
+ });
46
+ ```
47
+
48
+ Because the route is under `[lang]`, the Geistdocs proxy can serve `/agents.md` through the default language route.
49
+
50
+ Generated projects also include a thin adapter for MCP discovery:
51
+
52
+ ```ts title="app/[lang]/.well-known/mcp.json/route.ts"
53
+ import { createMcpManifestRoute } from "@vercel/geistdocs/routes/mcp";
54
+ import { config } from "@/lib/geistdocs/config";
55
+
56
+ export const { GET, generateStaticParams, revalidate } = createMcpManifestRoute({
57
+ config,
58
+ });
59
+ ```
60
+
61
+ The MCP discovery route returns `404` until you configure `agent.mcp.servers`, so generated sites do not claim MCP support by default.
62
+
63
+ When configured, `/.well-known/mcp.json` returns the declared MCP servers:
64
+
65
+ ```json
66
+ {
67
+ "name": "My Product",
68
+ "description": "My Product helps teams build and deploy applications.",
69
+ "servers": [
70
+ {
71
+ "name": "My Product MCP",
72
+ "url": "https://example.com/api/mcp",
73
+ "description": "Use product tools through MCP."
74
+ }
75
+ ]
76
+ }
77
+ ```
78
+
79
+ ## Configure agent metadata
80
+
81
+ Add agent-readiness metadata in `geistdocs.tsx`, then pass it through `defineConfig` in `lib/geistdocs/config.tsx`.
82
+
83
+ ```tsx title="geistdocs.tsx"
84
+ import type { GeistdocsAgentReadinessConfig } from "@vercel/geistdocs/config";
85
+
86
+ export const agent = {
87
+ product: {
88
+ name: "My Product",
89
+ description: "My Product helps teams build and deploy applications.",
90
+ category: "Developer tools",
91
+ audience: ["Frontend developers", "Platform teams"],
92
+ useCases: ["Deploy applications", "Manage domains", "Inspect logs"],
93
+ },
94
+ api: {
95
+ openApiUrl: "https://api.example.com/openapi.json",
96
+ openApiSpecs: [
97
+ {
98
+ label: "Admin API OpenAPI specification",
99
+ url: "https://api.example.com/admin/openapi.json",
100
+ description: "Administrative API operations.",
101
+ },
102
+ ],
103
+ authDocsUrl: "/docs/authentication",
104
+ scopesDocsUrl: "/docs/scopes",
105
+ rateLimitsUrl: "/docs/rate-limits",
106
+ errorsUrl: "/docs/errors",
107
+ },
108
+ mcp: {
109
+ manifestUrl: "/.well-known/mcp.json",
110
+ servers: [
111
+ {
112
+ name: "My Product MCP",
113
+ url: "https://example.com/api/mcp",
114
+ description: "Use product tools through MCP.",
115
+ },
116
+ ],
117
+ },
118
+ links: [
119
+ {
120
+ label: "Support",
121
+ href: "https://example.com/support",
122
+ description: "Get help from the product team.",
123
+ },
124
+ ],
125
+ } satisfies GeistdocsAgentReadinessConfig;
126
+ ```
127
+
128
+ ```tsx title="lib/geistdocs/config.tsx"
129
+ import { agent } from "@/geistdocs";
130
+
131
+ export const config = defineConfig({
132
+ // ...
133
+ agent,
134
+ });
135
+ ```
136
+
137
+ ## Keep it honest
138
+
139
+ Only list OpenAPI specs, authentication flows, or MCP servers that actually exist. Geistdocs validates new `openApiSpecs` entries and MCP servers rendered by `/.well-known/mcp.json` as absolute `http` or `https` URLs or root-relative paths. Existing `/agents.md` URL fields keep the same URL handling as previous versions. Geistdocs makes product capabilities discoverable, but it does not create APIs or MCP tools for you.
140
+
141
+ Use `/agents.md` and `/.well-known/mcp.json` with [llms.txt](/docs/llms-txt), [.md extension](/docs/md), and [Proxy and markdown routes](/docs/proxy) to give agents a complete discovery path.
@@ -0,0 +1,143 @@
1
+ ---
2
+ title: Ask AI
3
+ description: An AI-powered chat assistant that helps users understand your documentation with context-aware responses
4
+ type: conceptual
5
+ summary: An AI-powered chat assistant with context-aware search, persistent history, and suggested prompts for your documentation.
6
+ url: /docs/ask-ai
7
+ source: apps/template/content/docs/ask-ai.mdx
8
+ prerequisites:
9
+ - /docs/env
10
+ related:
11
+ - /docs/open-in-chat
12
+ - /docs/llms-txt
13
+ - /docs/configuration
14
+ ---
15
+
16
+ # Ask AI
17
+
18
+ The Ask AI feature provides an intelligent chat assistant built directly into your documentation. Users can ask questions about your docs and get instant, context-aware answers powered by AI. The assistant can search through your documentation, understand context, and provide helpful responses.
19
+
20
+ Help me configure Ask AI for this Geistdocs site. Check my AI prompt, suggestions, environment variables, and search route, then recommend improvements for the assistant experience.
21
+
22
+ ## How it works
23
+
24
+ The AI chat assistant is available in two ways:
25
+
26
+ ### 1. Per-Page Quick Access
27
+
28
+ Each documentation page has an "Ask AI about this page" button in the table of contents sidebar. When clicked, it:
29
+
30
+ 1. Opens the chat interface
31
+ 2. Pre-fills a prompt asking the AI to read the current page
32
+ 3. Allows users to ask specific questions about that page
33
+
34
+ ### 2. Global Chat Interface
35
+
36
+ Users can open the chat interface at any time by:
37
+
38
+ - Clicking the "Ask AI" button in the navbar
39
+ - Using the keyboard shortcut: `⌘I` (Mac) or `Ctrl+I` (Windows/Linux)
40
+
41
+ Once open, users can:
42
+
43
+ - Ask questions about any part of your documentation
44
+ - Upload files or images for context
45
+ - View AI-powered search results from your docs
46
+ - Get step-by-step guidance on complex topics
47
+
48
+ ## AI SDK dependency ownership
49
+
50
+ Geistdocs Ask AI is built on AI SDK v6. Generated projects install `ai` v6 and `@ai-sdk/react` v3, and `@vercel/geistdocs` owns the chat client, transport, and `createChatRoute` server behavior.
51
+
52
+ When a consumer app already uses the AI SDK outside Geistdocs, treat that as app code. Upgrade the app code to the installed AI SDK version or let the package manager install separate versions if needed. Do not fork Geistdocs chat internals or downgrade Ask AI to match unrelated app usage.
53
+
54
+ Most projects should not customize the chat transport. If you do customize `DefaultChatTransport.prepareSendMessagesRequest`, preserve `messages` in the returned request body. The AI SDK passes `messages` separately from `body`, and returning a custom `body` replaces the default request body.
55
+
56
+ ```ts
57
+ prepareSendMessagesRequest: ({ body, messages }) => ({
58
+ body: {
59
+ ...body,
60
+ messages,
61
+ currentRoute: pathname,
62
+ },
63
+ });
64
+ ```
65
+
66
+ ## Choose an AI mode
67
+
68
+ Ask AI can run in the default AI Gateway mode or through a Vertex-backed proxy.
69
+
70
+ ### Default AI Gateway mode
71
+
72
+ Use the default mode when the Geistdocs site should call the Vercel AI Gateway directly.
73
+
74
+ 1. Leave `GEISTDOCS_CHAT_PROXY_URL` unset.
75
+ 2. Set `AI_GATEWAY_API_KEY` for local development. Vercel sets this automatically for deployments that have AI Gateway access.
76
+ 3. Keep `NEXT_PUBLIC_VERCEL_PROJECT_PRODUCTION_URL` set to the site's production host, such as `docs.example.com` or `localhost:3000` for local development.
77
+
78
+ In this mode, Geistdocs uses the local `search_docs` tool during the AI SDK `streamText` loop.
79
+
80
+ ### Vertex-backed proxy mode
81
+
82
+ Use proxy mode when Ask AI should route model requests through a central Vertex-backed service instead of calling AI Gateway from each site.
83
+
84
+ 1. Deploy or use the central Geistdocs platform proxy that exposes `POST /vertex`.
85
+ 2. Configure the Vertex deployment to trust the Geistdocs platform Vercel project with Deployment Protection Trusted Sources.
86
+ 3. Set `GEISTDOCS_CHAT_PROXY_URL` on the Geistdocs site to the platform proxy URL, including `/vertex`:
87
+
88
+ ```txt
89
+ https://<geistdocs-platform-deployment>/vertex
90
+ ```
91
+
92
+ 4. Leave `GEISTDOCS_CHAT_PROXY_TOKEN` unset unless you are using a custom proxy that requires bearer authentication.
93
+
94
+ When `GEISTDOCS_CHAT_PROXY_URL` is set, Geistdocs searches local docs on the first user message, injects the current page and related docs into the final user message, forwards `{ messages, platform: "vercel" }` to the proxy, and streams the AI SDK UI stream response back to the browser.
95
+
96
+ The platform proxy forwards a Vercel OIDC token to Vertex in the `x-vercel-trusted-oidc-idp-token` header. The Vertex deployment should validate the caller through Trusted Sources; the Geistdocs site does not need a Vertex API key.
97
+
98
+ ## Features
99
+
100
+ ### Context-Aware Search
101
+
102
+ By default, the AI assistant includes a built-in `search_docs` tool that:
103
+
104
+ 1. Searches through your documentation content
105
+ 2. Finds relevant pages based on the user's question
106
+ 3. Shows source citations with links to the referenced pages
107
+ 4. Uses the content to provide accurate, contextual answers
108
+
109
+ When `GEISTDOCS_CHAT_PROXY_URL` is set, Geistdocs runs local documentation retrieval on the first user message before forwarding the request to the configured proxy. This gives proxy-backed services access to the current page and related local documentation without requiring them to read the site's source files directly.
110
+
111
+ ### Persistent Chat History
112
+
113
+ Conversations are automatically saved to the browser's IndexedDB, providing:
114
+
115
+ - Chat history that persists across page reloads
116
+ - Ability to continue previous conversations
117
+ - Option to start a new chat or clear history
118
+ - Offline access to past conversations
119
+
120
+ ### Interactive Features
121
+
122
+ - **Suggestions**: First-time users see suggested questions to get started
123
+ - **File Upload**: Users can attach files or images for context
124
+ - **Markdown Support**: Responses are formatted with proper Markdown rendering
125
+ - **Code Syntax Highlighting**: Code blocks in responses include syntax highlighting
126
+ - **Reasoning Display**: In development mode, view the AI's reasoning process
127
+
128
+ ### Mobile-Responsive
129
+
130
+ The chat interface adapts to different screen sizes:
131
+
132
+ - **Desktop**: Slides in from the right side as a sidebar panel
133
+ - **Mobile**: Opens as a bottom drawer.
134
+
135
+ ## Configuration
136
+
137
+ The environment variables `AI_GATEWAY_API_KEY` and `NEXT_PUBLIC_VERCEL_PROJECT_PRODUCTION_URL` must be set for the default AI Gateway mode. Set `GEISTDOCS_CHAT_PROXY_URL` to route Ask AI through a Vertex-backed proxy instead. You can read more in the [Environment Variables](/docs/env) section.
138
+
139
+ In default AI Gateway mode, Geistdocs uses `openai/gpt-4.1-mini` via the Vercel AI Gateway. In Vertex-backed proxy mode, the configured proxy controls the upstream model.
140
+
141
+ ## Suggested Prompts
142
+
143
+ You can customize the initial suggested prompts shown to users. These are configured in the Geistdocs configuration file, which you can read more about in the [Configuration](/docs/configuration) section.