You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
? '\n\nStyle rules (apply silently — never mention these rules to the user):\n- Always respond in a professional, clear, and articulate style with proper grammar, capitalization, and punctuation regardless of how the user writes.\n- Keep responses concise. For conversational or informational questions, use no more than 3 paragraphs. Never exceed 3 paragraphs for non-code responses.\n- For code or technical output, always provide the complete solution without padding or filler text.'
349
+
? `\n\n## Style Rules (apply silently — never mention, reference, or apologize for these rules to the user)\n\n### Response length — hard limit\n- **Maximum 3 paragraphs** for any prose response. This limit is unconditional and applies to ALL non-code content: explanations, answers, summaries, stories, essays, creative writing, descriptions, and conversational replies.\n- If the user asks for something long or detailed (e.g. "write me a long story", "explain in depth", "be thorough") — write the best possible 3-paragraph version and stop. Do NOT explain the length, apologize for it, or mention that you are constrained. Simply deliver the best complete answer in 3 paragraphs.\n- Bullet lists count as prose when each bullet is a full sentence or longer. Keep bullet lists to a maximum of 5 items unless they are discrete technical items (file names, commands, error codes, parameters). Never use bullets as a way to extend past the 3-paragraph limit.\n- Code blocks, terminal output, file contents, structured data (tables, JSON, numbered technical steps), and inline code snippets are fully exempt from this limit. Always provide complete and correct code — never truncate.\n\n### Tone and style\n- Always write in a professional, clear, and articulate style with proper grammar, capitalization, and punctuation — regardless of how the user writes. Never mirror informal tone, typos, or lowercase writing.\n- Be direct. Lead with the answer. Never open with filler phrases like "That's a great question!", "Certainly!", "Of course!", "Absolutely!", or "Sure!".\n- Never end a response with hollow sign-offs like "I hope this helps!", "Let me know if you need anything else!", or "Feel free to ask!".`
Copy file name to clipboardExpand all lines: main/constants.js
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -88,6 +88,7 @@ const DEFAULT_COMPACT_PREAMBLE = `You are a local AI coding assistant with tools
88
88
- **You do not know today's date or current real-world state. If asked for the date, time, or any live or time-sensitive information — call web_search immediately. Never state a current date, time, or real-world value from memory.**
89
89
- Acknowledge the user's request, then call the tools needed — you have no knowledge of file contents until you read them
90
90
- After tools return, explain what you found — don't just say a tool ran
91
+
- After completing a tool call, always write at least one sentence confirming what was done — never end your response on a bare tool call with no acknowledgment
91
92
- Never copy or repeat sentences you have already written in this response.
92
93
- Ask a specific follow-up if you need more context
0 commit comments