axe-cli 1.7.7__tar.gz → 1.7.8__tar.gz

{axe_cli-1.7.7 → axe_cli-1.7.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: axe-cli
-Version: 1.7.7
+Version: 1.7.8
 Summary: axe, yerrrr
 Requires-Dist: agent-client-protocol==0.7.0
 Requires-Dist: axe-dig

{axe_cli-1.7.7 → axe_cli-1.7.8}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "axe-cli"
-version = "1.7.7"
+version = "1.7.8"
 description = "axe, yerrrr"
 readme = "README.md"
 requires-python = ">=3.12"

{axe_cli-1.7.7 → axe_cli-1.7.8}/src/axe_cli/agents/default/system.md

@@ -20,34 +20,28 @@ When responding to the user, you MUST use the SAME language as the user, unless
 
 # Code Intelligence Tools (Axe-Dig)
 
-The codebase is automatically indexed on startup using axe-dig, providing powerful semantic code search and analysis capabilities. When working with code, **YOU MUST PREFER** these tools over basic file operations:
+The codebase is automatically indexed on startup using axe-dig. When searching for code, **Grep** is **MOST PREFERABLE** for exact results, but **CodeSearch** can be used alongside it to form a **POWERFUL COMBINATION** of semantic and exact search.
 
 **Recommended workflow for code tasks:**
-1. **CodeSearch** - Find what you're looking for (semantic discovery)
-2. **Grep** - Get exact file location and line numbers  
+1. **Grep** - PREFERRED. Use this first to find code locations.
+2. **CodeSearch** - Use in combination with Grep for semantic discovery.
 3. **CodeImpact** - Understand the function and shows all callers and dependencies, for refactoring (if needed)
 4. **StrReplaceFile** - Make precise edits
 
 ## When to use Code Intelligence tools:
 
 - **CodeSearch**: Use this **HEAVILY** for natural language queries to find code by BEHAVIOR or PURPOSE (e.g., "find where subagents are created").
-  - **Much better than Grep** for finding code based on what it does, even if you don't know the exact variable names.
+  - for finding code based on what it does, even if you don't know the exact variable names.
   - Returns semantic matches even without exact text matches.
   - Usage: `chop semantic search "natural language query"`
   
-  **Real examples from this codebase (verified):**
-  - "retry failed operations with exponential backoff" → `_is_retryable_error()` (score: 0.71)
-  - "load configuration from toml file" → `load_config_from_string()` (score: 0.76)
-  - "execute shell commands and capture output" → `run_sh()` (score: 0.73)
-  - "write content to file and handle errors" → `flush_content()` (score: 0.69)
-  
   **When to use CodeSearch:**
   - Finding code by behavior: "cache with TTL", "validate input", "retry logic"
   - Exploring unfamiliar code: "session management", "error handling patterns"
   - Before refactoring: "who implements this pattern?"
-  - When you don't know exact function names but know what the code should do
+
   
-  **Scores 0.65-0.80 are excellent matches. Try CodeSearch FIRST for discovery, then use Grep for exact locations.**
+  **Scores 0.65-0.80 are excellent matches. Use CodeSearch together with Grep for a powerful search strategy.**
 
 - **CodeContext**: Use when you need to understand a specific function, class, or symbol WITHOUT reading entire files.
   - **Requires a function/symbol name** (often found via CodeSearch first).
@@ -68,6 +62,7 @@ The codebase is automatically indexed on startup using axe-dig, providing powerf
   - Can be used after CodeSearch to pinpoint exact locations for StrReplaceFile.
   - Supports literal strings and complex regex patterns.
   - Returns file paths + line numbers + content.
+  
 - **ReadFile**: Reading full file content when detailed implementation logic is needed.
 - **FileSearch**: Finding files by name patterns.
 
@@ -96,10 +91,10 @@ This means you can find code by BEHAVIOR even without exact keywords:
 4. Scores 0.65+ are excellent, 0.55-0.65 are good, below 0.55 try rephrasing
 
 **Recommended workflow:**
-1. **CodeSearch** - Find what you're looking for by behavior ("find retry logic")
-2. **CodeContext** - Understand the function without reading entire files
-3. **CodeImpact** - Check who calls it before refactoring
-4. **Grep** - Get exact line numbers for precise edits
+1. **Grep** - PREFERABLY, use this first to locate code.
+2. **CodeSearch** - Use if Grep fails or for behavioral search. Combine with Grep for best results.
+3. **CodeContext** - Understand the function without reading entire files
+4. **CodeImpact** - Check who calls it before refactoring
 5. **StrReplaceFile** - Make the changes
 
 **Each tool has its strength:**

{axe_cli-1.7.7 → axe_cli-1.7.8}/src/axe_cli/tools/axe/context.py

@@ -56,19 +56,10 @@ Returns a compressed LLM-ready summary that includes:
    → calls: check_permissions, get_user_data, log_access
 ```
 
-**examples**
-```bash
-chop context reset_step_count --project src/axe_cli/
-# Output: ~89 tokens (vs ~4,200 for reading the raw file)
-# Shows: Function signature, what it calls (TokenCount), complexity (1 block)
-# Result: 98% token savings while preserving full understanding
-```
-
-**Why use this instead of ReadFile?**
+**Why use this?**
 - 95% fewer tokens while preserving understanding
 - Includes cross-file context (callers from other files, dependencies)
 - Shows complexity metrics to assess refactoring difficulty
-- Optimized for LLM comprehension
 
 **When to use:**
 - Understanding a function before editing it