Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Capture descriptions: support any OpenAI-compatible vision endpoint

Aperta
  • Qualcosa non va?
#4,846 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@FenjuFu ci sta già lavorando.

Dal 1/10/2026.

  • #4849 di @FenjuFu — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
ai, cli

Direzione di ricerca

Start in packages/cli/src/capture/contentExtractor.ts, focusing on captionImagesWithGemini and the existing OpenRouter request branch. Trace postExtractionPhase to understand credential detection and degraded reporting. Done means custom endpoint credentials are handled as specified, OpenRouter behavior remains unchanged, and the no-credentials guidance mentions the custom endpoint.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

hyperframes capture describes downloaded images only through OpenRouter, Vertex or the Gemini API (captionImagesWithGemini in packages/cli/src/capture/contentExtractor.ts). None of them is reliably reachable from mainland China, and none can point at a self-hosted vision model. Users in that position get the catalog-fallback asset-descriptions.md on every capture, even when they already pay for an OpenAI-compatible vision endpoint or run one locally.

Proposed solution

Bring back the three variables from #1809 on current main: HYPERFRAMES_VISION_BASE_URL, HYPERFRAMES_VISION_API_KEY and HYPERFRAMES_VISION_MODEL.

  • All three set: caption through <base>/chat/completions with the OpenAI-style request the OpenRouter branch already sends, ahead of OpenRouter, Vertex and Gemini.
  • Some but not all set: warn naming the missing variables (never echoing values), skip captioning, and report the phase as degraded. Never fall back to another provider.
  • OpenRouter shares the same request helper and keeps its URL, auth header and error text unchanged.
  • postExtractionPhase counts a complete custom endpoint as vision credentials, and the no-credentials hint mentions it.

I have this ready and will open a PR that links here.

Alternatives considered

A named preset per regional provider. Every one of them speaks the same chat-completions wire format, so a single base-URL setting covers them all and also covers local Ollama and vLLM.

Additional context

The #1809 review called the base-URL approach "the right shape" and asked for one fix: setting only some of the variables fell through silently and could caption through Gemini, the provider the user is trying to avoid. That PR was closed for merge conflicts and inactivity, before Vertex support (#3561) landed in the same function.

To check that the request shape works outside OpenRouter, I sent exactly what the OpenRouter branch builds today (one image_url data URI, the storyboard prompt, max_tokens: 500) to iFlytek Astron's Token Plan, an OpenAI-compatible endpoint (https://maas-token-api.cn-huabei-1.xf-yun.com/v2). The image was docs/images/image-thumbnail-evidence/after.png.

Model HTTP finish Caption
xopkimik26 (Kimi-K2.6) 200 stop A dark gray webpage displays white text reading "Timeline JPEG thumbnail resource check" with a horizontal strip of rainbow-colored vertical bars beneath it.
xopqwen35397b (Qwen3.5-397B) 200 stop A dark background displays a horizontal strip of repeating colorful vertical bars labeled "Synthetic JPEG chart" …
xopqwen36v35b (Qwen3.6-35B) 200 stop A dark-background interface displays a narrow, horizontally stretched bar of repeating rainbow-colored vertical stripes …
spark-x2.5 (text-only) 400 invalid request

None of the vision models spent the 500-token budget on reasoning. The text-only row is why the docs should say to choose a model that accepts image input.

Lingua principale
TypeScript
Stelle
54.1k
Fork
4.9k
Merge medio
7h 18m
PR unite (30g)
784

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di heygen-com/hyperframes

Tutte le issue di heygen-com/hyperframes

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.