Bring your traces in from Vercel and Better Stack
New · Trace sources · by Chamath & TomaGetting your traces into Glassray used to mean Langfuse, LangSmith, or PostHog. Now a Vercel-deployed app connects with a Trace Drain: copy three values into the Vercel dashboard, no code changes, and your AI traces start flowing. A multi-step trace that arrives in pieces still shows up as one clean trace. Better Stack joins too, so if your traces already live there you can pull them in directly instead of re-wiring your collectors.Filter your traces by any attribute you send
New · Traces · by ManuelYou could filter by the built-in fields, but not by the custom metadata your own app attaches. Now you can slice the trace stream by any custom attribute a trace carries, like merchantId, branch, or commit, and a new key works the moment it first appears, no setup. Operators cover the practical set: is, is not, contains, exists, regex matches, and numeric comparisons. If you use the tracing SDK, you can attach those attributes straight frommeta or the constructor.Also shipped this week
- Exact LLM cost on every trace: send your real cost with a trace, or let Glassray read it from a gateway that returns one (for example OpenRouter), instead of a tokens-times-price estimate.
- Concrete fix suggestions: a prompt or config fix now arrives as a before-and-after edit, with rules cited by name and example traces attached, not a “go explore your codebase” instruction.
- Edit deviations from chat: ask Glassray, in the dashboard or Slack, to relabel a deviation, rewrite its description, or correct its Expected rule and Observed summary; rewriting the Observed summary shows a before and after and asks first.
- Calibrated severity: deviations are rated by real impact and confidence instead of defaulting to critical, and correct background knowledge is no longer flagged as fabricated.
- Choose your default project: reassign which project is your org’s default, and delete the starter workspace once you have moved past it.
- Severity-first inbox: the deviations inbox now sorts by severity by default, so critical issues sit on top.
- Counts that add up: deviation totals now match the visible breakdown, and matches found automatically in the background now show up instead of staying hidden.
- Labels on deviation cards: read a deviation’s labels at a glance instead of only filtering by them.
- Webhook delivery detail: each delivery shows its duration, target URL, and raw response, so you can debug a failure without leaving Glassray.
- Sign-in fixes: passkeys are now a sign-in option, and email-verification and invitation links sign you in instead of erroring.
- Sturdier rule links: deviations stay attached to their rule even when a code re-read rewords it.
- Fresher answers in Ask: flows are re-checked live instead of quoted from stale data earlier in the conversation.
- Guided flow re-map: tell Glassray in plain language how to re-map a single flow and it re-reads that flow’s code and refreshes it in place, keeping its history.
- Fuller span detail: retriever, workflow, and agent spans now show their inputs and outputs directly, including on traces you already sent.
- Project-aware answers: Ask Glassray and the Slack agent know which project you are in, so answers stay scoped to it.
- Editable default rule: change the confirmation rule that applies to traces matching no flow.
- Delete a project with sources attached: no need to detach its trace sources first.
- Safer source disconnect: removing a trace source warns you first and keeps the traces it already pulled.
- Collapsible trace groups on a flow’s Traces tab, to keep long lists manageable.
- Smoother onboarding: “Invite your team” moved to the end and is optional, and invited users land in the right workspace.
- CLI setup lands you in the project you picked, and every yes/no prompt now behaves consistently.
- Smaller touches: a Switch button and cleaner cards on the projects page, loading skeletons on settings tabs, clearer explainer text on the rules screen, a health tooltip on a flow’s details panel, long flow names truncate with a tooltip, deviation graphs no longer break on unusual characters, Slack disconnect fully detaches the agent, and a custom date range with a bigger export on the developer page.
Keep prod, staging, and demo completely separate
New · Projects · by ManuelYour org now splits into projects (prod, staging, demo, local), and each one keeps its own sources, traces, flows, and deviations. A noisy staging run can never confirm or pollute a production issue again. Projects are fully independent: each one can connect its own repo and its own trace sources. And when you do want to share, you can copy a flow from one project into another, so a workflow you have already mapped carries over instead of starting from scratch.Fixes are now verified against real traces, not an AI’s word
Improved · Fix watcher · by ManuelWhen Glassray spots a commit that looks like it fixes a deviation, it no longer just trusts the judgment. It re-checks reality: after the change ships, we scan the traces that came in since it landed. One recurrence and the fix is refuted; zero and it’s closed, with the trace evidence attached. You can now ask “is this still happening since Sunday’s fix?” in a single call.Also shipped this week
- Flow health now reflects Confirmed deviations only, so suspected candidates no longer drag the number down.
- Confirmation rules: Org Admins can now set custom rules for when a deviation moves from suspected to confirmed, including asking a specific person to review it first.
- Slack notifications: choose between a message for each new deviation or a single daily digest.