🚀 What’s New
- Zero-Touch First-Boot Evaluation: A brand-new install now works end to end with zero manual intervention. First boot, the sample-repository scan, and the complete in-product GitHub App flow (create, authorize, install) were each verified live against a virgin install — your evaluation starts scanning immediately, no support ticket required.
- Unified BYOAI Model Configuration: The platform’s AI agents now have one canonical naming convention everywhere — fast (validation and finding enrichment), smart (remediation), and embedding (semantic code index). Whether you’re connecting your own models for validation or remediation, configuration is now simpler and consistent across the entire platform, with automatic backward compatibility for existing setups.
🛠 Improvements
- Gitea Connector Profile Display: The Gitea connector configuration page now visually confirms a successful connection by fetching and displaying the authenticated user’s avatar, full name, email, and a direct profile link — giving you the same connected-profile experience as the GitHub connector.
- Explicit Email Delivery Status: Self-hosted deployments can now explicitly declare when outbound email is intentionally disabled. The platform no longer silently fails when email isn’t configured — it clearly reports the state, so you always know whether notifications, scan-complete alerts, and support tickets are reaching their destinations.
- Reliable Codex Remedium Cold Starts: On fresh installations, the first AI remediation no longer times out while the remediation engine initializes. Codex Remedium now uses the full activity window for retries, ensuring your first fix lands as a real pull request even on a cold node.
🔧 Fixes
- Scan stuck on first boot: A first-boot timing issue could leave every scan permanently queued with no progress. Scans now start reliably on the very first launch — no need to restart or contact support.
- GitHub App creation failed on non-public origins: The in-product GitHub App creation flow no longer dead-ends with a Hookurlcannotbeblank or Nameisalreadytaken error on localhost, LAN, or any non-public origin. The app name is now uniquely pre-filled, and the manifest is correctly formed for all environments.
- GitHub Connect button missing credentials: Pressing Connect after creating a GitHub App now correctly builds the authorization URL — previously, a missing credential could send you to a GitHub 404.
- New-vs-fixed finding counts: The Dashboard’s new-vs-fixed finding trend now correctly tracks remediated findings, so your remediation progress is accurately reflected in the metrics.