grev

Unix filters that ask questions instead of matching patterns.

$ cat examples/menu.txt
chicken tikka masala
fresh fruit salad
spaghetti carbonara
tofu stir fry with rice

$ grev 'is a vegan meal' examples/menu.txt
fresh fruit salad
tofu stir fry with rice

The tools run on TypeSafe's Jev models, which answer typed questions with calibrated probabilities instead of generating text. That's why these tools behave like grep, sort or cut: output is always your input. Labels and scores appear only as explicit columns. A few thousand lines cost fractions of a cent and take seconds.

Examples

# Search logs by meaning
grev --about 'nginx error log' 'says the upstream server timed out' examples/nginx-error.log
journalctl -fu myapp | grev --line-buffered --about 'application log' 'shows the process crashed'
git log --oneline | grev --about 'commit messages' 'fixes a bug'

# Guard a commit: exit 0 means yes
git diff --cached | isv 'adds a secret or credential' && echo 'refusing to commit' && exit 1

# Label, route, rank
tagv billing technical feature-request other < examples/tickets.txt
tagv --split tickets/ billing technical other < examples/tickets.txt
rank -s -m3 -L 'not urgent|soon|urgent|critical' 'How urgent is the ticket {}?' examples/tickets.txt

# Find, cut, dedupe, reflow
man tar | pickv 'how do I list the contents of an archive?'
cutv 'email address' 'phone number' < examples/users.csv
uniqv -c 'Are {1} and {2} the same company?' examples/companies.txt
unwrap examples/memo.txt
seek --verify 'the spend ledger' .

# Bisect by meaning: the first health check that reports a failure (3 requests for 600 lines)
lookv -n --about 'health checks, one per minute' 'reports a failing dependency' examples/lookv-health.log

# Probabilities as columns, for awk
probev -H -q 'refund: asks for money back' -q 'angry: the writer is angry' < examples/tickets.txt

Every tool has --help and a man page. The common flags:

Install

• Packages: deb, rpm, apk, Arch packages and archives for Linux, macOS, FreeBSD and Windows are on the releases page. packaging/arch/PKGBUILD builds from source.
• With Go: go install github.com/aurorainfra/grev/cmd/...@latest
• From source: make && sudo make install, which also installs the man pages and bash/zsh/fish completions.

Configure

Everything lives in one file, ~/.grevconfig, in git-config style; the full reference is docs/CONFIG.md (or man grevconfig). jev key set puts your API key there with mode 0600:

[api]
	key = tsk-…                           ; written by `jev key set`
[defaults]
	progress = auto                       ; the -p overlay whenever stderr is a terminal
	jobs = max
	confirmAbove = 0.25                   ; ask before runs quoted above $0.25 (built-in: $1)
[limits]
	daily = 5                             ; spend caps in USD, across all tools
	monthly = 50
[tool "grev"]
	about = application logs              ; per-tool defaults for any long option,
	threshold = 0.7                       ; e.g. how sure the model must be to say yes

Thresholds are set per tool because -t means different things: P(yes) in grev, the minimum confidence of a choice in tagv, a path score in seek.

Manage it with jev config set limits.daily 5 or jev config list --show-origin, and check your spend with jev spend. Command-line flags beat environment variables, which beat the config. In CI, TYPESAFE_API_KEY supplies the key without any file.

Cost and safety

Jev charges $0.042 per million input tokens, and output is free. Grepping a 4,000-line source file costs about $0.008.

Nothing big runs by surprise:

• Any run quoted above confirmAbove ($1 unless configured) asks first. Without a terminal, it refuses.
• --max-cost and the daily/monthly caps stop a run before it goes over.
• Closing the output pipe (| head) stops the spending.

More

• docs/DESIGN.md: how the tools phrase questions and why, the evals, flag conventions and the cost model.
• docs/CONFIG.md: configuration in depth.
• Man pages: grev-tools(7), grevconfig(5), and one per tool.

License

Licensed under either of Apache License, Version 2.0 or MIT license, at your option.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.