--- title: "1.15.19 — Bounded Assistant approvals and operational tools" description: "The Admin Assistant now has a complete operator surface, owner-managed credentials, server-owned approval cards for every mutation, and permission-aware WebApp and cloud operations. Maintenance refreshes also discover new django-mojo releases immediately." date: "2026-08-22" tags: ["release"] canonical: "https://django-mojo.sitesmojo.com/changelog/1-15-19/" --- The Admin Assistant now has a complete operator surface, owner-managed credentials, server-owned approval cards for every mutation, and permission-aware WebApp and cloud operations. Maintenance refreshes also discover new django-mojo releases immediately. ### Added - Admin now includes a responsive Assistant panel with conversation history, streamed responses, structured result blocks, and owner-only credential and model setup. - Mutating Assistant tools now produce durable, server-owned approval cards that can be resolved over REST or WebSocket with live permission, fresh-auth, infrastructure-mode, and resource-revision checks. - The Assistant can inspect and operate WebApps, deployments, framework maintenance, managed-service upgrades, and fleet capacity through the same service and authorization boundaries as Admin. ### Changed - Assistant results are bounded and permission-filtered; deployment, capacity, metrics, and resource projections expose only the evidence and limits appropriate to the operator. - WebApp teardown and onboarding authority are shared across Admin and Assistant so destructive behavior and tenant checks have one implementation. ### Fixed - Maintenance Refresh now bypasses the framework version cache, so newly published django-mojo updates appear immediately. - Assistant approval fingerprints remain stable for long resource identifiers, responsive panel mode follows the actual viewport, and malformed operation identifiers fail safely. - WebApp take-offline results no longer claim an address stopped serving when its remaining routes keep it online. ### Security - Approval records redact sensitive arguments before fingerprinting and re-check authorization immediately before single-consumption execution. - Assistant setup secrets are excluded from request logs, and model-provided file URLs become links only when they are same-origin HTTPS. ### Upgrade notes - Apply the included migrations before enabling Assistant approvals; existing Assistant reads remain available independently of the new mutation workflow.