Feature Request: Buddy message persistence / logging
Resolved 💬 2 comments Opened Apr 3, 2026 by welt-moro Closed Apr 3, 2026
Problem
Buddy (companion) messages disappear too quickly from the terminal. By the time I notice the speech bubble, it's already gone — making it hard to read what the buddy said.
Current Behavior
- Buddy quips render in a speech bubble for a brief duration, then vanish
- Messages are not logged anywhere (not in session JSONL, not in
~/.buddy-companion/state.json) - No hook event fires when buddy speaks
- No CLI flag or setting to control display duration
Requested Solutions (any of these would help)
- Configurable display duration — a setting like
buddy.messageDurationinsettings.json - Buddy message log — persist messages to
~/.buddy-companion/history.jsonor similar - Hook event — a
BuddyMessagehook that fires when buddy speaks, so users can build custom logging - Scrollback-friendly rendering — ensure buddy messages remain in terminal scrollback history even after the bubble disappears from the TUI
Context
- Buddy was just released (April 1, 2026) so this is early feedback
- The feature itself is delightful — just need a way to actually read the messages
- Existing issues (#41867, #41908, #41684) focus on customization/gamification but not message persistence
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗