Hmbown/DeepSeek-TUI

Configurable path suffix for OpenAI-compat endpoints (closes #1874)

Open

#2,089 opened on May 25, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (29,199 stars) (2,435 forks)batch import
autonomous-readydocumentationenhancementgood first issuerust

Description

Shape. Some third-party endpoints reject /v1/chat/completions and accept only /chat/completions. Add path_suffix: Option<String> to ProviderConfigToml. Default is current behavior. Closes #1874.

Existing issues this resolves on PR merge

Closes:

  • Closes #1874

When opening a PR for this issue, the PR body must include the Closes #N lines for every issue above that this PR fully resolves, so they auto-close on merge.

Slate item 16/18. Tracking doc: .private/issue-slate.md (maintainer-only).

Contributor guide

Tech stack
rust
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
RustOpenAI API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Examine the ProviderConfigToml struct in the codebase to add the optional path suffix field. Look at how the default path is constructed for OpenAI compatible endpoints and modify the endpoint URL building logic to append the suffix when provided. Ensure backward compatibility by defaulting to the current behavior.
Configurable path suffix for OpenAI-compat endpoints (closes #1874) · Hmbown/DeepSeek-TUI#2089 | Good First Issue