Question 1

What is strayguard and what problem does it solve?

Accepted Answer

It is a git pre-commit hook that checks files newly added to a commit and flags ones that do not look like part of the project, such as throwaway scripts, debug dumps, data exports, build output and local config. You run git commit as usual and only see output when something looks wrong.

Question 2

How does strayguard use Jev?

Accepted Answer

Each new file that local rules do not already match is sent to Jev, which picks one of five categories and returns a probability. If Jev is at least 70% sure a file does not belong, strayguard shows it to you with the category and probability. Jev never writes text; it only picks a category and returns a probability.

Question 3

How do I install and run strayguard?

Accepted Answer

You need Python 3.9+ and a TypeSafe API key. Install with pipx install strayguard, export TYPESAFE_API_KEY, then run strayguard install inside your repo to add .git/hooks/pre-commit. The README says there is no config file.

Question 4

What happens at the strayguard prompt and what do the keys do?

Accepted Answer

The prompt lists suspect files with categories and probabilities. Press u to unstage them, g to add them to .gitignore and unstage them, k to keep and commit anyway, o to decide file by file, or Enter to keep everything. The commit stops only when strayguard changed something, and it never deletes files.

Question 5

Does strayguard send my file contents to TypeSafe?

Accepted Answer

Local rules run first: files matching rules like .env and .DS_Store are never sent anywhere. The remaining new files go to Jev for classification, and results are cached so the same file always gets the same answer. The digest does not detail what portion of a file's content is transmitted.

Question 6

Can I use strayguard with the pre-commit framework or other tools?

Accepted Answer

Yes. Add it to .pre-commit-config.yaml with repo https://github.com/Eve2512/Strayguard, rev v0.1.0 and id strayguard. The pre-commit framework captures hook output, so strayguard cannot ask interactive questions there; it shows the warning and lets the commit through.

Question 7

What are strayguard's limits?

Accepted Answer

By its own comparison table it only looks at files that are new in the current commit, not changes to files git already tracks. The README visible in the digest cuts off in its GUI clients, CI and coding agents section, so behaviour outside a terminal is only partly documented, and no accuracy benchmarks are published.

Strayguard

Highlights

Quickstart

Questions about this entry

From the Jev guides

From the Jev AI model community