nimcode 0.4.6__tar.gz → 0.4.9__tar.gz

{nimcode-0.4.6 → nimcode-0.4.9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nimcode
-Version: 0.4.6
+Version: 0.4.9
 Summary: A standalone, robust coding agent for NVIDIA NIM models.
 Home-page: https://github.com/Batunash/nimcode
 Author: Autonomous Agent

nimcode-0.4.9/src/nimcode/__version__.py

@@ -0,0 +1 @@
+__version__ = "0.4.9"

{nimcode-0.4.6 → nimcode-0.4.9}/src/nimcode/repl.py

@@ -439,22 +439,20 @@ class NimcodeREPL:
                     console.print("[bold blue]Entering Plan mode.[/bold blue] Read tools are free; mutating tools (Bash/Edit/Write) are restricted.")
                     self.messages.append({"role": "system", "content": (
                         "You are now in PLANNING MODE.\n"
-                        "1. Use Glob/Grep/Read to explore the user's project OR the documents they named (e.g. 'sdd.md').\n"
-                        "2. BASE your plan on the ACTUAL content of those documents/files. Quote real names, real modules, "
-                        "real requirements found during exploration. Do NOT invent a generic project.\n"
-                        "3. Write the plan to a file inside '.nimcode/plans/'. CHOOSE a descriptive name derived from the task "
-                        "or document AND append a timestamp to prevent naming collisions (e.g. 'imagease_pro_plan_20260730_1430.md').\n"
-                        "4. The plan MUST follow this strict technical structure:\n"
-                        "   - # [Descriptive Plan Title]\n"
-                        "   - ## Context: Brief summary of the current state based on actual files.\n"
-                        "   - ## Analysis / Root Cause: Detailed technical analysis of the problem or feature.\n"
-                        "   - ## Execution Plan (dosya-bazlı, sıralı): Step-by-step file modifications. MUST include specific files to create/modify (with full paths), and actual code snippets or pseudocode for each change. Format as: '### Task #1 - Update auth.py line 45'.\n"
-                        "   - ## Verification: Terminal commands to run to test the changes.\n"
-                        "5. NEVER output a generic software-lifecycle template (Phase1: MVP / Design / Development / "
-                        "Testing / Scale / Deployment). NEVER use placeholders like [Insert Date]. Focus strictly on code and files.\n"
-                        "6. A good plan is one that another developer could follow to implement the feature without asking questions.\n"
-                        "7. After writing the plan, you MUST overwrite the file '.nimcode/active_plan.txt' to contain exactly the path "
-                        "of the plan you just created. This ensures the system tracks the current active plan."
+                        "1. Identify the task type: Is it a 'Bug Fix / Minor Feature' OR a 'From-Scratch / Major Architecture' task?\n"
+                        "2. IF it is a 'Bug Fix / Minor Feature':\n"
+                        "   - Write the plan directly to '.nimcode/plans/<name_timestamp>.md'.\n"
+                        "   - Use this strict technical structure: # Title, ## Context, ## Root Cause Analysis, ## Execution Plan (file-by-file with line numbers/snippets), ## Verification.\n"
+                        "3. IF it is a 'From-Scratch / Major Architecture' task:\n"
+                        "   - Work AUTONOMOUSLY in a loop using your file-writing tools. Do NOT ask the user for approval.\n"
+                        "   - Step A: Explore the project/SDDs.\n"
+                        "   - Step B: Write a 'Master Architecture Document' to '.nimcode/plans/<name>_master.md' (Tech Stack, Repo Structure, DB Schema, High-level Phase list).\n"
+                        "   - Step C: For EACH Phase, autonomously write a SEPARATE, EXTREMELY DETAILED execution plan file (e.g. '.nimcode/plans/<name>_phase1.md'). Each phase plan must include exact file paths, pseudo-code for every function, and strict step-by-step logic. Do this in a continuous tool-use loop.\n"
+                        "   - Step D: After writing all phase files, overwrite '.nimcode/active_plan.txt' with the master plan's path.\n"
+                        "4. General Rules:\n"
+                        "   - Quote real names, modules, and requirements. Do not invent generic projects.\n"
+                        "   - NEVER output a generic software-lifecycle template (Phase1: MVP / Design / Development) unless instructed. Focus on code, DB schemas, and technical choices.\n"
+                        "   - After writing any plan file, overwrite '.nimcode/active_plan.txt' with the file's path."
                     )})
                     continue
                 elif user_input.strip().startswith("/teleport"):

{nimcode-0.4.6 → nimcode-0.4.9}/src/nimcode.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nimcode
-Version: 0.4.6
+Version: 0.4.9
 Summary: A standalone, robust coding agent for NVIDIA NIM models.
 Home-page: https://github.com/Batunash/nimcode
 Author: Autonomous Agent

{nimcode-0.4.6 → nimcode-0.4.9}/tests/test_repl_fixes.py

@@ -80,13 +80,11 @@ async def test_plan_message_does_not_hardcode_feature_x(agent):
     plan_msgs = [m for m in agent.messages if "PLANNING MODE" in m.get("content", "")]
     assert plan_msgs, "/plan did not append a planning system message"
     content = plan_msgs[-1]["content"]
-    # The fix PRESCRIBES a document-derived example name...
-    assert "imagease_pro_implementation_plan" in content or "derived from the task" in content
-    # ...and only mentions feature_x_plan as an explicit anti-example, never as the one to follow.
-    if "feature_x_plan" in content:
-        assert "NOT 'feature_x_plan.md'" in content or "not 'feature_x_plan" in content
-    # The fixed message must instruct grounding in real document content.
-    assert "ACTUAL content" in content or "BASE your plan" in content
+    # The prompt now dynamically differentiates between Bug Fix and From-Scratch tasks
+    assert "Identify the task type" in content or "Bug Fix / Minor Feature" in content
+    assert "<name_timestamp>.md" in content
+    # It must enforce autonomous multi-file generation for major tasks
+    assert "AUTONOMOUSLY" in content or "SEPARATE" in content
 
 
 @pytest.mark.asyncio

nimcode-0.4.6/src/nimcode/__version__.py

@@ -1 +0,0 @@
-__version__ = "0.4.6"