rowboatlabs / rowboatlabs/rowboat

when using groq as a custom key, the gptoss frequently gets this eror:

Open
#463 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
17.6k
Forks
1.7k
Avg merge
11h 37m
Merged PRs (30d)
173

Description

when using groq as a custom key, the gptoss frequently gets this eror: AI_APICallError responseBody: {"error":{"message":"'messages.2' : for 'role:assistant' the following must be satisfied[('messages.2' : property 'reasoning_content' is unsupported)]","type":"invalid_request_error"}}. add a option in api settings page to include or exclude reasoning content.also, add ability to add multiple models and switch betw them. that will be convenient

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the Groq custom-key request with a gptoss model and inspect the API settings page and model-selection entry points. Done means users can include or exclude reasoning content and configure multiple models that they can switch between without triggering the reported request error.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ai, api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.