Enhanced Grep logging with glob filter

[djdarcy]

Summary

Include the file glob filter alongside the search pattern in Grep log entries.

Current Behavior

[[2026-02-01 18:55:24]] {Grep: useTranslation }

Pattern is logged but not which files were searched.

Desired Behavior

[[2026-02-01 18:55:24]] {Grep: useTranslation | "*.tsx" }

Use pipe separator to visually demarcate pattern from glob filter.

Implementation

elif tool_info.name == "Grep":
    pattern = tool_input.get("pattern", "")
    glob_filter = tool_input.get("glob", "")
    if glob_filter:
        return f'{pattern} | "{glob_filter}"'
    return pattern

Notes

• output_mode not needed (doesn't affect what was searched)
• Pipe chosen over ellipsis for compactness
• Only show glob when present (many Grep calls don't use it)

Analysis

See 2026-02-01__19-10-22__session-logger-enhancements-analysis.md for detailed analysis.

[djdarcy]

✅ Implemented in v0.1.4

Grep logging now includes glob filter when present:

{Grep: useTranslation | "*.tsx" }
{Grep: TODO }  # No glob, no suffix

Implementation matches the proposed format with pipe separator.

Ready to close once v0.1.4 is released.

[djdarcy]

Additional Enhancement - Path Context

The original implementation only showed glob filter but not the search path. When searching a specific file (without glob), there was no indication of what was searched.

Fix Added

Now shows in "{path}" with smart handling:

Scenario	Output
Glob only, searching cwd	{Grep: pattern | "*.tsx" }
Specific file	{Grep: pattern in "C:\full\path\file.py" } (clickable)
Directory inside cwd	{Grep: pattern in "hooks/scripts/" } (relative, compact)
Directory outside cwd	{Grep: pattern in "C:\other\project" } (full path)

Rationale

• Files get full paths for VS Code clickability (key feature)
• Directories inside cwd get relative paths (compact, user knows context)
• Directories outside cwd get full paths (need full context)
• Searching cwd itself omits path (user knows where they are)

This completes the Grep logging enhancement.

[djdarcy]

Update: Consistent Separator Format

Changed path-only case to use | instead of in for cleaner scanning:

Updated Format

{Grep: pattern | "*.py" }                    ← glob only
{Grep: pattern | "C:\path\file.py" }         ← path only (| not "in")
{Grep: pattern | "*.json" in "dir/" }        ← glob + path ("in" distinguishes them)

Rationale

• | is always the separator after pattern
• in only appears when needed to distinguish glob from path
• Easier to visually parse - no need to mentally filter "in" as non-regex content