[changelog] [Added] Forge LLMs (Preview) now supports Claude Opus 4.8

Open Beginner friendly
#12 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript

Research direction

Start with src/llm.ts and inspect the model map and status list. Compare them with the linked Forge supported-models documentation, confirm the model IDs for Claude Opus 4.7, Claude Sonnet 5, and Claude Opus 4.8, and reconcile the full batch. Done means the shim accepts every newly supported model without adding a behavior-change footer.

Written by the indexing model from the issue text.

Description

upstream-changelog

guid: CHANGE-3356
pubDate: Mon, 20 Jul 2026 05:49:25 GMT
category: Added (Preview)
link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3356

What's changing

Support for the Claude Opus 4.8 model is now available in Forge LLMs (Preview). See the supported models list.

Parity impact for forge-sim

This touches the @forge/llm shim. forge-sim maintains an explicit supported-models allowlist in src/llm.ts (the model map + status list, currently topping out at claude-opus-4-6). If the shim rejects a model name that real Forge now accepts, that's a parity gap (throwing where Forge succeeds).

The map is already behind on recent bumps — it lacks claude-opus-4-7 (CHANGE-3334), claude-sonnet-5 (CHANGE-3352, tracked in #9), and now claude-opus-4-8. Worth reconciling the whole batch against the live supported-models doc in one pass, and confirming the model-id string Atlassian uses (claude-opus-4-8 vs a dated variant).

Additive change (new model row), so no forge-spec behavior-change footer needed.

Dominant language
TypeScript
Stars
5
Forks
2
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 ryanackley/forge-sim

All issues in ryanackley/forge-sim

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.