github.devotd.
ReleaseEvals

langfuse/langfuse v4.66.0 — consolidating the topic display permission and two fixes

Langfuse v4.66.0 contains one feature addition that consolidates the topic display permission in a single place, plus two fixes: preventing an empty reason message from being expanded and preventing the owner role from being selected when there is no ownership permission.

Repositorylangfuse/langfuse ↗

Langfuse v4.66.0 contains one feature addition that consolidates the topic display permission in a single place, plus two fixes: preventing an empty reason message from being expanded and preventing the owner role from being selected when there is no ownership permission.

GitHub description: 🪢 Open source agent evals & observability: Trace, evaluate, and improve LLM applications with one open platform.

stars
★ 36.1K
Forks
4K
Language
TypeScript
License
NOASSERTION
Latest release
v4.66.0
Read original source ↗View on GitHub ↗

langfuse/langfuse is an open-source platform that records and evaluates the execution of LLM applications. v4.66.0 is a release published on October 20, 2026, and it contains one feature addition and two fixes. The added feature consolidates the topic display permission — that is, the permission that allows topics to be displayed — into a single place. The two fixes make an empty reason message impossible to expand and make the owner role impossible to select when there is no ownership permission.

The repository describes this project as open-source agent evals and observability. Observability means leaving a record of an application's execution flow so that problems can be traced back, while agent evals means scoring the results of AI applications against defined criteria. The repository states that records are kept as traces and that evaluation and improvement are handled in a single platform. The star count shown on GitHub is 36121. This release is not a change that adds a new observability feature, but a change that tidies up the behavior of display permissions and role selection. The topic display permission was consolidated into one place, and the two fixes each blocked a screen from opening incorrectly and a role from being selected incorrectly.

However, this release information does not specifically state which screens and roles the topic display permission applies to. No figures comparing performance or usage are given either. The repository introduces the project as open source, but this material contains no license statement. Because this release consists of one feature addition and two fixes, it is hard to conclude that the way of observing has changed itself. If your environment deals with permissions and roles, it is necessary to check the applicable scope directly in the repository's release notes.