Ask the project assistant and get an answer cited from the docs, and read billing for whatever date range you pick
The assistant can now read the AI control plane documentation and cite the page it drew from, so a "how do I configure this" question comes back with a link you can check rather than an answer you have to trust. On the billing page, the usage card follows whatever range you select instead of snapping back to the full cycle, and connecting an upstream MCP server can surface its published setup guide. Billing contacts also start getting a Monday email with their usage for the cycle.
Features
The project assistant reads and cites the product documentation#4786 - Two new assistant tools expose the roughly 110 AI control plane documentation pages: one returns the page index, the other returns a single page's markdown along with the public link to cite. The assistant can only read pages that are in the index, so it cites documentation rather than fetching arbitrary URLs. (Author: @simplesagar)
The billing usage card follows the range you picked#4789 - Typing a range, picking one on the calendar, or drilling into a bar now updates the usage card to that window: billed tokens for the range, overage attributed to the time it was actually incurred with the crossing day prorated, and the per-unit average over the same window. Allowance figures stay cycle-only and hide on partial ranges, and the details table uses the same attribution, so card and table always agree. (Author: @daviddanialy)
Setup guides for upstream MCP servers#4721 - Published setup documentation for an upstream MCP server can be looked up by its endpoint URL, its registry specifier, or both, with matches returned most specific first and each one reporting how it matched. Servers with no published guide return an empty list rather than an error. (Author: @walker-tx)
Weekly usage summary email for billing contacts#4646 - Every Monday, each organization's billing alert contact gets their tokens-under-management total for the active cycle with a percent-change badge against the same elapsed point in the previous cycle. The token components behind that total are defined once and shared with the billing measure, so billing and reporting move together. Organizations with no usage in either window are skipped. (Author: @daviddanialy)
Risk Events listing served from ClickHouse#4766 - The project-wide Risk Events listing reads from ClickHouse behind the risk-list-from-clickhouse flag, keeping the same ordering, filters, and pagination, and fixing a bug that skipped the first result after a page boundary. (Author: @dennnis-ez)
Business memory extraction, in internal validation#4757 - Durable knowledge is selectively extracted from completed sessions, with semantic duplicates suppressed, behind a corpus browser that offers semantic search, a jump to the cited source message, and a counted content-scope tree. The dashboard is gated to developer sessions while extraction quality is validated, so nothing is customer-visible yet. (Author: @chase-crumbaugh)
Typed feature flags in the dashboard#4649 - A reactive feature-flag hook now distinguishes loading, enabled, disabled, missing, and error states, so a gated surface can tell "still loading" from "off" instead of flickering. Project navigation is the first consumer, with its existing opt-in and opt-out behavior unchanged. (Author: @alx-xo)
Bug fixes
Saving an app verification token takes effect immediately#4778 - Domains provisioned before the OpenAI challenge feature shipped were missing the route, so the token endpoint returned a 404 until some unrelated change rebuilt the ingress. Setting or clearing the token now triggers that rebuild directly. (Author: @ThomasRooney)
Serve the 0.3.12 hooks binary#4749 - Hook installations get the latest binary, and previously pinned releases stay available for installations that haven't regenerated their bootstrap script. (Author: @gram-bot)
