Spaces:
Sleeping
Sleeping
Commit History
-
fix: make workdir writable for config/cookie generation at runtime
a7fbd75 -
Configure for Hugging Face Space (Docker): port 7860, non-root user, secret-driven config via run.py
fd2eea3
-
fix: surface BardErrorInfo as error instead of silent null content
When Gemini upstream returns BardErrorInfo (e.g. [1060] from Docker bridge networks), the server now returns a proper 502 error with the error code instead of silently returning content: null. Also adds Docker host networking note to README. Closes #249fb5cad
-
docs: fix outdated claims in README
- httpx is required for streaming, not stdlib-only - Pro routing needs Gemini Advanced (paid), not free account - Add pip install httpx to Quick Startb866ca0
-
Merge pull request #23 from aaronjmars/security/monolithic-api-keys-auth-gate
Unverified signaturefix(security): honor api_keys auth in monolithic gemini_web2api.py75fe411 -
fix(security): honor api_keys auth in monolithic gemini_web2api.py
aeonframeworkThe README documents that setting api_keys in config.json gates /v1/* behind Bearer / x-api-key auth. The modular package (gemini_web2api/server.py) implements this via _authorized(). The monolithic script the README's Quick Start runs (`python gemini_web2api.py`) does not — DEFAULT_CONFIG omits api_keys, do_GET / do_POST never check it, so /v1/chat/completions and /v1/responses accept any request regardless of config. Combined with the default host of 0.0.0.0, anyone reachable on the operator's network can use the operator's Google account (and configured cookie) to drive Gemini, with the activity attributed to the operator's IP and Google account. Fix: - Add api_keys: [] to DEFAULT_CONFIG (defaults to no-auth, matches docs). - Add _authorized() to GeminiHandler — same logic as the modular package. - Gate /v1/* in do_GET and do_POST behind _authorized(), returning 401 with {"error": {"message": "invalid api key"}} on rejection. Behavior matches the modular package and the README'…b99e340
-
Support authenticated Gemini account routing
Unverified signatureSupport authenticated Gemini account routing25fc4ed -
Support authenticated Gemini account routing
ethansunqing04b9d27
-
unify acknowledgements and friend links format
c1c2d1f
-
Add GenericAgent credit
ee9ada5 -
docs: add limitations section, clarify no image support
- Add "Limitations" section to both README.md and README_CN.md - Clearly state: no multimodal, no real Pro, single-turn, rate limits - Created issue #12 with full technical explanation02697fb -
fix(multimodal): remove fake image support, model cannot decode base64
Testing revealed the model does NOT actually see image pixels when base64 is embedded in text. It only guesses from context/filename. Same image gives inconsistent answers; different images give same answers. This is hallucination, not real vision. Real multimodal requires ProcessFile streaming RPC (WIZ protocol) which cannot be implemented in a pure HTTP proxy. Image inputs now return a note asking user to describe in text.ad06fde -
feat(multimodal): auto-compress large images for reliable processing
- Add _compress_b64_if_needed(): resize to 256px + JPEG q60 if >50KB - Verified with real images: 210KB anime, 37KB signature, 510KB photo - All correctly identified by model after compression3b13ffe -
feat(multimodal): working image support via base64 text embedding
Images sent as image_url (base64) are embedded directly into the prompt text. Gemini's multimodal model processes the base64 data and attempts to describe the image content. This bypasses the ProcessFile streaming RPC requirement (which needs WIZ protocol) by leveraging the model's ability to parse base64 image data from text input. Limitations: - Works best with small images (<100KB) - Model accuracy may vary vs native image channel - URL-based images still need fetch + convert to base64f7f1672 -
feat(multimodal): scotty upload working, file binding WIP
Scotty resumable upload to content-push.googleapis.com works: - Step 1: POST /upload/ with X-Goog-Upload-Protocol: resumable - Step 2: POST upload_url with file data + finalize - Returns /contrib_service/ttl_1d/... file reference Blocking issue: StreamGenerate returns error 1003 when referencing uploaded files. Root cause: file must be bound to the same conversation session. Requires multi-turn conversation support (conversation_id management) to complete.c9db040 -
feat: add pro-enhanced model + extra_fields support
- New model: gemini-3.1-pro-enhanced ([31]=2 [80]=3, ~25% more output) - extra_fields in model config applied to StreamGenerate payload - Inner array expanded to 102 elements for higher field indices - Plumbed extra_fields through generate/generate_stream/server10335bd -
feat: add tool_choice / toolConfig support for all API paths
LiangLliu- OpenAI Chat & Responses: handle tool_choice parameter ("none" / "auto" / "required" / {function: {name}}) - Google Native API: handle toolConfig.functionCallingConfig.mode (NONE / AUTO / ANY) and allowedFunctionNames - tool_choice=none skips tool prompt injection and tool call parsing - tool_choice=none enables real streaming even when tools are declared - tool_choice=required adds constraint instruction to prompt8840d2c -
feat: full Google Native API support for Gemini CLI compatibility
LiangLliuAdd complete support for Google's generateContent/streamGenerateContent endpoints, enabling seamless integration with Gemini CLI and the @google/genai SDK. Key changes: 1. Real streaming (server.py) - Stream via generate_stream() with per-delta SSE chunks - Empty delta filtering (SDK rejects part.text === "") - Separate final chunk with finishReason: "STOP" + usageMetadata - Tool requests fall back to non-streaming to avoid truncated blocks 2. Function calling via prompt engineering (tools.py) - build_tool_prompt(): natural language tool instructions that avoid Gemini Web's prompt-injection detection - google_contents_to_prompt(): converts systemInstruction, tools, functionCall/functionResponse parts into prompt string + images - parse_google_function_calls(): extracts function calls from model output (3 formats: backtick blocks, bare blocks, raw JSON) 3. SDK protocol compliance - SSE format matches SDK regex /^\s*data: (.*)(?:\n\n)/ - func…3f5152e
-
feat: multimodal framework + image upload (WIP)
- Add multimodal.py: ProcessFile upload protocol implementation - Update tools.py: parse image_url from messages, return (prompt, images) - Update server.py: _upload_images() processes images before generation - Update gemini.py: file_refs parameter for StreamGenerate with images Note: ProcessFile requires cookie auth and correct proto format. Anonymous multimodal not yet working (error code 7). Text-only + streaming + tool calling all stable.510909e -
fix: code review issues (P1-P3)
- Cookie file caching with mtime check (no disk read per request) - Streaming retry logic (same as non-streaming) - Reusable httpx.Client and ssl context (no per-request allocation) - Shared _extract_texts_from_line() eliminates parsing duplication - _start_sse() helper eliminates 4x SSE header repetition - _usage() helper for token estimation - _parse_body() with proper 400 on invalid JSON - ValueError guard on @think= parameter - Single-pass regex in parse_tool_calls - Fixed __main__.py httpx detection (was always showing 'fallback') - Removed unused base64 import from gemini.pyd27caee -
feat: modularize + true streaming + multimodal support
- Split into package: gemini_web2api/{config,models,gemini,tools,server} - True SSE streaming via httpx (falls back to urllib if not installed) - Multimodal: image_url support in messages (base64 or URL) - pyproject.toml + requirements.txt for pip install - Entry: python -m gemini_web2api or gemini-web2api CLI85919ae -
merge PR #6: api key auth + docker
8937524 -
Merge remote-tracking branch 'origin/main'
HouYunFei8ae5a8e -
feat(server): 添加 API 密钥认证和 Docker 部署支持
HouYunFei +1: CodexCo-Authored-By: Codex <noreply@openai.com>f39fd46 -
Merge pull request #5 from LiangLliu/feat/google-native-api
Unverified signaturefeat: add Google native API support for Gemini CLIab00f1a -
feat: add Google native API support for Gemini CLI compatibility
LiangLliuAdd /v1beta/models endpoints (generateContent, streamGenerateContent) so that Gemini CLI can connect directly via GOOGLE_GEMINI_BASE_URL.f805ec8 -
feat: add proxy support (--proxy / config / env var)
Users behind firewall can now configure HTTP proxy via: - CLI: --proxy http://127.0.0.1:7890 - config.json: {"proxy": "http://..."} - env: HTTPS_PROXY=http://...cda0962 -
update logo: gemini sparkle + api braces
96b401b -
docs: add logo to readme
cd31d7a -
docs: add cookie guide, cross-link CN/EN readme
88cedd4 -
add logo
a9ae57d -
init: gemini-web2api v1.0.0
OpenAI-compatible API server for Google Gemini web interface. Zero auth, cross-platform, single file, no dependencies.504aef8