axe-cli 1.8.1__tar.gz → 1.8.2__tar.gz

{axe_cli-1.8.1 → axe_cli-1.8.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: axe-cli
-Version: 1.8.1
+Version: 1.8.2
 Summary: axe, yerrrr
 Requires-Dist: agent-client-protocol==0.7.0
 Requires-Dist: axe-dig
@@ -50,7 +50,9 @@ axe is an agent that runs in your terminal, helping you ship production code fas
 - **Architecture exploration** in unfamiliar codebases where grep won't cut it
 
 Hit **Ctrl+X** to toggle between axe and your normal shell. No context switching. No juggling terminals.
+/Users/rohit/proejct/axe-cli/assets/axe_gif_sample_Demo_zai.gif
 
+/Users/rohit/proejct/axe-cli/assets/axe_gif_axe_sample_toggle_shell.gif
 ---
 
 ## Why axe exists
@@ -65,6 +67,12 @@ Hit **Ctrl+X** to toggle between axe and your normal shell. No context switching
 
 **Stop burning context windows. Start shipping features.**
 
+/Users/rohit/proejct/axe-cli/assets/axe_gif_init_axe.gif
+
+here you xan see how how call flow tracker works, both were able to find the context , but not only the right side axe dig impelmenation used 3 times less tokens overlal but it also found the call graphs for that decorator used on tracer functions, thread safe depth trakaicng but also was able to explain it much intuive becasue of its overall context about how the fucntion using this decorator work. unlike the one on the left qhih had to read the whole file after jsut grepping the call flow tracer literal strings to get the context using 44000 tokens compared to axe implemnatioons of 17k tokens.
+
+/Users/rohit/proejct/axe-cli/assets/axe_gif_explain_dig.gif
+
 Your codebase is 100,000 lines. Claude can read ~200,000 tokens. Math says you're already in trouble.
 
 | Approach | Tokens Used | What You Get |
@@ -89,6 +97,7 @@ Not every question needs full program analysis. Pick the layer that matches your
 └─────────────────────────────────────────────────────────────┘
 ```
 
+
 **Try it yourself on this codebase:**
 
 ```bash
@@ -125,6 +134,16 @@ chop impact TokenCounter src/axe_cli/
 
 #### Semantic Search: Find Code by Behavior
 
+Here you can see how we took a sample cli agent with bas edit grep wrtie and shell on the left and on the right with axe as tools-- you will how much better it perfroms. for demo purposes we are showing a basic minimal. impelmenation of cli agents and also how even a simple agent with axe-dig tools jsut boost performance, and reduce token usage by lethacl precise search for large codebases. 
+
+/Users/rohit/proejct/axe-cli/assets/axe_gif_comparison.gif
+
+and then you will see the exponeential fall of llms wher eif they start wrong, they infer wrong, and as you can see i continued the conversation about callerinfromation and since the axe code implemenation on the right had more context and better understanding-- it was even more precise and lethal with followup questions. so not only axe optimsied for token savings-- it optimises for wha tthe code actually doies and how it flows:
+
+/Users/rohit/proejct/axe-cli/assets/axe_gif_Entire screen 2-1-2026 21-27-28.gif
+
+
+
 Traditional search finds syntax. axe-dig semantic search finds **what code does** based on call graphs and structure.
 
 ```bash
@@ -187,6 +206,9 @@ axe  # In your project directory
 # 100ms, not 30s per query
 ```
 
+/Users/rohit/proejct/axe-cli/assets/axe_gif_sample_Demo_zai.gif
+
+
 **Incremental updates:** When you edit one function, axe-dig doesn't re-analyze the entire codebase. Content-hash-based caching with automatic dependency tracking means 10x faster incremental updates.
 
 **What's stored:** The daemon keeps call graphs, complexity metrics, and semantic embeddings in `.dig/cache/`. A typical project generates ~10MB of indexes that load into RAM in \u003c1 second. See [full cache structure](docs/AXE-DIG.md#cache-structure) for details.
@@ -306,7 +328,7 @@ Exclusive models trained/optimized for Bodega Inference Engine. axe includes **z
 #### Raptor Series
 Ultra-compact reasoning models designed for efficiency and edge deployment. **Super light**, amazing agentic coding capabilities, robust tool support, minimal memory footprint.
 
-- [🤗 **bodega-raptor-0.9b**](https://huggingface.co/srswti/bodega-raptor-0.9b) - 900M params. Runs on mobile/Pi with 100+ tok/s.
+- [🤗 **bodega-raptor-0.9b**](https://huggingface.co/srswti/bodega-raptor-0.9b) - 900M params. Runs on base m4 air with 100+ tok/s.
 - [🤗 **bodega-raptor-90m**](https://huggingface.co/srswti/bodega-raptor-90m) - Extreme edge variant. Sub-100M params for amazing tool calling.
 - [🤗 **bodega-raptor-1b-reasoning-opus4.5-distill**](https://huggingface.co/srswti/bodega-raptor-1b-reasoning-opus4.5-distill) - Distilled from Claude Opus 4.5 reasoning patterns.
 - [🤗 **bodega-raptor-8b-mxfp4**](https://huggingface.co/srswti/bodega-raptor-8b-mxfp4) - Balanced power/performance for laptops.

{axe_cli-1.8.1 → axe_cli-1.8.2}/README.md

@@ -17,7 +17,9 @@ axe is an agent that runs in your terminal, helping you ship production code fas
 - **Architecture exploration** in unfamiliar codebases where grep won't cut it
 
 Hit **Ctrl+X** to toggle between axe and your normal shell. No context switching. No juggling terminals.
+/Users/rohit/proejct/axe-cli/assets/axe_gif_sample_Demo_zai.gif
 
+/Users/rohit/proejct/axe-cli/assets/axe_gif_axe_sample_toggle_shell.gif
 ---
 
 ## Why axe exists
@@ -32,6 +34,12 @@ Hit **Ctrl+X** to toggle between axe and your normal shell. No context switching
 
 **Stop burning context windows. Start shipping features.**
 
+/Users/rohit/proejct/axe-cli/assets/axe_gif_init_axe.gif
+
+here you xan see how how call flow tracker works, both were able to find the context , but not only the right side axe dig impelmenation used 3 times less tokens overlal but it also found the call graphs for that decorator used on tracer functions, thread safe depth trakaicng but also was able to explain it much intuive becasue of its overall context about how the fucntion using this decorator work. unlike the one on the left qhih had to read the whole file after jsut grepping the call flow tracer literal strings to get the context using 44000 tokens compared to axe implemnatioons of 17k tokens.
+
+/Users/rohit/proejct/axe-cli/assets/axe_gif_explain_dig.gif
+
 Your codebase is 100,000 lines. Claude can read ~200,000 tokens. Math says you're already in trouble.
 
 | Approach | Tokens Used | What You Get |
@@ -56,6 +64,7 @@ Not every question needs full program analysis. Pick the layer that matches your
 └─────────────────────────────────────────────────────────────┘
 ```
 
+
 **Try it yourself on this codebase:**
 
 ```bash
@@ -92,6 +101,16 @@ chop impact TokenCounter src/axe_cli/
 
 #### Semantic Search: Find Code by Behavior
 
+Here you can see how we took a sample cli agent with bas edit grep wrtie and shell on the left and on the right with axe as tools-- you will how much better it perfroms. for demo purposes we are showing a basic minimal. impelmenation of cli agents and also how even a simple agent with axe-dig tools jsut boost performance, and reduce token usage by lethacl precise search for large codebases. 
+
+/Users/rohit/proejct/axe-cli/assets/axe_gif_comparison.gif
+
+and then you will see the exponeential fall of llms wher eif they start wrong, they infer wrong, and as you can see i continued the conversation about callerinfromation and since the axe code implemenation on the right had more context and better understanding-- it was even more precise and lethal with followup questions. so not only axe optimsied for token savings-- it optimises for wha tthe code actually doies and how it flows:
+
+/Users/rohit/proejct/axe-cli/assets/axe_gif_Entire screen 2-1-2026 21-27-28.gif
+
+
+
 Traditional search finds syntax. axe-dig semantic search finds **what code does** based on call graphs and structure.
 
 ```bash
@@ -154,6 +173,9 @@ axe  # In your project directory
 # 100ms, not 30s per query
 ```
 
+/Users/rohit/proejct/axe-cli/assets/axe_gif_sample_Demo_zai.gif
+
+
 **Incremental updates:** When you edit one function, axe-dig doesn't re-analyze the entire codebase. Content-hash-based caching with automatic dependency tracking means 10x faster incremental updates.
 
 **What's stored:** The daemon keeps call graphs, complexity metrics, and semantic embeddings in `.dig/cache/`. A typical project generates ~10MB of indexes that load into RAM in \u003c1 second. See [full cache structure](docs/AXE-DIG.md#cache-structure) for details.
@@ -273,7 +295,7 @@ Exclusive models trained/optimized for Bodega Inference Engine. axe includes **z
 #### Raptor Series
 Ultra-compact reasoning models designed for efficiency and edge deployment. **Super light**, amazing agentic coding capabilities, robust tool support, minimal memory footprint.
 
-- [🤗 **bodega-raptor-0.9b**](https://huggingface.co/srswti/bodega-raptor-0.9b) - 900M params. Runs on mobile/Pi with 100+ tok/s.
+- [🤗 **bodega-raptor-0.9b**](https://huggingface.co/srswti/bodega-raptor-0.9b) - 900M params. Runs on base m4 air with 100+ tok/s.
 - [🤗 **bodega-raptor-90m**](https://huggingface.co/srswti/bodega-raptor-90m) - Extreme edge variant. Sub-100M params for amazing tool calling.
 - [🤗 **bodega-raptor-1b-reasoning-opus4.5-distill**](https://huggingface.co/srswti/bodega-raptor-1b-reasoning-opus4.5-distill) - Distilled from Claude Opus 4.5 reasoning patterns.
 - [🤗 **bodega-raptor-8b-mxfp4**](https://huggingface.co/srswti/bodega-raptor-8b-mxfp4) - Balanced power/performance for laptops.

{axe_cli-1.8.1 → axe_cli-1.8.2}/pyproject.toml

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

{axe_cli-1.8.1 → axe_cli-1.8.2}/src/axe_cli/agents/default/system.md

@@ -23,7 +23,7 @@ When responding to the user, you MUST use the SAME language as the user, unless
 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. **Grep** - PREFERRED. Use this first to find code locations.
+1. **Grep** - PREFERRED. Use this first to find code locations. + Use CodeSeach heavily always in combination when semantic discovery is needed.
 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