Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Custom Claude Code models dont show in the t3 code UI

Closed Beginner friendly
#23,735 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
desktop

Research direction

The issue points to apps/desktop and describes a mismatch in the Claude Code model picker when custom models are configured. Start by tracing how the picker obtains and displays model names, then compare that with the Claude Code TUI for the same configuration. Done means T3 Code displays the configured model names; verify by reproducing with a non-Claude model such as the GLM coding plan.

Written by the indexing model from the issue text.

Description

bug needs-triage
Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/desktop

Steps to reproduce
  • Configure claude code with the GLM coding plan or likely any other models other than Claude
Image - open t3 code - open the claude code model picker in t3 code
Expected behavior

T3 code should render the same model names as the claude code TUI

Actual behavior
Image

T3 Code shows the default claude model names even if the harness is instructed to use different ones

Impact

Minor bug or occasional failure

Version or commit

0.1.2-nightly.20261022.3526

Environment

Arch Linux

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
8h 4m
Merged PRs (30d)
199

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.