Track what’s new across the Qredence product suite. For documentation changes, see the docs repository.Documentation Index
Fetch the complete documentation index at: https://docs.qredence.ai/llms.txt
Use this file to discover all available pages before exploring further.
Week of May 20
Updates
Fleet-RLM — decoupled WebSocket streaming runtime Turn execution no longer runs inline with the WebSocket handler. Each user message is processed in a background task that builds its own agent context and publishes execution events through a shared event emitter. The same emitter fans out frames to every subscriber on/api/v1/ws/execution and /api/v1/ws/execution/events, so a dropped or reconnected client no longer cancels the turn. No client changes are required — frame shapes are unchanged. See Observability and HTTP and WebSocket API.Fleet-RLM — Entra JWKS cache and joserfc token validation
AUTH_MODE=entra now uses joserfc instead of PyJWT for token verification and ships with a built-in JWKS cache (5-minute TTL) that falls back to the last-known keyset if Entra’s JWKS endpoint is unreachable. Bearer-token validation, tid/aud/iss enforcement, and tenant admission behavior are unchanged. See Deployment.Bug fixes
- Final assistant text no longer duplicated in replay. The terminal trajectory step now omits the planner’s intermediate thought, so reopening a session replays the assistant’s final response once instead of twice. (Sessions and persistence)
- Frontend WebSocket parser prefers
step.outputfor final frames. Execution-step envelopes withkind: "final"now surface the actual response text instead of the internal label.
Week of May 12 – May 19
New features
Fleet-RLM 0.5.3 — backend-driven runtime settings The Settings page now renders typed runtime options and diagnostics directly from backend descriptors, so available configuration always matches what the server actually supports. See Configuration reference.Fleet-RLM — “About this instance” panel A new Settings panel surfaces the running service version, environment, and feature flags so you can confirm exactly what’s deployed before filing an issue. Powered by the new/api/v1/info endpoint in the HTTP API reference.Fleet-RLM — MLflow observability and auto-assessment
MLflow span processors now emit richer trace metadata, and you can wire scorer schedules to run automated assessment loops over completed sessions. See Observability.Fleet Pi — Daytona sandbox integration
Pi chat modes can now invoke Daytona sandbox tools end-to-end, with webhook and client support added to the web surface and improved startup memory recall. See Chat modes and Runtime SDK integration.Updates
- Session titles auto-derive from the first user message when no title is set, so conversations get human-readable labels without manual renaming. (fleet-rlm)
- Workbench UI polish — refined sidepanel controls, event display, and composer prompt overhead for a cleaner workspace.
- Runtime stack alignment — Fleet-RLM is now tested and published against Daytona 0.176, DSPy 3.2.1, Pydantic 2.13.4, SQLModel 0.0.38, Psycopg 3.3.4, Typer 0.25.1, and Uvicorn 0.47.0. Update your environment to match — see Installation.
- Fleet-RLM 0.5.31 patch release with a synced OpenAPI schema for frontend and SDK consumers.
Bug fixes
- History page restored. Conversation titles and transcript replay now show correctly when the durable session store only contains placeholder rows — the History view falls back to local conversation history instead of rendering opaque IDs.
- Resilient analytics initialization. PostHog callback registration no longer fails in threaded environments; it retries under a settings lock when needed.
- Hardened recursive delegation. Remote document context, degraded child execution metadata, and chunk-document aliases are handled more defensively, so partial failures surface clearly instead of returning stale evidence. See Recursive RLM.
- Frontend dependency security patches applied to address Dependabot alerts.