Workspace's right panel has no 'history' section showing recent actions — user wanting to see what they did 5 minutes ago (e.g., 'I just rotated the image, what angle?') has no log #322
Labels
No labels
blocked:commit-ready-failed
blocked:gate-fetch
blocked:gate-lint
blocked:gate-plan
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:needs-human
blocked:no-changes
blocked:verify-failed
bug
deferred
feature-request
in-progress
needs-decompose
needs-triage
quickfix
security/medium
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/Kimi_Agent_Brother_10_Digitizing_App#322
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Finding
grep -rn 'history.*log\|actionLog\|recentActions' src/components/workspace/returns 0. The workspace has no action log.The workspace's state has
history: HistoryState[]for undo/redo, but no human-readable action list.A user with 30 actions in the last 5 minutes:
The fix is an "Activity" or "Recent actions" log.
Where
src/components/workspace/useWorkspace.ts(history)grep -rn 'actionLog' src/components/workspace/returns 0Suggested fix shape
State: add
actionLog: Array<{ timestamp: number; action: string; details?: object }>to the workspace's state. Each action that affects the design logs an entry.UI: in the right panel (or as a sidebar), an "Activity" section:
Severity
Low. The user can use undo. Power users with complex workflows notice.
Discovered by
Gap analysis (2026-10-02) of workspace affordances.
Related
Mark referenced this issue2026-10-04 03:59:53 +00:00
Closed by commit
35add94(feat #322: Workspace Activity log).What landed:
Categorical settings (hoop/fabric/stabilizer/filename/preference/underlay/autoThreadMatch/machineProfile) get logged; numeric slider keys do not — those would flood the log on every drag tick. Per the issue spec, persistence is intentionally session-local.