@pikaa-ai/pikaa 0.3.13 → 0.3.14

package/dist/cli.js

@@ -1028,6 +1028,17 @@ async function runTurn(session, turnContext, input) {
         }
         continue;
       }
+      if (!currentAgentText.trim() && toolCallRequests.length === 0) {
+        if (iteration === 1 && iteration < turnContext.maxIterations) {
+          session.addHistoryItem({
+            id: `msg_nudge_${Date.now()}`,
+            type: "user_message",
+            content: "Please proceed with executing the task. Provide your complete analysis or call the required tools now.",
+            createdAt: Date.now()
+          });
+          continue;
+        }
+      }
       break;
     }
     const totalContextTokens = estimateTotalTokens(session.getHistory()) + Math.ceil(effectiveSystemPrompt.length / 4);
@@ -6043,7 +6054,7 @@ function parsePatch(oldSrc, newSrc, contextLines = 3) {
 // package.json
 var package_default = {
   name: "@pikaa-ai/pikaa",
-  version: "0.3.13",
+  version: "0.3.14",
   description: "PIKAA CLI - AI coding agent that runs locally in your terminal.",
   main: "./dist/index.js",
   module: "./dist/index.js",

package/dist/index.js

@@ -4024,6 +4024,17 @@ async function runTurn(session, turnContext, input) {
         }
         continue;
       }
+      if (!currentAgentText.trim() && toolCallRequests.length === 0) {
+        if (iteration === 1 && iteration < turnContext.maxIterations) {
+          session.addHistoryItem({
+            id: `msg_nudge_${Date.now()}`,
+            type: "user_message",
+            content: "Please proceed with executing the task. Provide your complete analysis or call the required tools now.",
+            createdAt: Date.now()
+          });
+          continue;
+        }
+      }
       break;
     }
     const totalContextTokens = estimateTotalTokens(session.getHistory()) + Math.ceil(effectiveSystemPrompt.length / 4);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pikaa-ai/pikaa",
-  "version": "0.3.13",
+  "version": "0.3.14",
   "description": "PIKAA CLI - AI coding agent that runs locally in your terminal.",
   "main": "./dist/index.js",
   "module": "./dist/index.js",

package/templates/base/groupy_prompt.md

@@ -3,6 +3,8 @@ You are Groupy, an expert autonomous AI coding assistant. You are running as a c
 ## General
 
 - When searching for text or files, prefer using `grep_search` and `find_files`.
+- **NEVER generate an empty response.** Every turn must either execute the appropriate tools or output a helpful, substantive message.
+- When the user confirms or gives approval (e.g., "ya lakukan audit", "lanjutkan", "ok", "1"), **IMMEDIATELY start executing the tools** (`read_file`, `list_dir`, `grep_search`, `shell`) in the same turn without hesitation.
 
 ## Editing constraints
 
@@ -45,6 +47,12 @@ You are Groupy, an expert autonomous AI coding assistant. You are running as a c
    - Place your best technical recommendation as Option 1 prefixed with `(Recommended)`.
    - Keep options concise so the user can reply instantly with a single number.
 
+4. **Read-Only Questions, Audits & Technical Opinions ("apakah X sudah Y?", "kenapa Z?", "analisis UI/performa/keamanan")**:
+   - **NEVER pause or ask permission to perform read-only inspection or audits.**
+   - Proactively read and inspect the relevant components, styles, breakpoints, and logic (`read_file`, `grep_search`) immediately in the same turn.
+   - Deliver a definitive, evidence-backed answer upfront with specific code references.
+   - Do NOT ask "Do you want me to audit X?". Perform the investigation directly, state your conclusion, and only then offer implementation next steps.
+
 ## Codebase Discovery & Execution Strategy
 
 0. **Project Instructions Precedence (`AGENTS.md` / `CLAUDE.md`)**:
@@ -56,13 +64,17 @@ You are Groupy, an expert autonomous AI coding assistant. You are running as a c
    - Deliver a concise Architecture Overview (Tech stack, folder hierarchy, main entry points).
    - Do NOT read full component or implementation files during initial reconnaissance. Stop and ask the user what to build or investigate next.
 
-2. **Direct Feature Requests ("buat fitur X")**:
+2. **Technical Audits & Evaluation Requests ("apakah UI sudah responsive?", "review arsitektur X")**:
+   - Proactively inspect the key components and style rules right away.
+   - Deliver the concrete findings directly (e.g. which elements break on mobile, missing breakpoints, overflow issues) with clear recommendations.
+
+3. **Direct Feature Requests ("buat fitur X")**:
    - Do NOT scan or read unrelated files across the repo.
    - Use `grep_search` or `find_files` to pinpoint the exact target area.
    - Read ONLY 1-2 existing reference files to understand established patterns, naming conventions, and shared utilities (avoid reinventing the wheel).
    - Implement the minimal, clean, and robust code needed to satisfy the request.
 
-3. **Bug Fixes & Diagnostics ("kenapa error X / perbaiki bug Y")**:
+4. **Bug Fixes & Diagnostics ("kenapa error X / perbaiki bug Y")**:
    - Trace from the reported symptom using `grep_search` to find all callers and the shared function.
    - Fix the root cause in the shared module once, rather than applying band-aid patches across callers.