What langwatch/langwatch shipped
Written by FoxPlug from the repository's own releases; not affiliated with Langwatch. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/langwatch/langwatch; Langwatch did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 2, 2026
What shipped
- A removed member's seat is now held for 30 days, and Stripe lowers the seat count from the next cycle. Pull request #9404
- Organizations over their seat limit now hold back SSO sign-ins, admins can see who is waiting, and a Billing role was added. Pull request #9391
- The Usage page was redesigned with a plan strip, a month-by-day view, a per-project split and seats. Pull request #9406
- Any API key in Settings can be reopened to show its details, and each key has a Rotate action for its secret. Pull request #9359
- Every organization member, not only admins, can now start a paid subscription. Pull request #9370
- Self-hosted licence renewal, replace, environment licence and offline cases were fixed. Pull request #9402
- The self-hosted licence path was cleared from lock to activation, and failed instant evals no longer stay stuck. Pull request #9415
- Version 3.23.0 shipped with agent and evaluator versioning with deploy labels, plus experiment and dependency fixes. Release
- Default models gained a Judge column and row that picks the model scenario runs use to judge a scenario. Pull request #9358
- Dashboard widgets now say when they fail and no longer show old rows under a new period. Pull request #9362
Why it matters
This week's changes fix real dead ends for people running self-hosted installs, from licence renewal to SSO sign-in behind a proxy to seat limits. Billing and seats also got a lot of work: any member can start a subscription, seat counts follow what is in use, and the Usage page now shows how the month built up. Alongside that, API keys can be reopened and rotated, and version 3.23.0 brought agent and evaluator versioning with deploy labels.
Changelog entry
- Hold a removed member's seat for 30 days; Stripe lowers seats from the next cycle. Pull request #9404
- Seat requests over the limit, identity provider refusal screens and a Billing role. Pull request #9391
- Redesign the Usage page with the plan strip and the month by day and by project. Pull request #9406
- Reopen an API key's details and rotate its secret. Pull request #9359
- Let every organization member start a paid subscription. Pull request #9370
- Self-hosted licence renewal, replace, environment licence and offline fixes. Pull request #9402
- Clear the self-hosted licence path from lock to activation and fix failed instant evals. Pull request #9415
- Add a Judge column to default models for scenario judging. Pull request #9358
- Say when a dashboard widget fails and never show old rows under a new period. Pull request #9362
- Release 3.23.0 with agent and evaluator versioning with deploy labels. Release
- Say what a non-array value is when the CLI --jq iterates or indexes it. Pull request #9410
- Send SSO issuer discovery and the domain proof file through the outbound proxy. Pull request #8942
This week: seats are held 30 days after a member is removed, over-limit organizations hold back SSO sign-ins, the Usage page was redesigned, any member can start a paid subscription, and API keys can be reopened and rotated. Version 3.23.0 also shipped agent and evaluator version
Several fixes landed this week for self-hosted installs, including licence renewal and replace, activation, and SSO sign-in behind a proxy. Seats changed too: removing a member holds their seat for 30 days and Stripe lowers the count from the next cycle, organizations over their seat limit now hold back SSO sign-ins, and any member can start a paid subscription. The Usage page was redesigned with a plan strip, a month-by-day view and a per-project split. API keys can be reopened and rotated. Version 3.23.0 shipped agent and evaluator versioning with deploy labels, plus experiment and dependency fixes.
Week of October 26, 2026
What shipped
- Mcp-server 3.0.0 shipped, with dashboards now addressing the new Dashboards API and the reports tools renamed platform analytics reports. Release
- Typescript-sdk 2.1.0 shipped with a per-widget Langy traces setting in the query editor, widget queries taking sources and projects as params, and a per-run concurrency option on the experiment run API. Release
- System messages sent mid-conversation are now kept in place on the Bedrock lane, which addresses a case where a trailing system message broke the cache and cost full input price. Pull request #9219
- Dashboard widget queries now take sources and projects as parameters. Pull request #9171
- The scope filter dropdown now lets you search and jump to any other project you can see. Pull request #9116
- A sign-in refused by an identity provider now shows the person a clear message instead of an unexplained failure. Pull request #9180
- A span's own user-prefixed attributes no longer cause a 500 when a trace is opened. Pull request #9179
- The group queue worker that hands a job back now passes its group over, fixing an intermittent scheduling race. Pull request #9154
- A dead worker's groups are now reclaimed when its liveness beacon lapses rather than when its active key expires, cutting the wait for queued jobs. Pull request #9139
Why it matters
This week two client packages moved to new major and minor versions, so dashboard and reports code written against the old API needs updating. Alongside that, the gateway gained a route for a budgets-and-tracing-wrapped API, and a set of fixes landed for trace reads, queue scheduling, SSO sign-in messages and Bedrock caching.
Changelog entry
- Mcp-server 3.0.0: dashboards address the new Dashboards API; reports move to analytics reports and the reports tools are renamed. Release
- Typescript-sdk 2.1.0: per-widget Langy traces setting, widget queries take sources and projects, per-run concurrency on the experiment run API. Release
- Per-span PII redaction budget raised to 400,000 characters, reducing spans stored unscanned. Pull request #9209
- Mid-conversation system messages kept in place on the Bedrock lane. Pull request #9219
- Langy shows a gateway spending limit as a budget card instead of a failed reply. Pull request #9197
- Span attributes named user.* no longer break a trace read. Pull request #9179
- SSO sign-in refused by an identity provider now shows a clear message. Pull request #9180
- Scope filter can search and jump to any project you can see. Pull request #9116
- Open drawers sit to the left of the expanded Langy panel instead of under it. Pull request #9159
- Group queue worker passes its group over when handing a job back. Pull request #9154
- Dead worker's groups reclaimed when its beacon lapses, not its active key. Pull request #9139
Week of October 19, 2026
What shipped
- Monitors now pause themselves when most of their evaluations fail, so a hanging endpoint stops burning evaluation spend. Pull request #9040
- Evaluation calls that time out are no longer retried. Pull request #9037
- Doubleword is now a built-in model provider, added with an API key and called as doubleword/ model. Pull request #8557
- Each API request records which kind of credential it used, and legacy project keys are now limited to ingestion. Pull request #8962
- Client address headers are read only from configured proxies, instead of trusting any private-looking peer. Pull request #8970
- The NLP Lambda clients and per-organisation S3 accounts accept web-identity credentials as an alternative to static AWS keys. Pull request #8994
- The per-request access log now records the client IP and the acting principal. Pull request #8963
- A new command runs only the tests an edit reaches, across package boundaries. Pull request #8945
- Settings gains an Instant Evals column for picking the decision model, including your own key. Pull request #8935
- One nightly suite runs at 01:00 UTC and puts every result on a single pinned dashboard issue. Pull request #8877
Why it matters
This week closes several reliability and security gaps that showed up in real deployments: failing monitors and timed-out evaluations no longer run unchecked, forwarded headers are only trusted from known proxies, and API requests now record their credential type and client. Self-hosted and cloud setups also gain more deployment options through web-identity credentials, a new model provider and a nightly suite that reports in one place.
Changelog entry
- Monitors pause when most of their evaluations fail. Pull request #9040
- Timed-out evaluation calls are no longer retried. Pull request #9037
- Doubleword added as a built-in model provider. Pull request #8557
- API requests record their credential type; legacy project keys become ingestion-only. Pull request #8962
- Client address headers are read only from configured proxies. Pull request #8970
- Web-identity credentials accepted for NLP Lambda and per-organisation S3 clients. Pull request #8994
- Access logs include client IP and acting principal. Pull request #8963
- A command runs only the tests an edit reaches. Pull request #8945
- Instant Evals decision model column in Default models settings. Pull request #8935
- One nightly suite with a single pinned dashboard issue. Pull request #8877
- Self-hosted installs receive release and security notices from Cloud. Pull request #8949
- Operators can force a password reset for a set of users. Pull request #8959
This week: monitors pause themselves when evaluations mostly fail, timed-out evaluation calls are no longer retried, API logs record credential type and client IP, Doubleword is a built-in provider, and a single nightly suite reports on one dashboard.
This week's changes: online evaluation monitors now pause themselves when most evaluations fail, so a hanging endpoint stops spending on failed runs. Timed-out evaluation calls are no longer retried. Each API request records which credential type and client it used, and legacy project keys are limited to ingestion. Client address headers are read only from configured proxies. The NLP Lambda clients and per-organisation S3 accounts accept web-identity credentials instead of static AWS keys. Doubleword is now a built-in model provider, Settings has an Instant Evals column for choosing the decision model, and the new nightly suite puts every result on one pinned dashboard issue.
Week of October 12, 2026
What shipped
- Vertex AI calls send the stored service account again, so Vertex AI judges run instead of failing before reaching Google. Pull request #8784
- Code evaluators run on the project's engine again in the workbench, experiments, online evaluations and the REST evaluate door. Pull request #8716
- Hosted MCP keeps sessions across deploys and retires the SSE transport, so clients are not logged out or given method not allowed. Pull request #8718
- A repeated refresh within 60 seconds returns the token pair already minted instead of invalid grant, so users stay signed in. Pull request #8719
- LWQL engine tables and views stay on a failed converge and are reconverged by a 5-minute check instead of returning 503. Pull request #8727
- Platform metrics are recorded through the OTel facade so the OTLP push carries them, restoring group queue and other series. Pull request #8759
- The listed consumer stops re-reading parked and blocked groups every 50ms, easing Redis processor load in production. Pull request #8750
- Serialised LangChain messages in span inputs and outputs render as chat messages instead of raw JSON in the trace drawer. Pull request #8747
Changelog entry
- Vertex AI calls send the stored service account again so Vertex AI judges run. Pull request #8784
- Code evaluators run on the project's engine in the workbench, experiments and online evaluations. Pull request #8716
- Hosted MCP keeps sessions across deploys and no longer serves the SSE transport. Pull request #8718
- A repeated refresh within 60 seconds returns the token pair already minted. Pull request #8719
- LWQL engine tables and views reconverge on a 5-minute check after a failed deploy. Pull request #8727
- Platform metrics are recorded through the OTel facade so the OTLP push carries them. Pull request #8759
- The listed consumer stops re-reading parked and blocked groups every 50ms. Pull request #8750
- Serialised LangChain messages render as chat messages in the trace drawer. Pull request #8747
- Discard and redrive in the dead letter queue handle more than 2,000 groups at once. Pull request #8751
- Agent testing drawer close and width, dataset upload completion and trace search scoping are fixed. Pull request #8755
Week of October 5, 2026
What shipped
- Instant Evals are now a model choice on every LLM-as-a-judge evaluator, covering boolean, score and category judges. Pull request #8467
- Analytics dashboard panels stay under the ClickHouse memory limit and show a compact panel error instead of failing with a large query error. Pull request #8525
- The gateway added voice support for consumer apps, covering streaming audio, provider tokens, a live broker and realtime metering against per-user and project budgets. Pull request #8450
- Governance added an aggregate project that owns no traces and reads its member projects through shared grants. Pull request #8487
- Governance anomaly alerts now deliver to registered webhook endpoints, with migrated endpoints keeping the raw body and sha256 signing. Pull request #8530
- OTLP bodies are decoded by magic bytes, so zstd and gzip payloads arrive correctly even under a wrong Content-Encoding header. Pull request #8501
- Self-hosting can rotate CREDENTIALS_SECRET, scrape worker metrics, and drop two unused chart settings. Pull request #8472
- Trace list page size is capped at 1000, so a page size of 10000 is now a validation error. Pull request #8484
- Experiment results from a run still being stored now say so, and store faster. Pull request #8492
- A public coding agent cost skill reads coding sessions and recommends settings that cut cost and context. Pull request #8550
Why it matters
This week tightens the platform people already run: analytics dashboards hold up under high-volume projects, traces and experiments give clearer results, and self-hosted installs gained secret rotation and safer upgrades. Governance, voice in the gateway, and the new judge model open up new ways to read every trace and to serve consumer voice apps. Several fixes came straight from real installations and customer reports.
Changelog entry
- Instant Evals are now a model choice on every LLM-as-a-judge evaluator: boolean, score and category. Pull request #8467
- Analytics dashboards stay under the ClickHouse memory limit and show a compact panel error. Pull request #8525
- ClickHouse memory errors are translated on the strict layout, and the documents refetch loop is stopped. Pull request #8539
- ClickHouse memory limit fix and compact panel error are ported to the strict layout. Pull request #8536
- Gateway voice support for consumer apps: streaming audio, provider tokens, live broker and realtime metering. Pull request #8450
- An aggregate governance project owns no traces and reads member projects through shared grants. Pull request #8487
- Governance anomaly alerts deliver to webhook endpoints with raw body and sha256 signing. Pull request #8530
- OTLP bodies are decoded by magic bytes, including zstd and gzip under a wrong Content-Encoding header. Pull request #8501
- Unparseable OTLP bodies are logged as client warnings on the traces, logs and metrics routes. Pull request #8489
- Self-hosting can rotate CREDENTIALS_SECRET and scrape worker metrics; two unused chart settings are dropped. Pull request #8472
- Trace list page size is capped at 1000. Pull request #8484
- Experiment results from a run still being stored say so, and store faster. Pull request #8492
This week: Instant Evals as the model for every LLM judge, analytics panels that stay under the memory limit, voice support in the gateway, an aggregate governance project, OTLP bodies decoded by magic bytes, and CREDENTIALS_SECRET rotation for self-hosted installs.
This week's work on LangWatch covers several areas people asked about. Instant Evals are now a model choice on every LLM-as-a-judge evaluator. Analytics dashboards stay under the ClickHouse memory limit and show a compact panel error rather than failing. The gateway gained voice support for consumer apps, with streaming audio, provider tokens, a live broker and realtime metering. Governance added an aggregate project that reads member projects through shared grants, and anomaly alerts now deliver to webhook endpoints with raw body and sha256 signing. OTLP bodies are decoded by magic bytes, so zstd and gzip payloads arrive correctly. Self-hosted installs can rotate CREDENTIALS_SECRET, scrape worker metrics, and drop two unused chart settings.
Week of September 28, 2026
What shipped
- LangWatch 3.20.1 released with SSO and self-hosting fixes. Release
- LangWatch 3.20.0 released with third-party calls off by default and managed models only for self-hosted installs. Release
- Self-sign-up can now be restricted on self-hosted email auth installs via environment variable or Helm value. Pull request #8441
- Developer seat added: a member who owns a personal project and nothing shared, for enterprises at Full seat cap. Pull request #8373
- Langy's browser notifications now use Web Push from the server so they arrive with the tab closed or browser restarted. Pull request #8420
- OpenAPI document is now generated from route declarations at boot instead of committed to the repository. Pull request #8419
- Organization keys can now list all virtual keys across projects without sending X-Project-Id. Pull request #8449
- Campaign conversion events track email click through sign up and paid subscription. Pull request #8445
- Traces now display costs below a tenth of a cent instead of rounding to $0.0000. Pull request #8434
- Instant Evals require opt-in by organizations before sending trace data to outside judges. Pull request #8348
Why it matters
Two releases shipped this week addressing self-hosted security, SSO, and seat licensing. The strict layout branch landed several features including developer seats and improved notifications. Multiple hardening fixes for code isolation, authentication, and data privacy ensure self-hosted installs are more secure by default.
Changelog entry
- Self-hosted SSO with one connection routes sign-in straight to that provider. Pull request #8411
- Self-hosted email auth can restrict sign-up via SIGN_UP_MODE environment variable. Pull request #8441
- Developer seat: member who owns personal project, not counted against Full seat cap. Pull request #8373
- Langy sends browser notifications via Web Push from server. Pull request #8420
- Instant Evals require organization opt-in before use. Pull request #8348
- Traces display costs below $0.00005 with correct decimals. Pull request #8434
- Campaign conversion events track sign-in, sign-up, and paid subscription. Pull request #8445
- Organization keys list all virtual keys without per-project credential. Pull request #8449
- OpenAPI document generated at boot from routes, not committed. Pull request #8419
- Project credentials stay with project admins in cost rollup. Pull request #8421
- Code-block runner hardened: rebuilt per execution, endpoint auth checked. Pull request #8424
- Annotation commands serialize per trace and return 404 on unknown delete. Pull request #8400
3.20.1 and 3.20.0 shipped: stricter self-hosted defaults, SSO fixes, developer seats for enterprise teams, and improved notifications. Traces now display sub-penny costs correctly.
LangWatch 3.20.0 and 3.20.1 are out. Self-hosted installs now disable third-party calls by default and restrict self-sign-up via environment variable. A new developer seat lets enterprises add members to personal projects without consuming Full seats. Langy's notifications use Web Push. Instant Evals require opt-in before sending data outside. Traces display costs below a tenth of a cent.
Week of September 21, 2026
What shipped
- LangWatch 3.18.0 ships with a Helm chart for self-hosted deployments. Release
- The CLI now runs from a committed launcher instead of a bundled hook, and agent testing can compare agents in one run. Release
- A new integration guide for LiteLLM Proxy lets teams trace every call through their internal LLM gateway without touching application code. Pull request #8309
- Datasets can now hold uploaded images and files in cells, and those attachments reach models and agents mapped to those columns. Pull request #7964
- Connected self-hosted installs can now call LangWatch-hosted services with usage metered and capped against the license. Pull request #8232
- Fixes for upgrading a self-hosted 3.16 Helm install to 3.18 on EKS were validated on a real customer deployment. Pull request #8323
- A new docs page guides administrators through moving to their own identity provider with self-serve updates. Pull request #8271
- When Instant Evals are disabled, the UI now prompts to enable them instead of showing a model popover. Pull request #8295
- A search now correctly judges sentences classified as judgements, and Test Connection sends real calls. Pull request #8268
- Every tenant-scoped Postgres model is now automatically derived into the LangWatchQL catalog, matching the ClickHouse approach. Pull request #8209
Why it matters
3.18.0 brings self-hosted deployments to Kubernetes with a Helm chart, adds support for images and files in datasets, and enables self-hosted instances to use LangWatch-hosted services with metered usage. Teams using LiteLLM as their gateway can now trace all calls without code changes. These updates address deployment, extensibility, and integration gaps.
Changelog entry
- Helm chart for LangWatch application deployed to Kubernetes Release
- CLI runs from a committed launcher instead of bundled hook Release
- Agent testing can compare agents in one run Release
- LiteLLM Proxy integration guide for tracing without application code changes Pull request #8309
- Datasets support uploading and storing images and files in cells Pull request #7964
- Uploaded attachments are delivered to prompts and agents mapped to columns Pull request #7964
- Connected self-hosted deploys can call LangWatch-hosted services with metered usage Pull request #8232
- Self-serve update guide for moving to your own identity provider Pull request #8271
- Instant Evals prompt displays when flag is off instead of model popover Pull request #8295
- Fixes validated for upgrading self-hosted 3.16 Helm installs to 3.18 on EKS Pull request #8323
LangWatch 3.18.0: Helm chart for self-hosted K8s, images and files in datasets, LiteLLM Proxy integration, connected self-hosted with metered hosted services.
LangWatch 3.18.0 is out. New Helm chart for self-hosted Kubernetes deployments. Datasets now support images and files. LiteLLM Proxy integration lets teams trace calls through their internal gateway without code changes. Connected self-hosted installs can use LangWatch-hosted services with metered usage against the license.
Week of September 14, 2026
What shipped
- Instant Eval runs execute a LangWatchQL statement as a judgment job with progress tracking and persisted results, enabling bulk evaluation workflows beyond the exploratory inline query cap. Pull request #8208
- The Instant Eval CLI waits for answers, accepts target shorthand syntax, and estimates spend before running, making evaluation accessible without writing LangWatchQL by hand. Pull request #8216
- Instant Eval judgments meter on the gateway spend spine as Stripe charges with a 1 USD free budget, moving billing onto the standard cost tracking system. Pull request #8220
- LangWatchQL gains eval functions that call the classifier interface, letting judgment calls sit inline in analytics queries alongside metrics and dimensions. Pull request #8201
- Any LangWatch API key now has one query door into LangWatchQL via POST /api/v1/query, running read-only SELECT statements across all projects the key can read with ClickHouse row policies enforcing scope. Pull request #8113
- Custom dashboard charts now run in their own sandboxed frame on a separate route, allowing widgets to import any module under the production Content-Security-Policy. Pull request #8151
- Sign-in now offers one-click social authentication through Google, GitHub, and Microsoft buttons alongside Auth0, removing the double-SSO-click from production. Pull request #8143
- Trace reading logic (conversation threading, LLM span splitting, digest generation) moved from React components into reusable extraction modules for use across the platform. Pull request #8194
- Ingestion pull outcome writes now carry typed dispatches instead of casts, improving bookkeeping accuracy for customer assignment and timestamps. Pull request #8111
- Cost rollup checks moved from a nightly cron to an event-driven per-tenant process that triggers only when cost changes land, replacing batch checking with reactive updates. Pull request #8121
Why it matters
Instant Evals shipped as a complete feature this week: runs, CLI, judgment functions, billing, and metrics. LangWatchQL now has a unified query door that any API key can use. These changes let users evaluate bulk text through the platform and access analytics programmatically without building custom integration.
Changelog entry
- Feat(instant-evals): the Instant Eval run, a judgment job over an LWQL statement with progress and persisted judgments Pull request #8208
- Feat(instant-evals): the CLI that waits for the answer, the target shorthand and estimate before spend Pull request #8216
- Feat(instant-evals): meter judgements on the gateway spend spine, a Stripe meter and a 1 USD free budget Pull request #8220
- Feat(lwql): eval functions judged by the classifier interface (Instant Evals) Pull request #8201
- Feat(query): self-describing LangWatchQL door + whoami --json Pull request #8113
- Feat(analytics): serve chart sandbox frame on its own route so widgets can import any module Pull request #8151
- Feat(identity): one-click social sign-in — the Auth0 connection bridge, native-provider groundwork, and AUTH_PROVIDER Pull request #8143
- Refactor(traces): framework-free conversation, chat split, LLM span and bounded digest modules Pull request #8194
- Feat(governance): replace the cost-rollup comparator cron with an event-driven per-tenant costRollupWatch process manager Pull request #8121
- Fix(instant-evals): review sweep over the ten Instant Evals PRs Pull request #8230
- Fix(instant-evals): end-to-end dogfood on main, five fixes in how numbers and words reach the caller Pull request #8233
- Fix(clickhouse): renumber the coding-agent usage migration to 00099, 00097 was taken Pull request #8235
Instant Evals are live: run bulk judgments through LangWatchQL, use the CLI without writing queries, and only pay for what you evaluate. One query door for any API key. Dashboard charts now run in sandboxed frames.
Instant Evals shipped this week with three layers: LangWatchQL now has eval() functions for inline judgments, runs execute bulk evaluation jobs with progress tracking, and the CLI makes it accessible without SQL. Billing integrates with Stripe on the standard cost spine. Separately, any LangWatch API key now has one query door into LangWatchQL—POST /api/v1/query runs read-only SELECT across all readable projects. Custom dashboard charts moved to sandboxed frames. Sign-in gained one-click social auth.