Is GPT-5.6 Luna a fast alias for Sol?
No. Luna, Terra, and Sol are different capability tiers in the same GPT-5.6 generation: Luna focuses on speed and cost efficiency, Terra focuses on balance, and Sol focuses on flagship capabilities. Use gpt-5.6-luna when calling it; you cannot turn it into Sol merely by changing the prompt, nor should you expect all three to perform the same on difficult tasks.
What programming tasks is Luna suitable for?
It is suitable for local code explanations, error analysis, change reviews, test drafts, and routine implementation suggestions. It is best to provide the relevant code, runtime behavior, and acceptance criteria so that the results can be verified. For cross-file dependencies, complex architectures, or repeated tool coordination, compare Terra and Sol, and make your choice based on whether actual tests pass.
How can I have Luna analyze screenshots?
In the message content for Chat Completions, include both a text question and image_url image content, and clearly specify the area to analyze and the desired output format. For example, ask it to list interface issues, explain chart trends, or organize information from a screenshot. Images should be clear and readable; small text and dense areas can be cropped before submission to reduce unnecessary visual distraction.
Which API should I choose when integrating Luna?
Use Chat Completions or Responses and provide the full model ID. Chat Completions uses messages and choices, while Responses uses input and its corresponding response structure; handle history management, streaming events, and tool parameters separately according to the selected API, and do not mix the two formats.
Can Luna directly deliver usable JSON?
You can ask Luna to generate JSON with specified fields for information extraction, classification, and ticket organization. The standard chat endpoint defines JSON object and JSON Schema format control fields; when using these controls, rely on the configuration actually accepted by gpt-5.6-luna. The prompt should clearly specify field meanings, handling of missing values, and permitted labels. After receiving results, the application still needs to parse the JSON, validate the structure and business rules, and handle refusals or truncated output; correct formatting does not mean the content is accurate, nor does it mean related actions have already been performed.