Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

find_files drops bracket-prefixed paths in narrowed searches

Open Beginner friendly
#185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
cli, tooling

Research direction

Look for the find_files function or Step adapter that processes native find tool output. The bug is in a filter that strips lines starting with '[' or 'WARNING:'. Identify where this filtering happens, adjust the logic to distinguish between tool notices and valid file paths (like [id]/page.tsx), and add a test case for Next.js-style route directories.

Written by the indexing model from the issue text.

Description

What happened?

find_files can silently drop valid matches when the returned relative path starts with [ or WARNING:.

A common case is a narrowed search inside a Next.js routes directory. With routes/[id]/page.tsx present, find_files with path: "routes" returns (no matches), even though the native find backend returns [id]/page.tsx correctly. The same reproduces with [...slug] and [[...slug]].

The Step adapter currently strips every native output line starting with [ or WARNING:, so valid paths are treated as notices.

I reproduced this on clean main @ f113768 with the built-in tool profile and project-native Vitest, without external extensions.

Steps to reproduce
  1. Create routes/[id]/page.tsx.
  2. Run find_files with: 
    { "pattern": "*.tsx", "path": "routes" }
  3. The native find tool returns [id]/page.tsx.
  4. The Step-facing find_files result is (no matches), with matchedFiles: 0 and returnedFiles: 0.
Expected behavior

Valid file paths should not be removed because their relative path happens to start with text used by native notices.

Version

main @ f113768 / @step-harness/coding-agent 0.84.4

Dominant language
TypeScript
Stars
54
Forks
20
Avg merge
4h 1m
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stepfun-ai/Step-Code

All issues in stepfun-ai/Step-Code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.