feat(tui): image renderer integration — thread through AppCtx #98
No reviewers
Labels
No labels
area:agents
area:ai
area:config
area:dashboard
area:design
area:design-review
area:devtools
area:entities
area:gallery
area:generate
area:image
area:infra
area:meta
area:model-browser
area:navigation
area:presets
area:security
area:sessions
area:settings
area:sharing
area:test
area:ux
area:webhook
area:workdir
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/loom!98
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "tui/image-ctx-85"
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?
Summary
render_image()anddelete_image()convenience methods toAppCtxArc<Mutex<Box<dyn ImageRenderer>>>is populated fromCoreHandlesat startupTest plan
Closes charles/loom#85
🤖 Generated with Claude Code
Review — PR #98: image renderer through AppCtx
LGTM. Small, focused, does exactly what it says.
Minor
render_imagesilently swallows a poisoned mutex (renderer.lock().ok()?). This is the right call for the render path — you don't want a panic mid-frame — but atracing::warn!onErrwould help debug if someone ever hits a poisoned lock.delete_imagesimilarly swallows errors silently vialet _ = guard.delete(handle). Same suggestion: a debug/warn log would be cheap insurance.