Anthropic LLM provider fails to list models: "Cannot destructure property 'baseUrl' of 'e.body' as it is undefined"

[s31teg]

Description

Description
When selecting Anthropic as the AI provider in AI/LLM settings and clicking "Refresh Models", the request fails with a 500 error. The Model dropdown remains empty and no Anthropic models can be selected.
This occurs even with:

• A valid Anthropic API key
• The correct Base URL (https://api.anthropic.com)
• A clean Base URL with no trailing spaces

Steps to Reproduce:
Go to AI/LLM settings
Enable AI/LLM features
Select "Anthropic" as the provider
Enter a valid Anthropic API key
Set Base URL to https://api.anthropic.com (or leave as default)
Click "Refresh Models"
Error appears; Model dropdown remains empty

TriliumNext Version

0.101.3

What operating system are you using?

macOS

What is your setup?

Server access only

Operating System Version

Mac

Error logs

notes.ne16.xyz-1770369376050.log

[dosubot]

Hi @s31teg! I'm Dosu and I’m helping the Trilium team.

This is a known issue: the backend endpoint for listing Anthropic models expects a POST request with a JSON body containing baseUrl, but the frontend sends a GET request with baseUrl as a query parameter. This causes req.body to be undefined, leading to the destructuring error you see.

A quick workaround is to patch the backend code to read baseUrl from either req.body or req.query. In apps/server/src/routes/api/anthropic.ts, replace:

const { baseUrl } = req.body;

with:

const baseUrl = req.body?.baseUrl || req.query?.baseUrl;

This will let the endpoint handle both POST and GET requests, resolving the error and allowing model listing to work as expected. This approach matches how other providers (like Ollama) are handled in Trilium. For more details and discussion, see this GitHub issue.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[s31teg]

@dosu

can you fix this in the next release, since this has been noted since 13 July 2025

[dosubot]

I can't make code changes or release fixes myself, but I've confirmed this bug is still present in the current codebase and hasn't been scheduled for a fix yet. The backend expects baseUrl from req.body, but the frontend sends it as a query parameter, causing the error you see. The fix is straightforward: update the endpoint to read baseUrl from either req.body or req.query (source).

This issue has been affecting users for a while, so it's worth prioritizing for the next release. If you need an immediate workaround, patch the backend as described above.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[s31teg]

Not possible when I'm using the pre compilied version :(