dzhng/jevgrep: first run, 2026-10-11
Installed from its README in a throwaway sandbox by Claude Code (Claude Opus 5.5), with a Jev API key in the environment and nothing else: no GPU, no desktop, no other paid keys, no accounts. The README's first example was run once. Repo commit 703aba1a36a3; 60 seconds. All results · Task
Quick start: ran. Jev calls made: 11.
| Install | npm install -g @dzhng/jevgrep (failed EACCES on /usr/local/lib/node_modules; then: npm config set prefix ~/.npm-global && npm install -g @dzhng/jevgrep, with ~/.npm-global/bin on PATH) -> jg 0.8.0 |
|---|---|
| Quick start, as run | printf '%s' "$TYPESAFE_API_KEY" | jg auth --provider typesafe --stdin; jg doctor; jg "How are telemetry events recorded and sent?" ./apps/cli --max-requests 10 (run from ~/src) |
| What came back | auth: 'TypeSafe key saved.' doctor: 'Jev connection verified through TypeSafe.' search exit 0: 'Jevgrep: 1 relevant files. ... - "src/index.ts" — relevant; role uncertain; locations only ... Declaration locations: - "src/index.ts" End context.' Thin result (locations only, no source excerpts), plausibly because the CLI has no telemetry code and the request cap was low. |
| What stopped it | Nothing. |
Steps the README does not mention
- Global npm install failed with EACCES (machine's /usr/local is root-owned); set a user npm prefix (~/.npm-global) and added its bin to PATH instead of using sudo
- Used non-interactive 'jg auth --provider typesafe --stdin' (documented in apps/cli/README.md and jg --help, not the top-level README) because 'jg auth' is interactive
- Skipped 'jg skill' (agent-skill installer, needs interactive agent selection; does not call Jev and is not needed for the search)
- README example targets a placeholder ./my-project; substituted the repo's own small ./apps/cli (17 files) as the search root
- Added --max-requests 10 (default ceiling is 1000) to keep Jev calls to a handful
The session's closing message
jevgrep (`jg` 0.8.0) installed and ran its quick start search; the search came back with a real but very thin answer. - **Install:** the README's `npm install -g @dzhng/jevgrep` failed with a permission error, because this machine's global npm folder is owned by root. That's a machine issue, not the project's. I pointed npm at a folder in my home directory (`~/.npm-global`), added it to PATH, and it installed cleanly. - **Auth:** the README's `jg auth` asks questions interactively. I used the scriptable form, `jg auth --provider typesafe --stdin`, with the key piped in from TYPESAFE_API_KEY. That form is documented in `apps/cli/README.md` and `jg --help`, not in the main README. `jg doctor` then reported "Jev connection verified through TypeSafe." - **Quick start:** I ran the README's question, `jg "How are telemetry events recorded and sent?"`, against the repo's own small CLI folder `./apps/cli` (17 files), since the README's `./my-project` is just a placeholder. I added `--max-requests 10` to keep Jev calls to a handful; the default limit is 1000. - **Result:** it exited cleanly with "1 relevant files: `src/index.ts` — relevant; role uncertain; locations only". There were no source excerpts. The likely reasons are that this folder has no telemetry code and my request cap was low. - **Skipped:** `jg skill`, which installs the coding-agent skill. It prompts interactively and doesn't call Jev. - **Jev calls:** at most 11 (1 from `jg doctor` plus up to 10 from the search). The report records 11 because I don't have an exact count. Nothing blocked the run, and the API key was never printed or written to a file. DELIVERABLE: ~/work/output/report.json