feat: add list_files and grep_file skills tools#2267
Open
brandonkeung wants to merge 5 commits into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR extends Kagent’s agent toolsets (Go + Python runtimes) with native, in-process filesystem visibility tools—list_files and grep_file—so agents can inspect session/skills files without relying on bash (which may be disabled). It also adjusts Go path-resolution and tool construction behavior to be more robust around symlinked roots and missing sandbox-runtime settings.
Changes:
- Added
list_files/grep_filetool descriptions and implementations for both Python (kagent-skills,kagent-adk) and Go (go/adk/pkg/skills,go/adk/pkg/tools). - Updated Go tool initialization to omit
bashwhen sandbox-runtime settings are unavailable, instead of failing the entire toolset. - Added/expanded unit tests covering new directory listing and grep behaviors across both runtimes.
Reviewed changes
Copilot reviewed 12 out of 12 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| python/packages/kagent-skills/src/kagent/tests/unittests/test_skill_execution.py | Adds unit tests for list_dir_content / grep_content (including traversal/recursive/error cases). |
| python/packages/kagent-skills/src/kagent/skills/shell.py | Implements list_dir_content and grep_content core logic. |
| python/packages/kagent-skills/src/kagent/skills/prompts.py | Adds standardized prompt/description text for list_files and grep_file. |
| python/packages/kagent-skills/src/kagent/skills/init.py | Exposes new functions/descriptions in the public skills package API. |
| python/packages/kagent-adk/src/kagent/adk/tools/skills_toolset.py | Adds ListFilesTool/GrepFileTool to the default ADK toolset. |
| python/packages/kagent-adk/src/kagent/adk/tools/skills_plugin.py | Ensures agents get list_files / grep_file tools when missing. |
| python/packages/kagent-adk/src/kagent/adk/tools/file_tools.py | Introduces ADK tool wrappers ListFilesTool and GrepFileTool wired to skills implementations. |
| python/packages/kagent-adk/src/kagent/adk/tools/init.py | Exports the new tool classes. |
| go/adk/pkg/tools/skills.go | Adds Go list_files/grep_file, makes bash optional, and adjusts symlink root resolution. |
| go/adk/pkg/tools/skills_test.go | Adds tests for toolset composition and end-to-end tool invocation via functiontool.Run(). |
| go/adk/pkg/skills/shell.go | Adds Go implementations ListDirContent and GrepContent. |
| go/adk/pkg/skills/shell_test.go | Adds unit tests for the new Go directory listing and grep functions. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
brandonkeung
force-pushed
the
feat/grep-list-files-tools
branch
from
July 15, 2026 21:01
14ac799 to
7b55923
Compare
Adds native, in-process list_files and grep_file tools to both the Go and Python agent runtimes, alongside the existing read_file/write_file/ edit_file/bash skills tools. Gives agents safe, non-privileged file visibility without depending on bash, which some deployments disable for privilege/security reasons. Also fixes two related bugs found while implementing and testing this: - Go: a symlink-resolution inconsistency in resolveReadPath/ resolveWritePath/resolveEditPath could reject valid paths under a symlinked session root. - Go: NewSkillsTools failed entirely (dropping all tools) when the bash command executor couldn't be constructed, instead of omitting bash. Signed-off-by: brandonkeung <brandonlkeung@gmail.com>
- Skip symlinked entries that resolve outside the searched root during recursive grep_file, in both the Go and Python implementations. A symlink inside an otherwise-jailed directory (e.g. from an untrusted skill package) could previously be followed to read file contents outside the intended sandbox. - Bound the Go grep scanner's line buffer (was capped at the default 64KiB bufio.Scanner token size, which errored on long lines such as minified JSON). - Reject an empty path explicitly in the Go grep_file tool instead of surfacing a confusing "no file path provided" error from deeper in the call stack. Signed-off-by: brandonkeung <brandonlkeung@gmail.com>
Adds the two new tools to the quick-start import example and the Tool Workflow table, and notes the symlink-escape protection in the Security section, matching how the existing read_file/write_file/ edit_file/bash tools are already documented there. Signed-off-by: brandonkeung <brandonlkeung@gmail.com>
Thermos branch review turned up a real bug introduced by the previous symlink-escape fix, plus a consolidation opportunity and a missing timeout: - Go: `root, err := filepath.EvalSymlinks(path)` inside GrepContent's `if info.IsDir()` block shadowed the outer `err`, so a WalkDir failure was never observed by the `err != nil` check afterward. Combined with an in-bounds directory symlink (which WalkDir doesn't recurse into, and which grepFile can't read as a file), this caused the walk to abort silently partway through, returning a truncated "success" result with no error. Fixed by not shadowing err, and by explicitly skipping symlinked directories instead of letting grepFile fail on them. - Go: consolidated the symlink-escape containment check into a single shared `skillruntime.WithinRoot` helper (previously GrepContent had its own filepath.Rel-based check, duplicating the pre-existing isWithinRoot used by resolveReadPath/resolveEditPath/resolveWritePath) so there's one implementation of this security-relevant property instead of two that could drift. - Python: grep_file's regex match now runs via asyncio.to_thread with a 30s asyncio.wait_for timeout, mirroring the timeout bash already enforces. Python's re engine backtracks and a pathological, agent-controlled pattern run synchronously inside an async def could otherwise block the whole event loop indefinitely (Go is unaffected; its regexp package is RE2-based and linear-time). - Mention list_files/grep_file in the bash tool's own description in both languages, and log (debug level) when bash is omitted because the sandbox-runtime isn't configured, so its absence isn't silent. Verified live: both Go and Python runtime pods rebuilt and redeployed, confirmed via the UI that a recursive grep_file across a working directory containing the skills/ symlink (the exact scenario the shadowing bug silently broke) now correctly finds matches on both sides of the symlink. Signed-off-by: brandonkeung <brandonlkeung@gmail.com>
…d failures Across several review passes on grep_file/list_files, close out the remaining correctness gaps in the recursive-search path (Go and Python): - Fix filepath.WalkDir root resolution so an unresolved symlink root is actually recursed into, and fix an err-shadowing bug that silently truncated results on a WalkDir failure. - Skip non-regular files (FIFOs, sockets, devices) before opening them -- previously a FIFO with no writer connected would hang the search indefinitely, in both the recursive walk and single-target paths. - Cap matched lines to 2000 chars (matching read_file's existing convention); previously unbounded in Python and could fail the whole search past 1MB in Go. - Give GrepFileTool a dedicated thread pool in Python instead of the shared default pool, since a hung regex match can't be forcibly killed and would otherwise starve unrelated work. - Treat a single unreadable file or subdirectory as a skip rather than aborting the whole search, so one bad entry doesn't discard matches already found elsewhere in the tree. Annotate "no matches found (N entries could not be read)" when skips occurred, so a systemic failure isn't indistinguishable from a genuinely empty search. - Surface a real error, instead of a misleadingly confident empty result, when the search root itself is unreadable. - Extract Go's classifyWalkEntry and Python's _resolve_working_path helpers to keep the now-more-involved walk logic readable. Regression tests added for each fix above, verified to fail against the prior code. Signed-off-by: brandonkeung <brandonlkeung@gmail.com>
brandonkeung
force-pushed
the
feat/grep-list-files-tools
branch
from
July 16, 2026 19:08
8f8fb8c to
041e747
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
list_filesandgrep_filetools to both the Go (go/adk/pkg/skills,go/adk/pkg/tools) and Python (kagent-skills,kagent-adk) agent runtimes, alongside the existingread_file/write_file/edit_file/bashskills tools.bash, which some deployments disable for privilege/security reasons.resolveReadPath/resolveWritePath/resolveEditPathcould reject valid paths under a symlinked session root.NewSkillsToolsfailed entirely (dropping all tools) when the bash command executor couldn't be constructed, instead of just omitting bash.filepath.WalkDirroot resolution fixed so an unresolved symlink root is actually recursed into; an err-shadowing bug that silently truncated results on aWalkDirfailure fixed.grep_fileno longer hangs indefinitely on a FIFO (or other non-regular file) with no writer connected, in both the recursive walk and single-target paths.read_file's existing convention) — previously unbounded in Python, and could fail the whole search past 1MB in Go.GrepFileToolnow uses a dedicated thread pool instead of the shared default pool, since a hung regex match can't be forcibly killed and would otherwise starve unrelated work."no matches found (N entries could not be read)"so a systemic failure isn't indistinguishable from a genuinely empty search.Test plan
TestGrepContent(go/adk/pkg/skills/shell_test.go) — matches, recursion, symlink escape/resolution, FIFO hang safety, unreadable file/subdirectory/root handling, output truncation — andTestListFilesAndGrepFileTools_RunThroughADK,TestNewSkillsTools_OmitsBashWithoutSRTSettings(go/adk/pkg/tools/skills_test.go)kagent-skills/kagent-adkcovering the same scenarios (path traversal, recursive/ignore-case, symlink escape, FIFO hang safety, unreadable file/subdirectory/root handling, truncation,GrepFileTooltimeout behavior)list_files/grep_fileby name and returning correct output