superagents-lab/jev-search: 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 a98f724ad742; 103 seconds. All results · Task

Quick start: did not run. Jev calls made: 0.

Install	`corepack enable (failed: EACCES on /usr/local/bin) -> corepack enable --install-directory ~/.local/bin; pnpm install --frozen-lockfile; cp .dev.vars.example .dev.vars`
Quick start, as run	`pnpm dev (with TYPESAFE_API_KEY set in .dev.vars, JEV_PROVIDERS=typesafe), then open http://localhost:3030 and search`
What came back	Dev server failed to start: 'Error: Failed to start the remote proxy session ... Could not start remote dev session. No credentials found, and the environment is non-interactive so browser login cannot be started. Either: Set a CLOUDFLARE_API_TOKEN environment variable, Run `wrangler login`' -> ELIFECYCLE Command failed with exit code 1.
What stopped it	Two missing credentials, both required by the README: (1) a Cloudflare account (wrangler login or CLOUDFLARE_API_TOKEN), because pnpm dev always opens a remote Workers AI session even when JEV_PROVIDERS=typesafe; (2) a SEARCH1API_API_KEY (a separate paid Search1API key, required for every search). Neither is on this machine.

Steps the README does not mention

corepack enable fails without root (EACCES symlinking into /usr/local/bin); had to use corepack enable --install-directory ~/.local/bin and add it to PATH
Set COREPACK_ENABLE_DOWNLOAD_PROMPT=0 so corepack could download pnpm 10.8.0 without a prompt
pnpm install printed 'Ignored build scripts: esbuild, sharp, workerd' (pnpm approve-builds); README does not mention it (the dev server failed before this mattered)

The session's closing message

The install worked, but I couldn't get the quick start to run: it needs two credentials this machine doesn't have. No Jev calls were made.

- **Install:** worked, with one step the README doesn't mention. Its `corepack enable` failed because it needs write access to `/usr/local/bin`. I ran `corepack enable --install-directory ~/.local/bin` instead and added that folder to PATH. After that, `pnpm install --frozen-lockfile` finished (pnpm 10.8.0). It warned that it had skipped the setup scripts for esbuild, sharp and workerd, which the README also doesn't mention.
- **Quick start (`pnpm dev`):** failed straight away. It stopped with "Could not start remote dev session. No credentials found… Set a CLOUDFLARE_API_TOKEN or run `wrangler login`." The README warns about this: `pnpm dev` always opens a remote Cloudflare session, even when TypeSafe is the only model configured.
- **What blocked it:**
  - **Cloudflare account:** the server won't start without a Cloudflare login or API token.
  - **Search1API key:** every search also needs a `SEARCH1API_API_KEY`, a separate paid key, which isn't in the environment either. Starting the server would still not have produced a search result without it.

I put the key in `.dev.vars` as the README says, then deleted that file when I stopped so the key isn't left on disk. The key was never printed. Results and the extra steps are recorded in the report.

DELIVERABLE: ~/work/output/report.json