Release notes: July 17 to July 20, 2026

Back to the changelog

A focused update: you can now have Nomain scan connected repositories for committed secrets and mask them before analysis, and chat answers are more reliable end to end.

Highlights

• Secret scanning in connected repositories. Turn it on per repository and Nomain scans the downloaded code for committed secrets and masks any it finds before analysis runs, so secrets never reach the analyzed code, the graph, or the chat agent.
• More reliable chat answers. Answers no longer come back empty or half-formed, and a streaming answer now recovers if the model connection drops mid-reply.

Nomain app and agent

More reliable chat answers

We closed a set of edge cases that could leave an answer blank or cut short, and hardened live streaming so an answer that is interrupted mid-reply picks itself back up instead of stopping. You should see fewer empty or partial answers, with no change to how you ask questions.

Analysis and system management

Secret scanning in connected repositories

You can now have Nomain check a connected repository for committed secrets (API keys, tokens, credentials) and mask them before they are ever analyzed. See Repositories & sources.

• Opt-in per repository. Secret scanning is off by default and enabled by an administrator from the same New System, add source, and edit source dialogs as the path filter, because turning it on rewrites Nomain's stored copy of your code.
• Masked before anything reads it. On each analysis, findings are replaced in the stored code with a ***MASKED:…*** marker before parsing, so the secret never reaches the graph nodes, the explanations, or the embeddings the chat agent searches. Your original repository is not touched.
• Visible, but never leaked. A scan that finds something marks its analysis step with the new Alert status (an orange badge), lists each finding in the Job Log as rule: file:line, never the secret value itself, and the run still completes.