dejima-audit UX and behavior improvements #65

Closed
opened 2026-08-03 20:40:40 -07:00 by branderson · 0 comments
Owner

dejima-audit needs another round of UX improvements. dejima-audit ack has some issues affecting usability and also has a major bug making it mostly useless.

  • exact approvals ([a] approve this exact content) are not being recorded, and these findings continue to be shown every time dejima-audit ack is run in a project
  • color is needed. We should add color to this utility when available to highlight the severity of issues, filenames, the splits between diffs and between file content and dejima-audit UI text. Currently everything blends together in one color with no whitespace or anything to separate sections
  • dejima prompts the user to continue or quit if there are unacknowledged findings in the workspace, but the container hasn't started yet. We could directly drop them into dejima-audit ack with a keystroke [a] here, so that they can resolve prior acks before diving into the container
  • this warning in dejima itself (unacknowledged CRITICAL finding(s)) should also be color-coded. CRITICAL should stand out, the number of findings, the command to run manually outside of dejima, the keystrokes to choose options, and the run IDs should all be highlighted in dejima
  • in dejima-audit ack, the key for skip should be [s], not [c]
  • any warning which cannot be acknowledged should only be shown once. They should not build up and gate exit from dejima-audit ack forever
dejima-audit needs another round of UX improvements. `dejima-audit ack` has some issues affecting usability and also has a major bug making it mostly useless. - exact approvals (`[a] approve this exact content`) are not being recorded, and these findings continue to be shown every time `dejima-audit ack` is run in a project - color is needed. We should add color to this utility when available to highlight the severity of issues, filenames, the splits between diffs and between file content and dejima-audit UI text. Currently everything blends together in one color with no whitespace or anything to separate sections - `dejima` prompts the user to continue or quit if there are unacknowledged findings in the workspace, but the container hasn't started yet. We could directly drop them into dejima-audit ack with a keystroke [a] here, so that they can resolve prior acks before diving into the container - this warning in dejima itself (unacknowledged CRITICAL finding(s)) should also be color-coded. CRITICAL should stand out, the number of findings, the command to run manually outside of dejima, the keystrokes to choose options, and the run IDs should all be highlighted in `dejima` - in `dejima-audit ack`, the key for skip should be [s], not [c] - any warning which cannot be acknowledged should only be shown once. They should not build up and gate exit from `dejima-audit ack` forever
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dejima/dejima#65