Findings are observations that IronBee’s analysis identified — a browser console error that kept appearing, a failing form submission, a file with a high fix-cycle rate, or a pattern of retries. Each finding is grounded in actual session data, not generic advice.Documentation Index
Fetch the complete documentation index at: https://docs.ironbee.ai/llms.txt
Use this file to discover all available pages before exploring further.
Finding areas
Findings are grouped by area depending on which analysis type produced them:| Area | Question answered | Analysis type |
|---|---|---|
| quality | Is the agent testing thoroughly enough? | Quality |
| efficiency | Where is time or compute being wasted? | Quality, Cost |
| patterns | Which issues and files recur across sessions? | Quality |
| behavior | What working habits need adjustment? | Quality, Session Insights |
| cost | Where is spend going and what should change? | Cost |
Severity levels
| Severity | Meaning |
|---|---|
notice | Descriptive observation — informational only, no action required |
concern | Worth watching — may generate a recommendation |
critical | Serious degradation — should generate a recommendation |
concern and critical findings may have recommendations attached. notice findings are purely descriptive.
Findings list
The Findings tab shows all findings for the current analysis, grouped by area and sorted by severity. Each finding includes:- Title — a brief description of the observation
- Severity — critical / concern / notice
- Area — quality / efficiency / patterns / behavior / cost
- Body — full markdown description with supporting evidence, metrics, and sometimes visualizations
- Linked recommendation (if any) — the action derived from this finding
Visualizations
Some findings include inline diagrams (pie charts, bar charts, Gantt, journey diagrams) rendered from the finding body. Visualizations are decorative — every fact they show is also stated in prose.Session insight findings
Session insight findings are rich multi-paragraph reports rather than single observations. They cover:- Session highlight — a standout session with notable characteristics
- At-a-glance — four summary sub-findings (sessions, hours, cost, cache)
- Project areas — patterns, friction points, interaction style
- What works — validated effective behaviors
- Features to try — underused capabilities relevant to the project