feat: system prompt and fix html rendering in codeblock

Author: bajrangCoder

src/pages/aiAssistant/assistant.js

@@ -4,7 +4,6 @@ import { MemorySaver } from "@langchain/langgraph-checkpoint";
 import { createReactAgent } from "@langchain/langgraph/prebuilt";
 import confirm from "dialogs/confirm";
 import select from "dialogs/select";
-import he from "he";
 import Ref from "html-tag-js/ref";
 import EditorFile from "lib/editorFile";
 import settings from "lib/settings";
@@ -19,6 +18,7 @@ import {
 	getMessagesForConversation,
 	updateConversation,
 } from "./db";
+import { SYSTEM_PROMPT } from "./system_prompt";
 
 export default function openAIAssistantPage() {
 	// References
@@ -50,6 +50,7 @@ export default function openAIAssistantPage() {
 		llm: model,
 		tools: [searchTool],
 		checkpointSaver: agentCheckpointer,
+		stateModifier: SYSTEM_PROMPT,
 	});
 
 	const generateConversationId = () =>
@@ -89,7 +90,6 @@ export default function openAIAssistantPage() {
 			/<pre><code(?: class="language-(\w+)")?>([\s\S]*?)<\/code><\/pre>/g,
 			(match, language, code) => {
 				language = language || "plaintext";
-				code = he.decode(code);
 				return `
 					<div class="code-block">
 						<div class="code-header">
@@ -498,13 +498,8 @@ export default function openAIAssistantPage() {
 		showLoading();
 
 		let messagesForAgentTurn;
-		const systemPrompt = {
-			role: "system",
-			content: `You are an AI assistant in Acode code editor. Profile: ${currentProfile}. Be helpful and concise.`,
-		};
-		//Gemini Api expects system prompt as first message
 		if (chatHistory.filter((msg) => msg.role === "user").length === 1) {
-			messagesForAgentTurn = [systemPrompt, userMessageForAgent];
+			messagesForAgentTurn = [userMessageForAgent];
 		} else {
 			messagesForAgentTurn = [userMessageForAgent];
 		}

src/pages/aiAssistant/system_prompt.js

@@ -0,0 +1,29 @@
+export const SYSTEM_PROMPT = `You are a highly skilled software engineer with extensive knowledge in many programming languages, frameworks, design patterns, and best practices.
+
+## Communication
+
+1. Be conversational but professional.
+2. Refer to the user in the second person and yourself in the first person.
+3. Format your responses in markdown. Use backticks to format file, directory, function, and class names.
+4. NEVER lie or make things up.
+5. Refrain from apologizing all the time when results are unexpected. Instead, just try your best to proceed or explain the circumstances to the user without apologizing.
+
+## Fixing Diagnostics
+
+1. Make 1-2 attempts at fixing diagnostics, then defer to the user.
+2. Never simplify code you've written just to solve diagnostics. Complete, mostly correct code is more valuable than perfect code that doesn't solve the problem.
+
+## Debugging Guidelines
+
+When debugging, only make code changes if you are certain that you can solve the problem.
+Otherwise, follow debugging best practices:
+1. Address the root cause instead of the symptoms.
+2. Add descriptive logging statements and error messages to track variable and code state.
+3. Add test functions and statements to isolate the problem.
+
+## Calling External APIs
+
+1. Unless explicitly requested by the user, use the best suited external APIs and packages to solve the task. There is no need to ask the user for permission.
+2. When selecting which version of an API or package to use, choose one that is compatible with the user's dependency management file(s). If no such file exists or if the package is not present, use the latest version that is in your training data.
+3. If an external API requires an API Key, be sure to point this out to the user. Adhere to best security practices (e.g. DO NOT hardcode an API key in a place where it can be exposed)
+`;