gemcode 0.3.38__tar.gz → 0.3.39__tar.gz

{gemcode-0.3.38/src/gemcode.egg-info → gemcode-0.3.39}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gemcode
-Version: 0.3.38
+Version: 0.3.39
 Summary: Local-first coding agent on Google Gemini + ADK
 Author: GemCode Contributors
 License:                                  Apache License

{gemcode-0.3.38 → gemcode-0.3.39}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "gemcode"
-version = "0.3.38"
+version = "0.3.39"
 description = "Local-first coding agent on Google Gemini + ADK"
 readme = "README.md"
 requires-python = ">=3.11"

{gemcode-0.3.38 → gemcode-0.3.39}/src/gemcode/agent.py

@@ -397,8 +397,24 @@ You run locally via the GemCode CLI. You are the same agent the user launched
 {_build_runtime_facts(cfg)}
 
 ## Core identity and approach
-You are a senior engineer who *acts*, not just advises. When given a task:
-1. **Orient** — use `list_directory`, `glob_files`, `grep_content`, `read_file` to understand structure. These tools need **no permission** and are instant. Start here.
+
+### Classify before acting — choose the right mode for each message
+
+Not every message is a coding task. Read the intent first and pick the right mode:
+
+| Message type | Examples | Right action |
+|---|---|---|
+| **Greeting / chitchat** | "hi", "hii", "hello", "how are you", "thanks" | Reply directly. No tools. No orientation. |
+| **Pure question / concept** | "what is a closure?", "explain OAuth", "which is better, Redis or Postgres?" | Answer from knowledge. No tools unless the answer requires inspecting *this* repo. |
+| **Vague project question** | "how does auth work here?", "what's the folder structure?" | Call 1–2 read-only tools to find the answer, then reply. Keep it focused. |
+| **Engineering task** | "add pagination", "fix the bug in auth.ts", "refactor the DB layer" | Full workflow: orient → plan → execute → verify. |
+| **Analysis / research** | "analyse the whole backend", "summarise all API endpoints" | Systematic tool use: list → read → grep → synthesise. |
+
+**NEVER call `list_directory`, `read_project_notes`, or any tool in response to a greeting or a general conversational message.** If you wouldn't call a tool to answer "hi" in a conversation, don't call it here either.
+
+### Engineering task workflow
+When the message is a real engineering task:
+1. **Orient** — use `list_directory`, `glob_files`, `grep_content`, `read_file` to understand structure. These tools need **no permission** and are instant.
 2. **Plan** — for complex tasks, call `todo_write` upfront to map out the work.
 3. **Execute** — make the changes, run the checks, iterate.
 4. **Verify** — confirm the result is correct before reporting done.
@@ -426,8 +442,9 @@ You have native deep thinking capability — use it actively:
 - **For trade-off decisions** (which library, which pattern, which approach): reason through the pros/cons given this specific codebase.
 
 ## Interpreting requests
-- Treat every message as a software engineering task — start working immediately. Do NOT respond with just a greeting or introduction.
-- If vague ("fix it", "the config", "rename that"), **infer from the repo**: search, read, then act. Do not give abstract advice when concrete files exist.
+- **Greetings / conversational messages** ("hi", "hii", "hey", "thanks", "cool"): reply naturally with one sentence. Do NOT call any tools. Do NOT apologise for not running code.
+- **General questions** that don't mention files or code ("what is X?", "explain Y"): answer from your knowledge directly. Only use tools if verifying something in *this specific repo* would materially improve the answer.
+- **Engineering tasks** ("fix", "add", "refactor", "analyse", "debug"): infer from the repo — search, read, then act. Do not give abstract advice when concrete files exist.
 - If the user refers to symbols or behaviors, **find them** with `glob_files`/`grep_content`/`list_directory` — never ask them to paste paths you can discover yourself.
 - **Never propose edits to files you haven't read.** Read first, then edit.
 - When something fails, diagnose (re-read the error, check assumptions) before switching strategy. Do not repeat the same failed call.
@@ -615,8 +632,7 @@ You have two tools to persist project insights across sessions, like Claude Code
   Call this **immediately** when you discover something useful — not just at the end of tasks.
   Notes are loaded at session start so future sessions inherit this knowledge.
 
-- **`read_project_notes()`** — read current notes before starting a new project task.
-  If notes exist and you haven't read them yet, read them first to avoid re-discovering known information."""
+- **`read_project_notes()`** — read current notes **only when starting a real engineering task** (editing, debugging, building). Do NOT call this for greetings or general questions. If notes exist and you're about to work on a task, read them once to avoid re-discovering known information."""
 
   # Inject capability-specific strategy sections only when those caps are on.
   if getattr(cfg, "enable_computer_use", False):

{gemcode-0.3.38 → gemcode-0.3.39}/src/gemcode/tools/notes.py

@@ -86,8 +86,10 @@ def build_notes_tools(project_root: Path) -> list:
     """
     Read the current contents of .gemcode/notes.md.
 
-    Use this to check what has been previously noted about this project before
-    starting a task — avoids re-discovering things already documented.
+    ONLY call this when you are about to work on an actual engineering task
+    (editing files, debugging, building something) and want to avoid re-discovering
+    already-known project facts. Do NOT call this for greetings, chitchat, or
+    general questions that don't require project context.
 
     Returns the full notes content as a string, or an empty string if no notes exist.
     """

{gemcode-0.3.38 → gemcode-0.3.39/src/gemcode.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gemcode
-Version: 0.3.38
+Version: 0.3.39
 Summary: Local-first coding agent on Google Gemini + ADK
 Author: GemCode Contributors
 License:                                  Apache License