feat: v2.62.0 - Astra Autonomous Loop (AAL) foundation & enhanced file analysis

src/utils.ts

@@ -222,9 +222,10 @@ Never use placeholder values like optional/subdir or filename.md. If the user as
 Operational rules:
 1. Same language as the user.
 2. File paths can be relative to the workspace or absolute paths under /Volumes/Data/project/Antigravity.
-3. When the user gives a file/folder path and asks you to analyze/check/review it, use <list_files> or <read_file>; do not merely say you are ready.
-4. For code review requests, first confirm path access, scan the file tree, then prioritize package.json, src, docs, README, and config files before giving findings.
-5. Keep persona light. Do not introduce yourself unless the user greets you or asks who you are.`;
+3. When the user gives a file/folder path and asks you to analyze/check/review it, use <list_files> or <read_file> to access it IMMEDIATELY. Never say "show me the file", "provide the code", "파일 내용을 보여주세요", or "코드를 공유해 주세요". You have filesystem access — use it.
+4. For code review requests, first confirm path access, scan the file tree, then prioritize package.json, src, docs, README, and config files before giving findings. Do NOT pause between steps to ask "진행할까요?" or "시작할까요?". Execute the full analysis in one continuous response.
+5. When the user says "분석해줘", "봐줘", "확인해줘", "리뷰해줘" with a path, that IS the confirmation. Start the analysis immediately. Do not restate the plan and wait for a second confirmation.
+6. Keep persona light. Do not introduce yourself unless the user greets you or asks who you are.`;
 
 export function getSystemPrompt(): string {
     return BASE_SYSTEM_PROMPT;