Onboarding follows the vision provider
The wizard's fresh config.toml now carries both [vision.*] blocks, and its credential pass reads the ACTIVE provider before prompting: an anthropic setup asks for ANTHROPIC_API_KEY as before, a keyed openai-compatible endpoint asks for its configured key_env instead, and a keyless local runtime says so and asks for nothing. Doc sweep for the same: README's stage list and knobs line, CLAUDE.md's config summary (which still claimed username lived there), the Help flow's "Claude vision" wording, and .env.example's ANTHROPIC_API_KEY note. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016jXZFSTZQKzAC8fqpWSz9g
This commit is contained in:
co-authored by
Claude Fable 5
parent
118503e4e0
commit
15d3120029
@@ -19,7 +19,7 @@ BGG has no bulk import and no write API. Cataloging a few hundred games by hand
|
||||
|
||||
## How it works
|
||||
|
||||
1. **extract** — Shelf photos go to the Anthropic API (Claude vision), which reads game titles off spines and boxes along with edition cues: publisher, edition wording, print year, language.
|
||||
1. **extract** — Shelf photos go to a vision model (Claude by default; any OpenAI-compatible endpoint or a local Ollama model works), which reads game titles off spines and boxes along with edition cues: publisher, edition wording, print year, language.
|
||||
2. **resolve** — Titles are matched to BGG game IDs via the [XML API2](https://boardgamegeek.com/wiki/page/BGG_XML_API2) (exact + fuzzy matching, popularity tiebreaks), then edition cues are matched against BGG's version list for each game. Anything uncertain is flagged rather than guessed.
|
||||
3. **review** — A local review step for ambiguous matches: pick the right game/version, or leave the version blank. Wrong guesses never reach your collection.
|
||||
4. **diff** — Your existing BGG collection is fetched and compared, per copy (owning one edition of a game doesn't hide a second edition you also own).
|
||||
@@ -93,7 +93,7 @@ Secrets live in environment variables only, never in config files, code, or logs
|
||||
| `BGG_USERNAME` | diff, upload, enrich | Your BGG username (public, but kept in `.env` so it lives in one place) |
|
||||
| `BGG_PASSWORD` | upload (website login) | Your BGG password |
|
||||
|
||||
Non-secret knobs (`photos_dir`, `data_dir`, the vision model, the rate limit) live in `config.toml`. From here you can drive everything from the browser:
|
||||
Non-secret knobs (`photos_dir`, `data_dir`, the per-provider vision blocks, the rate limit) live in `config.toml`. From here you can drive everything from the browser:
|
||||
|
||||
```sh
|
||||
uv run bggpipe web # opens http://127.0.0.1:8377/ — the whole app in the browser
|
||||
|
||||
Reference in New Issue
Block a user