fix(openai): enhance API compatibility for frontend integration (Issue #113) - #117
Closed
Michael-A-Kuykendall wants to merge 2 commits into
Closed
fix(openai): enhance API compatibility for frontend integration (Issue #113)#117Michael-A-Kuykendall wants to merge 2 commits into
Michael-A-Kuykendall wants to merge 2 commits into
Conversation
…#113) - Add explicit Content-Type headers to all JSON responses (models, chat, errors) - Enhance Model structure with optional fields for frontend compatibility - Add permission, root, and parent fields to Model struct with proper serialization - Improve error responses with consistent OpenAI format and proper headers - Fix SSE streaming headers (Content-Type, Cache-Control, Connection) - Use stable timestamp (Jan 1, 2022) for model creation for consistency - Comprehensive test coverage for frontend compatibility enhancements - Resolves Issue #113: Open WebUI and AnythingLLM integration compatibility 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Michael A. Kuykendall <michaelallenkuykendall@gmail.com>
Signed-off-by: Michael A. Kuykendall <michaelallenkuykendall@gmail.com>
Michael-A-Kuykendall
force-pushed
the
fix/issue-113-openai-frontend-compatibility
branch
from
October 13, 2025 14:39
1095c76 to
9d9e447
Compare
Owner
Author
Michael-A-Kuykendall
deleted the
fix/issue-113-openai-frontend-compatibility
branch
May 26, 2026 14:52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Problem Fixed
Popular LLM frontends (Open WebUI, AnythingLLM) could not detect or properly integrate with shimmy despite CURL requests working fine. The issue was subtle compatibility gaps in response headers and model metadata format.
Technical Enhancements
🔧 Response Headers
Content-Type: application/jsonheaderstext/event-stream,no-cache,keep-aliveheaders📊 Enhanced Model Structure
permission,root,parentfor OpenAI spec compliance🚨 Improved Error Handling
📡 Streaming Compatibility
Changes Made
Core API Responses (
src/openai_compat.rs)Enhanced Model Structure
Comprehensive Error Responses
Test Coverage
test_enhanced_model_structure(): Validates optional field serializationtest_frontend_error_response_format(): Error format compatibilitytest_frontend_models_endpoint_response(): Models endpoint structuretest_open_webui_anythingllm_compatibility(): Frontend-specific testsFrontend Impact
Validation
The changes maintain 100% backward compatibility while adding the missing pieces that frontends require for proper integration. All existing functionality preserved.
🤖 Generated with Claude Code