Repository navigation
Conversation
Add a TOC entry, a backend table row and a setup section for Upstage Solar (OpenAI-compatible) with solar-pro4 and solar-mini4, and show how to turn reasoning on with :request-params. Signed-off-by: YoungjuKim <[email protected]>
This branch has not been deployed
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.
This adds setup instructions for Upstage's Solar models to the README: a TOC entry, a row in the backend table, and a collapsible section after Moonshot.
Upstage's API is OpenAI-compatible (
https://api.upstage.ai/v1/chat/completions), so the section only usesgptel-make-openai. The example registerssolar-pro4andsolar-mini4with:capabilities (tool-use json reasoning),:context-window 512(Upstage documents 512K) and per-million costs from the pricing page. It also notes that Solar thinks whenreasoning_effortislow…max(and not withnone/minimal), and shows:request-params '(:reasoning_effort "medium")to turn it on. The response carries the reasoning inmessage.reasoning, which gptel already reads.Why now: Upstage retires
solar-pro3,solar-pro2andsolar-minion 2026-10-30 (KST) (model history), so the example lists only the current models.Checked against the API on 2026-10-17 (
https://api.upstage.ai/v1):POST /chat/completionsstream_options.include_usagedelta.reasoningtools->tool_callsresponse_formatjson_schemastrictreasoning_effortnone/minimalreasoning_effortlow…maxmessage.reasoning+reasoning_tokensAlso checked: an assistant message that carries the previous
reasoning(as gptel sends it on tool-call turns) is accepted. Not checked: a gptel session end to end inside Emacs.Disclosure: I work at Upstage.
AI assistance: drafted with an AI coding assistant (Claude); I reviewed the changes and ran the checks listed above.
🤖 Generated with Claude Code