Skip to main content

Share Feedback

When nori gets something wrong — a control that fails for the wrong reason, a wiki page that misreads your architecture, a document summary that misses the point — Share Feedback reports it directly from the screen where you found it, optionally with the result attached so the problem can be reproduced.

Attaching is off by default, and this page describes exactly what an attachment does and does not contain. If you are clearing nori through a security review, read the What is uploaded section rather than relying on the summary.

Where the action appears​

WhereWhat it reports onWhat can be attached
A control's result pagethe verdict and findings for that controlthat control's findings file
A wiki topicthe generated pagethat page
Wiki (Files) — a document summarynori's AI summary of a document you uploadedthat summary
The project headerthe standard the project runs againstthe project's whole data folder

The action needs a connection to azuma and is disabled offline — it is not queued for later.

Sending feedback​

  1. Choose This is wrong or This is correct. There is no default; a verdict you did not give is not one nori will invent for you.
  2. Describe the problem under What should we know? — what is wrong, and what you expected instead. Up to 4000 characters, and required.
  3. Optionally tick the attachment box.
  4. Send feedback.

What is uploaded​

If you send feedback without ticking the attachment box, only your verdict and your comment are transmitted.

If you tick it, one artifact is uploaded to azuma's private storage alongside the report.

Before you send, you see the full list​

Ticking the box for the data-folder attachment opens What will be uploaded: the total file count and size, then one row per top-level folder, each expandable to every individual file by name and size. Nothing in that list is sampled, truncated, or summarised — a list that quietly stopped after the first few entries would be worse than no list, because it would look complete.

Beneath it, a Never uploaded line accounts for what was held back, with counts and sizes.

For this attachment you must additionally tick a second box confirming you have reviewed the list. If the folder changes while you are writing — a background run finishing, for example — nori refuses to send, shows you the updated list, and clears that confirmation so you review it again. What is uploaded is always what you reviewed.

What is never included​

Three things are excluded from every attachment, unconditionally:

  • The evidence documents you uploaded. PDFs, certificates, diagrams — the originals never leave your machine.
  • The text nori extracted from them. A different file name carrying the same content would defeat the point of excluding the first.
  • Your project's config.json. It can hold your provider API key in plain text, along with the absolute path to your source tree.

What an attachment can contain​

An attachment is nori's own output about your project, and that output can quote your code.

  • A findings file — the smallest attachment — lists the findings for one control. A finding may carry a file path, a line number, and a short snippet of the code it refers to.
  • The data-folder archive contains everything above for every run, plus the wiki pages nori generated from your source, the raw responses your AI model returned, the comment threads on your findings (including reviewer names and email addresses), and any guided-triage transcript.
  • The archive also includes the full prompts and responses exchanged with your model for any exchange that failed, and for all exchanges if you had debug logging enabled. A prompt can carry a substantial amount of repository content.
This is the one path by which your code can reach azuma

Analysis, indexing and telemetry never upload your source — see Telemetry & Privacy. A Share Feedback attachment is the deliberate exception: you tick a box, you review an itemised list, and for the data-folder archive you confirm a second time. If your organisation cannot share code excerpts, send feedback without an attachment. The report is still useful.

Size limits​

An attachment is capped at 200 MB, and a data folder holding more than about 256 MB of files cannot be packaged safely. In either case nori tells you the actual size and suggests sending the feedback without the attachment, or clearing out indexed documents first.

Where it goes​

Feedback and any attachment are sent to azuma over HTTPS. Attachments are stored in a private container, one file per report, and are used to reproduce and fix the problem you reported.