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

Support gpt-6.1-terra as a Copilot model

Open Beginner friendly
  • Is something wrong?
#10,778 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
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github, typescript
Domain
backend, databases

Research direction

Read src/copilot-model.ts and shared/model-information/sources/lifecycle-compatibility.json to see how supported Copilot models are defined, then inspect containers/api-proxy/ai-credits-pricing.js for the pricing format. Add gpt-6.1-terra as a supported model with the stated rates and run copilot-model-catalog-sync.test.ts; done means the model is accepted and that test passes.

Written by the indexing model from the issue text.

Description

Problem

GitHub Copilot now lists GPT-6.1 Terra in the model picker. AWF rejects it before any container starts.

gh-aw already carries pricing for it in v1.0.1 (pkg/cli/data/models.json, github-copilot and openai).

Cause

src/copilot-model.ts builds SUPPORTED_COPILOT_MODELS from shared/model-information/sources/lifecycle-compatibility.json. That file lists gpt-6-astra, gpt-6-luna, gpt-6-sol and gpt-6.1-sol, but not gpt-6.1-terra. Setting COPILOT_MODEL=gpt-6.1-terra fails with model 'gpt-6.1-terra' is unsupported or unrecognized by this AWF version.

containers/api-proxy/ai-credits-pricing.js and containers/api-proxy/models.dev.catalog.json also have no entry for it.

Request

  • Add gpt-6.1-terra to lifecycle-compatibility.json (supported).
  • Add its pricing to ai-credits-pricing.js. gh-aw uses input $1, output $5, cached input $0.05, cache write $1.25 per 1M tokens.
  • Keep copilot-model-catalog-sync.test.ts passing.

Checked against

github/gh-aw-firewall main. I read the source and did not run AWF.

Dominant language
TypeScript
Stars
157
Forks
80
Avg merge
3h 45m
Merged PRs (30d)
422

Getting set up

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 github/gh-aw-firewall

All issues in github/gh-aw-firewall

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.