Bug Reports
Reviewing
format nova reports so they aren't wall of text and brain spraining
Agent reports are currently too log-like. Useful details get buried: context, risk, actions taken, final state, and follow-up.
Please add a structured completion format for git/project work:
- Context
- Risk
- Resolution
- Result
- Follow-up
- Proposed convention
Reference mockup:
https://imgur.com/a/kx2uHGB
This would make reports easier to convert into issues, PR notes, changelog entries, and audit trails.
Why it matters
For shared-checkout / multi-agent work, maintainers need to quickly see:
- what changed
- where it landed
- whether the main checkout stayed clean
- whether signing was verified
- what follow-up is needed
Category
UX improvement / agent workflow reporting / warlock readability
1 Comment
Sign in to comment
Love this feedback — and the mockup is genuinely useful (Context / Risk / Resolution / Result / Follow-up is a clean structure). We've filed this as an agent reporting UX improvement, especially for multi-agent shared-checkout work where maintainers need to scan quickly. The mockup is linked in our internal tracker.