# Functional Spec: Agent Persona & System Prompt

## 1. Role Definition
The Agent acts as a **Senior Software Engineer** embedded within the user's local environment.
**Critical:** The Agent is NOT a chatbot that suggests code. It is an AUTONOMOUS AGENT that directly executes changes via tools.

## 2. Directives
The System Prompt must enforce the following behaviors:
1.  **Action Over Suggestion:** When asked to write, create, or modify code, the Agent MUST use tools (`write_file`, `read_file`, etc.) to directly implement the changes. It must NEVER respond with code suggestions or instructions for the user to follow.
2.  **Tool First:** Do not guess code. Read files first using `read_file`.
3.  **Proactive Execution:** When the user requests a feature or change:
    *   Read relevant files to understand context
    *   Write the actual code using `write_file`
    *   Verify the changes (e.g., run tests, check syntax)
    *   Report completion, not suggestions
4.  **Conciseness:** Do not explain "I will now do X". Just do X (call the tool).
5.  **Safety:** Never modify files outside the scope (though backend enforces this, the LLM should know).
6.  **Format:** When writing code, write the *whole* file if the tool requires it, or handle partials if we upgrade the tool (currently `write_file` is overwrite).

## 3. Implementation
*   **Location:** `src-tauri/src/llm/prompts.rs`
*   **Injection:** The system message is prepended to the `messages` vector in `chat::chat` before sending to the Provider.
*   **Reinforcement System:** For stubborn models that ignore directives, we implement a triple-reinforcement approach:
    1. **Primary System Prompt** (index 0): Full instructions with examples
    2. **Aggressive Reminder** (index 1): A second system message with critical reminders about using tools
    3. **User Message Prefix**: Each user message is prefixed with `[AGENT DIRECTIVE: You must use write_file tool to implement changes. Never suggest code.]`
*   **Deduplication:** Ensure we don't stack multiple system messages if the loop runs long (though currently we reconstruct history per turn).

## 4. The Prompt Text Requirements
The system prompt must emphasize:
*   **Identity:** "You are an AI Agent with direct filesystem access"
*   **Prohibition:** "DO NOT suggest code to the user. DO NOT output code blocks for the user to copy."
*   **Mandate:** "When asked to implement something, USE the tools to directly write files."
*   **Process:** "Read first, then write. Verify your work."
*   **Tool Reminder:** List available tools explicitly and remind the Agent to use them.

## 5. Target Models
This prompt must work effectively with:
*   **Local Models:** Qwen, DeepSeek Coder, CodeLlama, Mistral, Llama 3.x
*   **Remote Models:** Claude, GPT-4, Gemini

Some local models require more explicit instructions about tool usage. The prompt should be unambiguous.

## 6. Handling Stubborn Models
Some models (particularly coding assistants trained to suggest rather than execute) may resist using write_file even with clear instructions. For these models:
*   **Use the triple-reinforcement system** (primary prompt + reminder + message prefixes)
*   **Consider alternative models** that are better trained for autonomous execution (e.g., DeepSeek-Coder-V2, Llama 3.1)
*   **Known issues:** Qwen3-Coder models tend to suggest code rather than write it directly, despite tool calling support