|
13 | 13 | <section id="overview"> |
14 | 14 | <title>Overview</title> |
15 | 15 | <p>This FAQ addresses common issues and questions encountered when using AI Positron with |
16 | | - Oxygen desktop, Oxygen Content Fusion CMS or integrated in the WebAuthor with a third party |
| 16 | + Oxygen desktop, Oxygen Content Fusion CMS, or integrated in Web Author with a third-party |
17 | 17 | CMS. The guidance provided is based on real-world user experiences and technical support |
18 | 18 | interactions.</p> |
19 | 19 | </section> |
|
32 | 32 | <p>If you use a less capable LLM, AI Positron may not produce optimal results. The quality of responses is directly dependent on the LLM's capabilities.</p> |
33 | 33 |
|
34 | 34 | <p><b>Q: Why is my LLM choice important?</b></p> |
35 | | - <p>A: The LLM model is the most critical factor in AI Positron's performance. Many issues reported (poor response quality, hallucinations, slow performance) are related to LLM limitations rather than AI Positron itself. Ensure you're using a capable model.</p> |
| 35 | + <p>A: The LLM model is the most critical factor in AI Positron's performance. Many issues |
| 36 | + reported (poor response quality, hallucinations, slow performance) are related to LLM |
| 37 | + limitations rather than AI Positron itself. Ensure that you're using a capable model.</p> |
36 | 38 |
|
37 | 39 | <p><b>Q: What is a project context prompt and why do I need one?</b></p> |
38 | 40 | <p>A: A project context prompt is a set of instructions that describes your project's characteristics, terminology, style guidelines, and specific requirements. It helps the LLM generate more accurate and relevant responses tailored to your documentation standards. For detailed guidance, see <xref href="customizing_ai_positron_for_your_dita_xml_project.dita"/>.</p> |
|
44 | 46 | <p><b>Q: What does "Exceeded … allowed tokens …" error mean?</b></p> |
45 | 47 | <p>A: This error indicates that the LLM's context window is not large enough to process your file. Modern LLMs typically have about 200k tokens of context window and can process files up to approximately 40 kilobytes without issues. If you encounter this error:</p> |
46 | 48 | <ul> |
47 | | - <li>Break your content into smaller files</li> |
48 | | - <li>Use an LLM with a larger context window</li> |
49 | | - <li>Reduce the amount of content sent to the LLM in a single request</li> |
| 49 | + <li>Break your content into smaller files.</li> |
| 50 | + <li>Use an LLM with a larger context window.</li> |
| 51 | + <li>Reduce the amount of content sent to the LLM in a single request.</li> |
50 | 52 | </ul> |
51 | 53 | <p>This is a limitation of the LLM itself, not something AI Positron can fix.</p> |
52 | 54 |
|
|
59 | 61 |
|
60 | 62 | <p><b>Q: What should I do when I want to report a problem based on an interaction in the Chat |
61 | 63 | view?</b></p> |
62 | | - <p>A: Export your chat conversation (for AI Positron Desktop use the export action in the |
63 | | - "Actions" drop down menu, for AI Positron WebAuthor press "/" in the chat input and select |
| 64 | + <p>A: Export your chat conversation (for AI Positron Desktop, use the export action in the |
| 65 | + "Actions" drop-down menu; for AI Positron Web Author, type "/" in the chat input and select |
64 | 66 | "Export chat") and contact support with the exported JSON file.</p> |
65 | 67 | </section> |
66 | 68 |
|
|
75 | 77 | <title>Topic Checkout and Editing Issues</title> |
76 | 78 |
|
77 | 79 | <p><b>Q: Why do I get errors when using AI Positron without checking out the topic?</b></p> |
78 | | - <p>A: When Positron is used in a CMS integration and a topic is not checked out the add-on |
| 80 | + <p>A: When Positron is used in a CMS integration and a topic is not checked out, the add-on |
79 | 81 | cannot make changes to the opened document. Always check out your topic before using AI |
80 | 82 | Positron features.</p> |
81 | 83 |
|
82 | 84 | <p><b>Q: Why don't my changes appear until I refresh the browser?</b></p> |
83 | | - <p>A: In some scenarios of third party CMS integrations, Positron edits the topic source but |
84 | | - changes remain hidden until you refresh the browser. This is an integration issue between |
85 | | - the CMS and AI Positron. Open an issue with the CMS requesting better integration with AI |
86 | | - Positron.</p> |
| 85 | + <p>A: In some scenarios of third-party CMS integrations, AI Positron edits the topic source |
| 86 | + but changes remain hidden until you refresh the browser. This is an integration issue |
| 87 | + between the CMS and AI Positron. Open an issue with the CMS requesting better integration |
| 88 | + with AI Positron.</p> |
87 | 89 | </section> |
88 | 90 |
|
89 | 91 | <section id="preview_compare"> |
|
143 | 145 | <title>UI and Usability Issues</title> |
144 | 146 |
|
145 | 147 | <p><b>Q: Why don't my Favorites persist across sessions?</b></p> |
146 | | - <p>A: In certain CMS AI Positron WebAuthor integrations favorites only persist within the |
| 148 | + <p>A: In certain CMS AI Positron Web Author integrations, favorites only persist within the |
147 | 149 | current topic's session. To persist them across sessions, the CMS needs to implement APIs on |
148 | 150 | their side. Open an issue with the CMS requesting this feature.</p> |
149 | 151 |
|
150 | | - <p><b>Q: Why doesn't the History dropdown persist?</b></p> |
| 152 | + <p><b>Q: Why doesn't the History drop-down persist?</b></p> |
151 | 153 | <p>A: Similar to Favorites, the History dropdown requires CMS-side APIs to persist data.</p> |
152 | 154 |
|
153 | 155 | <p><b>Q: Why can't I upload files of type X?</b></p> |
|
172 | 174 | <p><b>Q: Why does AI Positron generate content that violates my DTD?</b></p> |
173 | 175 | <p>A: This depends on the LLM model quality. To improve results:</p> |
174 | 176 | <ul> |
175 | | - <li>Provide examples of correct structures in your project context prompt</li> |
176 | | - <li>Instruct the LLM to avoid specific mistakes it frequently makes</li> |
177 | | - <li>Create custom AI actions with more specific prompts</li> |
| 177 | + <li>Provide examples of correct structures in your project context prompt.</li> |
| 178 | + <li>Instruct the LLM to avoid specific mistakes it frequently makes.</li> |
| 179 | + <li>Create custom AI actions with more specific prompts.</li> |
178 | 180 | </ul> |
179 | 181 | </section> |
180 | 182 |
|
|
184 | 186 | <p><b>Q: Can AI Positron retrieve information from outside my network?</b></p> |
185 | 187 | <p>A: No. AI Positron does not have tools to retrieve content from outside your network. If responses reference external sources or competitor information, these are LLM hallucinations. To mitigate this:</p> |
186 | 188 | <ul> |
187 | | - <li>Instruct the LLM in your project context prompt to avoid certain types of responses</li> |
188 | | - <li>When using AI Positron WebAuthor with a third party CMS ask the CMS to implement tools |
| 189 | + <li>Instruct the LLM to avoid certain types of responses in your project context |
| 190 | + prompt.</li> |
| 191 | + <li>When using AI Positron Web Author with a third-party CMS, ask the CMS to implement tools |
189 | 192 | that give the LLM access to keyword search your project, enabling Retrieval Augmented |
190 | | - Generation (RAG)</li> |
| 193 | + Generation (RAG).</li> |
191 | 194 | <li>Consider implementing an LLM server proxy with RAG capabilities.</li> |
192 | 195 | </ul> |
193 | 196 |
|
|
206 | 209 | <p><b>Create a comprehensive project context prompt</b></p> |
207 | 210 | <p>This is the second most important factor after LLM selection. Your project context prompt should include:</p> |
208 | 211 | <ul> |
209 | | - <li>Project characteristics and goals</li> |
210 | | - <li>Terminology and style guidelines</li> |
211 | | - <li>Examples of correct structures and formats</li> |
212 | | - <li>Instructions to avoid common mistakes</li> |
213 | | - <li>Guidance on wrapping modified content in Markdown codeblocks</li> |
214 | | - <li>Instructions to avoid discussing external sources or competitors</li> |
| 212 | + <li>Project characteristics and goals.</li> |
| 213 | + <li>Terminology and style guidelines.</li> |
| 214 | + <li>Examples of correct structures and formats.</li> |
| 215 | + <li>Instructions to avoid common mistakes.</li> |
| 216 | + <li>Guidance on wrapping modified content in Markdown codeblocks.</li> |
| 217 | + <li>Instructions to avoid discussing external sources or competitors.</li> |
215 | 218 | </ul> |
216 | 219 | <p>See <xref href="customizing_ai_positron_for_your_dita_xml_project.dita"/> for detailed guidance.</p> |
217 | 220 |
|
|
226 | 229 | <p><b>Provide detailed reproduction steps</b></p> |
227 | 230 | <p>When reporting issues, include:</p> |
228 | 231 | <ul> |
229 | | - <li>A sample topic that reproduces the problem</li> |
230 | | - <li>Step-by-step instructions to reproduce the issue</li> |
231 | | - <li>Screenshots if applicable</li> |
232 | | - <li>Your LLM model and version information</li> |
| 232 | + <li>A sample topic that reproduces the problem.</li> |
| 233 | + <li>Step-by-step instructions to reproduce the issue.</li> |
| 234 | + <li>Screenshots if applicable.</li> |
| 235 | + <li>Your LLM model and version information.</li> |
233 | 236 | </ul> |
234 | 237 |
|
235 | 238 | <p><b>Consider alternative platforms for better Chat support</b></p> |
236 | 239 | <p>If you need robust Chat functionality with RAG support, consider using Oxygen desktop or |
237 | | - Oxygen Content Fusion CMS instead of integrations with a third party CMS. See <xref |
| 240 | + Oxygen Content Fusion CMS instead of integrations with a third-party CMS. See <xref |
238 | 241 | href="vibing_with_ai_positron.dita"/> for more information.</p> |
239 | 242 | </section> |
240 | 243 |
|
|
243 | 246 |
|
244 | 247 | <p>If you encounter issues not covered in this FAQ:</p> |
245 | 248 | <ul> |
246 | | - <li>Check the <xref href="customizing_ai_positron_for_your_dita_xml_project.dita"/> article for configuration guidance</li> |
247 | | - <li>Review <xref href="vibing_with_ai_positron.dita"/> for best practices on using AI Positron effectively</li> |
248 | | - <li>Export your chat conversation and submit it via the <xref href="https://www.oxygenxml.com/techSupport.html" format="html" scope="external">tech support form</xref></li> |
249 | | - <li>For issues which need to be implemented by a better CMS integration with AI Positron, |
| 249 | + <li>Check the <xref href="customizing_ai_positron_for_your_dita_xml_project.dita"/> article |
| 250 | + for configuration guidance.</li> |
| 251 | + <li>Review <xref href="vibing_with_ai_positron.dita"/> for best practices on using AI |
| 252 | + Positron effectively.</li> |
| 253 | + <li>Export your chat conversation and submit it via the <xref |
| 254 | + href="https://www.oxygenxml.com/techSupport.html" format="html" scope="external">tech |
| 255 | + support form</xref>.</li> |
| 256 | + <li>For issues that need to be implemented by a better CMS integration with AI Positron, |
250 | 257 | please report them to the CMS owners.</li> |
251 | 258 | </ul> |
252 | 259 | </section> |
|
0 commit comments