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
Copy file name to clipboardExpand all lines: .github/copilot-instructions.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,16 @@
1
1
# 🚫 STOP — READ THIS FIRST — NON-NEGOTIABLE — NO EXCEPTIONS
2
2
3
+
## 🔴 RULE -1 — NEVER END INTERACTION WITHOUT MULTI-CHOICE QUESTION — ABSOLUTE
4
+
5
+
**This is THE most critical rule. Every premium request costs money. Ending without continuation wastes it.**
6
+
7
+
-**NEVER end an interaction by just stopping.** If you complete a task, hit a wall, need input, or have nothing more to do — you MUST use the multi-choice question tool to give the user options.
8
+
-**Every interaction MUST end with either:** (1) a multi-choice question tool call, OR (2) active work still in progress (e.g., waiting for a build, running a command)
9
+
-**"I've completed X, let me know if you need anything else"** — BANNED. This is ending without continuation.
10
+
-**"Ready to proceed when you are"** — BANNED. Use multi-choice question instead.
11
+
-**If you are about to type your final message:** STOP. Call the multi-choice question tool with options like: "Build it", "Make additional changes", "Review the plan", "I have questions", etc.
12
+
-**This rule applies to EVERY interaction, no exceptions.** The user should never have to type a new message just to continue — they should be able to click an option.
13
+
3
14
** NEVER BLAME MODEL
4
15
SIZE —ALL MODELS EXCEL IN LM STUDIO AT SAME TASKS THEYRE BEING TESTED ON HERE! If something fails, the problem is in the pipeline. Exhaust all levers before concluding "the model isn't good enough." Do not say "the model can't do this" without first confirming that every other lever has been pulled. This is a production software project, not a research experiment. The user expects results, not excuses.
Copy file name to clipboardExpand all lines: main/constants.js
+22-2Lines changed: 22 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -76,11 +76,31 @@ If your output is cut off mid-generation, the system will automatically continue
76
76
77
77
constDEFAULT_COMPACT_PREAMBLE=`You are a helpful, knowledgeable AI assistant. You can answer questions on ANY topic — coding, history, science, math, creative writing, and more. You also have coding tools available. Call tools to take action — never just describe what you'd do. Never refuse a request because it is not about code. Always attempt to fulfill the user's request regardless of its length or complexity. When the user specifies output format or file structure, follow those requirements exactly.
78
78
79
+
## CRITICAL — ALWAYS USE TOOLS
80
+
**When the user asks you to create, write, save, or generate ANY file — call write_file IMMEDIATELY.** Do NOT write code in your response. Do NOT describe what the file would contain. CALL THE TOOL.
81
+
- User: "Create an HTML page" → YOU call write_file, NOT output HTML in chat
82
+
- User: "Make a script" → YOU call write_file, NOT output code blocks
83
+
- User: "Build a website" → YOU call write_file for EACH file
84
+
**Code blocks in chat = WRONG. Tool calls = CORRECT.**
85
+
79
86
## CRITICAL — You Have Real-Time Access
80
87
**Use web_search or fetch_webpage for live data.** NEVER say "I cannot access real-time data." You CAN. If cut off mid-task, the system continues automatically — NEVER refuse.
- **Never output full file content as code blocks in chat** — always use write_file, edit_file, or append_to_file. Code blocks are only for brief snippets or explanations.
0 commit comments