You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**Per-repository aggregation** — results grouped by repo, not as a flat list; fold/unfold each repo to focus on what matters
37
37
-**Keyboard-driven TUI** — navigate with arrow keys, toggle selections, filter by file path, confirm with Enter — without leaving the terminal
38
38
-**Fine-grained selection** — pick exactly the repos and extracts you want; deselected items are recorded as exclusions in the replay command
39
-
-**Structured output** — clean Markdown lists with GitHub links, or machine-readable JSON — ready to paste into docs, issues or scripts
39
+
-**Structured output** — Markdown document with a `# Results for` query heading, GitHub deeplinks and the exact matched token per extract; or machine-readable JSON that, when segment data is available, includes `matchedText`, `line` and `col` fields — ready to paste into docs, issues or scripts
40
40
-**Team-prefix grouping** — group results by team prefix (e.g. `platform/`, `data/`) using `--group-by-team-prefix`
41
41
-**Replay command** — every session produces a one-liner you can run in CI to reproduce the exact same selection without the UI
42
+
-**Regex search** — use `/pattern/flags` syntax for pattern-based searches; the CLI derives a safe API query and filters results locally
42
43
-**Syntax highlighting** — code fragments rendered with language-aware coloring (TypeScript, Python, Go, Rust, YAML, JSON and more)
43
44
44
45
## Use cases
@@ -111,6 +112,7 @@ The official [`gh` CLI](https://cli.github.com/) does support `gh search code`,
Each extract link points directly to the matching line on GitHub.
35
+
Each extract link points directly to the matching line on GitHub. When the GitHub API returns the exact matched token, it is appended inline after the link — for example:
Every output — in both Markdown and JSON formats, and for both `repo-only` and `repo-and-matches` output types — is prefixed with a `# Results for` heading that identifies the search query. When active qualifiers are present, they are appended after a `·` separator:
44
+
45
+
```text
46
+
# Results for "useFeatureFlag" · including archived · excluding templates
47
+
```
48
+
49
+
In [regex mode](/usage/search-syntax#regex-mode), the pattern is shown in backticks:
0 commit comments