grep
tool judged 2% likely a named technique or architecture
See how it has spread across media tiers
Mentions over time
Table view
| Week | Articles | Sources |
|---|---|---|
| 2025-W28 | 1 | 1 |
| 2025-W51 | 1 | 1 |
| 2026-W01 | 2 | 1 |
| 2026-W03 | 1 | 1 |
| 2026-W11 | 1 | 1 |
| 2026-W13 | 1 | 1 |
| 2026-W18 | 1 | 1 |
| 2026-W24 | 1 | 1 |
| 2026-W26 | 1 | 1 |
| 2026-W30 | 1 | 1 |
| 2026-W35 | 1 | 1 |
| 2026-W37 | 1 | 1 |
| 2026-W39 | 1 | 1 |
| 2026-W40 | 8 | 4 |
| 2026-W41 | 1 | 1 |
In their words
● Grep "retry" in acme-app 212 matches ● Read payments/retry.py ● Read payments/gateway.py ● Read billing/invoices.py ● Read tests/test_payments.py … 36 more files Still looking for the backoff rule… › Why do card retries stop after a decline?
git grep -nE 'git apply|gh pr merge|git push|patch -p' -- .github scripts || true List every secret name that an agent process could read, and mark any name that can push, deploy, or open a firewall change.
#!/usr/bin/env bash # proposal: unexecuted junior gate for an agent diff set -euo pipefail BASE = " ${ 1 :- origin /main } " MAX_FILES = " ${ MAX_FILES :- 8 } " MAX_LINES = " ${ MAX_LINES :- 200 } " git rev-parse --is-inside-work-tree > /dev/null FILES = " $( git diff --name-only " ${ BASE } ...HEAD" || true ) " COUNT = " $( printf '%s\n' " $FILES " | sed '/^$/d' | wc -l | tr -d ' ' ) " STAT = " $
Command mapping The parser translates common flags and subcommands: npm i -D <pkgs> becomes pnpm add -D <pkgs> npx <cmd> becomes pnpm dlx <cmd> npm ci becomes pnpm install --frozen-lockfile npm cache clean --force becomes pnpm store prune npm init <template> becomes pnpm create <template> Commands that only mention npm inside strings or arguments, like git commit -m "fix npm bug" or grep -r "npm"
Deterministic arm configuration (JSON) { "providers" : { "deepseek" : { "url" : "https://api.deepseek.com" , "format" : "openai" }, "deepseek-anthropic" : { "url" : "https://api.deepseek.com/anthropic" , "format" : "anthropic" } }, "plugins" : { "order" : [ "schema_translator" , "intent" , "keyword_compactor" ], "config" : { "keyword_compactor" : { "tool_policies" : [ { "match" : "read*" , "mode"
As a permissions config: { "permissions": { "allow": ["Read","Edit","Write","Grep","Glob", "Bash(git add:*)","Bash(git commit:*)", "Bash(npm test:*)","Bash(npm run:*)","Bash(npm ci:*)","Bash(pytest:*)"], "ask": ["Bash(git push:*)","Bash(npm publish:*)","Bash(aws:*)","Bash(terraform apply:*)","Bash(kubectl apply:*)"], "deny": ["Bash(git push --force:*)","Bash(git push -f:*)","Bash(*--no-verify*)"]
Grep the whole company; diff any change; roll any part of it back.
It issues many small questions to answer one large one, often at the same time, and every result it receives consumes context, and can add cost and latency to subsequent model calls.” Nwokah explains that Grep (the command-line tool that searches plain text for line matches on a specific keyword or pattern) returns matches, and the agent goes on to read whole files.