ForgeLlmAPIError: Forge LLMs model not allowed Error in LLM Chat

Forge
1

Hi there,

I tried forge llm and keep getting this error, and can’t figure out what the issue is.

Currently I am on this version:

"@forge/llm": "^1.0.2",

The Error:

ERROR   21:45:51.938  e169d1ec-eecd-4715-9d19-4dc6d3ea197b  ForgeLlmAPIError: Forge LLMs model not allowed: anthropic.claude-sonnet-5
    at checkResponseError (webpack://jira-issue-panel-ui-kit/node_modules/@forge/llm/out/utils/error-handling.js:30:1)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async LlmApiImpl.chat (webpack://jira-issue-panel-ui-kit/node_modules/@forge/llm/out/llm-api.js:25:1)
    at async generateIssueDescription (webpack://jira-issue-panel-ui-kit/src/resolvers/generation.js:247:1)
    at async Object.handler (webpack://jira-issue-panel-ui-kit/node_modules/@forge/resolver/out/index.js:33:1)
..) {
  code: 'FORGE_LLMS_MODEL_FORBIDDEN',
  status: 403,
  statusText: 'Forbidden',
  traceId: 'c2c833acc84942d9857c97609f18245b'
}

The basic request:

import { chat } from '@forge/llm'

...

const llmPrompt = {
  model: 'claude-sonnet-5',
  messages: [
    { role: 'system', content: systemPrompt },
    { role: 'user', content: userPrompt }
  ]
};

const finalResponse = await chat(llmPrompt);
const content = finalResponse.choices[0].message.content;
....

And declared in my manifest as:

llm:
    - key: main-llm
      model:
        - claude
2

hello,

This shouldn’t be the case if your app manifest has Family defined. Just wanted to ensure that your app was deployed with the LLM module in the manifest(with family) before you performed these invocations. I can see this failed invocation was from a tunnel, and you did a bunch of deployments after these failed invocations yesterday. Can you give it another try to see if that works?

3

Hi there,

thank you for your help. Now it worked. Somehow I had to go and update the version from within my administration account. In the past it just updated by hitting forge deploy. Maybe something went wrong with my configuration.

However, after I triggered the update it worked. :star_struck:

Best,
Chris