## Summary The `/buddy` companion feature generates real-time speech bubble responses that are displayed to users in the terminal UI, but these responses are **not persisted anywhere** — not in session JSONL, not in ~/.claude.json, not in debug logs. ## Why this matters - **No audit trail** — if the companion says something inappropriate or harmful, there is zero evidence for the user to reference or report - **No reproducibility** — Anthropic cannot investigate companion behavior incidents w

Buddy companion speech bubble responses are not persisted in session logs

Status Closed — not planned

Maintainer reply None cached

Activity 4 comments · opened Apr 2, 2026 · closed Apr 9, 2026

Summary

The /buddy companion feature generates real-time speech bubble responses that are displayed to users in the terminal UI, but these responses are not persisted anywhere — not in session JSONL, not in ~/.claude.json, not in debug logs.

Why this matters

No audit trail — if the companion says something inappropriate or harmful, there is zero evidence for the user to reference or report
No reproducibility — Anthropic cannot investigate companion behavior incidents without logs
Asymmetric logging — every tool call, assistant message, and hook execution is logged with millisecond timestamps, but the one component with a personality engine and zero supervision is ephemeral

What we verified

| Location | Companion bubble text found? |
|---|---|
| Session JSONL (all message types) | No — only companion_intro and petted events |
| ~/.claude.json companion field | No — only name, personality, hatchedAt |
| ~/.claude/debug/ logs | No |
| ~/.claude/history.jsonl | No |
| Terminal scrollback (kitty) | No — bubble is a TUI overlay, not terminal text |

The only message types in the JSONL are: message, assistant, user, text, tool_use, tool_result, thinking, system, file-history-snapshot, queue-operation, attachment, companion_intro. No companion_response type exists.

Suggestion

Persist companion speech bubble text in the session JSONL as a companion_response message type, consistent with how all other session activity is logged.

Environment

Claude Code v2.1.90
Companion: Gristle (octopus, Rare)
macOS Darwin 25.3.0

View original on GitHub ↗

4 Comments

byPawel · 6 months ago

This is about the /buddy companion feature shipped in Claude Code v2.1.89+. The companion generates speech bubble responses in the terminal UI that are not persisted in session logs.

The companion_intro attachment type already exists in the session JSONL (verified), but the actual speech bubble text generated by the companion has no corresponding companion_response entry. This is an accountability gap — every other piece of session activity (tool calls, assistant messages, hooks) is logged with timestamps.

Reopening as this is a valid Claude Code feature request, not an unrelated issue.

alii · 6 months ago

Thank you for trying out the buddy. It was a small April Fools feature and has been removed in the latest release, so closing this as not planned.

byPawel · 6 months ago

@alii Aww, that's actually sad news ;) The buddy had real charm, and honestly with proper logs it's the rare joke feature that would've been genuinely useful beyond the punchline. Casting my vote for a comeback :P

github-actions[bot] · 6 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.