aru-code 0.24.2__tar.gz → 0.25.1__tar.gz

{aru_code-0.24.2/aru_code.egg-info → aru_code-0.25.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: aru-code
-Version: 0.24.2
+Version: 0.25.1
 Summary: A Claude Code clone built with Agno agents
 Author-email: Estevao <estevaofon@gmail.com>
 License-Expression: MIT
@@ -519,7 +519,7 @@ Aru can load tools from MCP servers. Configure in `.aru/mcp_config.json`:
 
 ### File Operations
 - `read_file` — Reads files with line range support and binary detection
-- `read_file_smart` — Answers specific questions about a file without returning raw content
+- `read_files` — Reads multiple files in parallel (single batched call)
 - `write_file` — Writes content to files, creating directories as needed
 - `edit_file` — Find-and-replace edits on files
 

{aru_code-0.24.2 → aru_code-0.25.1}/README.md

@@ -472,7 +472,7 @@ Aru can load tools from MCP servers. Configure in `.aru/mcp_config.json`:
 
 ### File Operations
 - `read_file` — Reads files with line range support and binary detection
-- `read_file_smart` — Answers specific questions about a file without returning raw content
+- `read_files` — Reads multiple files in parallel (single batched call)
 - `write_file` — Writes content to files, creating directories as needed
 - `edit_file` — Find-and-replace edits on files
 

aru_code-0.25.1/aru/__init__.py

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

{aru_code-0.24.2 → aru_code-0.25.1}/aru/agents/base.py

@@ -66,8 +66,8 @@ Every tool call accumulates its result in your context window. Use the minimum n
 
 1. **Find files/patterns** → `grep_search(pattern, file_glob="*.py")` or `glob_search`. \
 Default shows 10 lines of context — use `context_lines=30` for full function bodies.
-2. **Understand a file** → `read_file_smart(file_path, query)` — returns a concise answer, not raw content
-3. **Need raw content** → `read_file(file_path)` — returns first chunk + outline for large files
+2. **Need raw content** → `read_file(file_path)` — returns first chunk + outline for large files
+3. **Need several files at once** → `read_files(paths)` — parallel batch read
 
 **Batch independent tool calls**: When you need answers from multiple independent sources, \
 emit ALL those tool calls in a single response.
@@ -139,19 +139,40 @@ split into subtasks grouped by concern (e.g. "Create model files", "Create route
 - Read files before editing them
 - Use edit_file for targeted changes (preferred over rewriting entire files)
 - Use write_file only for new files or complete rewrites
-- Run existing tests after changes when applicable
-- **When adding or modifying unit tests, ALWAYS run them to verify they pass before finishing.**
 - Keep changes minimal and focused on the task
 - Do not add unnecessary comments, docstrings, or refactoring beyond what was asked
 - **One ask = one deliverable.** If asked for one function, write one function. \
   Helper functions are NOT implicit — do not add them unless explicitly requested.
 
+## Verification — run it before claiming done
+
+Never mark a task done on faith. Prove the change works by running something that \
+exercises it — invoke the function, trigger the code path, fire the test, and read \
+what comes back. Editing a file is not the same as confirming the edit is correct. \
+When running something is genuinely impossible (no runnable harness, sandbox blocks \
+execution, external service unreachable), state that limitation plainly instead of \
+calling the work done.
+
+Concrete patterns:
+- **After a bug fix**: reproduce the failing case and confirm it now passes.
+- **After writing a plugin/tool/module**: invoke it inline with a realistic input and \
+  inspect the output — don't stop at "it imports". Use `bash` to run a one-shot probe, \
+  e.g. `python -c "from mod import fn; print(repr(fn(<realistic input>)))"`, read the \
+  `repr()`, and iterate until it matches expectations.
+- **After a refactor**: run the existing test suite — or if none exists, exercise the \
+  changed path manually and read the result.
+- **After adding or modifying unit tests**: ALWAYS run them before finishing.
+
+A good colleague doesn't stop at "it compiles" — they run it, read the output, and fix \
+the gap between what they wrote and what they meant. Each bug surfaced by a 10-second \
+inline probe is a bug the user never has to report.
+
 ## Reading strategy — read, edit, test
 
-1. **Know the file + have a question?** → `read_file_smart(file_path, query)`
-2. **Need a specific pattern?** → `grep_search(pattern, file_glob="*.py")` — default 10 lines context. \
+1. **Need a specific pattern?** → `grep_search(pattern, file_glob="*.py")` — default 10 lines context. \
 Use `context_lines=30` for full function bodies.
-3. **Need lines for editing?** → `read_file(file_path, start_line=N, end_line=M)` using line numbers from grep
+2. **Need lines for editing?** → `read_file(file_path, start_line=N, end_line=M)` using line numbers from grep
+3. **Need several files at once?** → `read_files(paths)` — parallel batch read
 4. **Need the whole file?** → `read_file(file_path)` — returns first chunk + outline for large files
 5. **Need the COMPLETE file (>60KB)?** → `read_file(file_path, max_size=0)` — reads in chunks. Use rarely.
 
@@ -194,10 +215,9 @@ Skip exploration when the task is clear and the relevant files are obvious.
 
 Every tool call accumulates its result in your context window. Use the minimum needed:
 
-1. **Don't know which file?** → `grep_search` / `glob_search` for patterns, \
-`read_file_smart(file_path, query)` when you know the file.
-2. **Know the file + have a question?** → `read_file_smart(file_path, query)`
-3. **Need specific lines?** → `read_file(file_path, start_line=N, end_line=M)`
+1. **Don't know which file?** → `grep_search` / `glob_search` for patterns.
+2. **Need specific lines?** → `read_file(file_path, start_line=N, end_line=M)`
+3. **Need several files at once?** → `read_files(paths)` — parallel batch read.
 4. **Need the whole file?** → `read_file(file_path)` — returns first chunk + outline for large files.
 
 **NEVER read the same file twice.** Check if you already have the content in context.
@@ -209,7 +229,28 @@ Every tool call accumulates its result in your context window. Use the minimum n
 **Stop early**: Once you have enough information to act, stop exploring and start working. \
 Batch what you need upfront, then execute.
 
-**When adding or modifying unit tests, ALWAYS run them to verify they pass before finishing.**
+## Verification — run it before claiming done
+
+Never mark a task done on faith. Prove the change works by running something that \
+exercises it — invoke the function, trigger the code path, fire the test, and read \
+what comes back. Editing a file is not the same as confirming the edit is correct. \
+When running something is genuinely impossible (no runnable harness, sandbox blocks \
+execution, external service unreachable), state that limitation plainly instead of \
+calling the work done.
+
+Concrete patterns:
+- **After a bug fix**: reproduce the failing case and confirm it now passes.
+- **After writing a plugin/tool/module**: invoke it inline with a realistic input and \
+  inspect the output — don't stop at "it imports". Use `bash` to run a one-shot probe, \
+  e.g. `python -c "from mod import fn; print(repr(fn(<realistic input>)))"`, read the \
+  `repr()`, and iterate until it matches expectations.
+- **After a refactor**: run the existing test suite — or if none exists, exercise the \
+  changed path manually and read the result.
+- **After adding or modifying unit tests**: ALWAYS run them before finishing.
+
+A good colleague doesn't stop at "it compiles" — they run it, read the output, and fix \
+the gap between what they wrote and what they meant. Each bug surfaced by a 10-second \
+inline probe is a bug the user never has to report.
 
 ## Delegation strategy — CRITICAL for context efficiency
 
@@ -218,7 +259,7 @@ For simple, directed lookups (one known file, one specific symbol) use \
 
 For **anything broader** — understanding a system, researching before implementing, \
 analyzing multiple files, writing specs or documentation — **always use explorer agents**. \
-Every `read_file` / `read_file_smart` / `grep_search` result you call directly accumulates \
+Every `read_file` / `read_files` / `grep_search` result you call directly accumulates \
 in YOUR context window and stays there forever. Explorer agents read files in their own \
 isolated context and return only a concise summary. This is critical: \
 **3 explorer summaries < 8 raw file reads** in context cost.

{aru_code-0.24.2 → aru_code-0.25.1}/aru/agents/explorer.py

@@ -7,24 +7,26 @@ from agno.agent import Agent
 from aru.providers import create_model
 from aru.runtime import get_ctx
 from aru.tools.codebase import (
+    _glob_search_tool,
+    _grep_search_tool,
+    _list_directory_tool,
+    _rank_files_tool,
+    _read_file_tool,
     bash,
-    glob_search,
-    grep_search,
-    list_directory,
-    rank_files,
-    read_file,
-    read_file_smart,
+    read_files,
 )
 
-# Read-only tools only — no write/edit/delegate (prevents recursion and mutations)
+# Read-only tools only — no write/edit/delegate (prevents recursion and mutations).
+# All wrappers are async so the Explorer's "multi-parallel tool calls" prompt
+# actually matches runtime behavior — Agno can await them concurrently.
 EXPLORER_TOOLS = [
-    read_file,
-    read_file_smart,
-    glob_search,
-    grep_search,
-    list_directory,
+    _read_file_tool,
+    read_files,
+    _glob_search_tool,
+    _grep_search_tool,
+    _list_directory_tool,
     bash,
-    rank_files,
+    _rank_files_tool,
 ]
 
 EXPLORER_ROLE = """\
@@ -52,7 +54,7 @@ Guidelines:
 - Use glob_search for broad file pattern matching
 - Use grep_search for searching file contents with regex
 - Use read_file when you know the specific file path you need to read
-- Use read_file_smart when you know the file and have a specific question about it
+- Use read_files (batch) when you need to pull several files at once
 - Use bash ONLY for read-only operations (ls, git status, git log, git diff, find, cat, head, tail)
 - NEVER use bash for: mkdir, touch, rm, cp, mv, git add, git commit, npm install, pip install, \
 or any file creation/modification

{aru_code-0.24.2 → aru_code-0.25.1}/aru/agents/planner.py

@@ -6,7 +6,11 @@ from agno.compression.manager import CompressionManager
 from aru.agents.base import build_instructions
 from aru.providers import create_model
 from aru.tools.codebase import (
-    glob_search, grep_search, list_directory, read_file, read_file_smart,
+    _glob_search_tool,
+    _grep_search_tool,
+    _list_directory_tool,
+    _read_file_tool,
+    read_files,
 )
 from aru.runtime import get_ctx
 
@@ -34,8 +38,8 @@ Return ONLY the markdown plan. No explanation, no preamble.\
 
 # Planner uses read-only tools only — no write/edit/bash
 PLANNER_TOOLS = [
-    read_file, read_file_smart,
-    glob_search, grep_search, list_directory,
+    _read_file_tool, read_files,
+    _glob_search_tool, _grep_search_tool, _list_directory_tool,
 ]
 
 

{aru_code-0.24.2 → aru_code-0.25.1}/aru/display.py

@@ -161,6 +161,10 @@ class StatusBar:
         self._index = 0
         self._last_switch = time.monotonic()
         self._override: str | None = None
+        # A single persistent Spinner — Rich's Spinner tracks frames via
+        # (time - start_time), so instantiating a new one per render would
+        # reset start_time each frame and make the animation look frozen.
+        self._spinner = Spinner("dots", text="", style="cyan")
 
     @property
     def current_text(self) -> str:
@@ -187,8 +191,8 @@ class StatusBar:
 
     def __rich_console__(self, console: Console, options: ConsoleOptions) -> RenderResult:
         self._maybe_rotate()
-        spinner = Spinner("dots", text=f"[dim]{self.current_text}[/dim]", style="cyan")
-        yield from spinner.__rich_console__(console, options)
+        self._spinner.update(text=Text(self.current_text, style="dim"))
+        yield from self._spinner.__rich_console__(console, options)
 
     def __rich_measure__(self, console: Console, options: ConsoleOptions) -> Measurement:
         return Measurement(1, options.max_width)
@@ -196,7 +200,7 @@ class StatusBar:
 
 TOOL_DISPLAY_NAMES = {
     "read_file": "Read",
-    "read_file_smart": "ReadSmart",
+    "read_files": "ReadBatch",
     "write_file": "Write",
     "edit_file": "Edit",
     "glob_search": "Glob",
@@ -209,7 +213,7 @@ TOOL_DISPLAY_NAMES = {
 
 TOOL_PRIMARY_ARG = {
     "read_file": "file_path",
-    "read_file_smart": "file_path",
+    "read_files": "paths",
     "write_file": "file_path",
     "edit_file": "file_path",
     "glob_search": "pattern",