claude-code - 💡(How to fix) Fix Feature request: setting to disable the companion (Voidspinner) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45032Fetched 2026-04-09 08:14:54
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×2commented ×1cross-referenced ×1

Claude Code 2.1.92 introduced a companion character ("Voidspinner") that appears in the terminal UI with a speech bubble. There is currently no way to disable it.

Root Cause

Some users find the companion distracting in a professional/focused terminal workflow. It should be easy to opt out without sacrificing core functionality.

Fix Action

Fix / Workaround

Current workarounds

Code Example

{
  "companionEnabled": false
}
RAW_BUFFERClick to expand / collapse

Summary

Claude Code 2.1.92 introduced a companion character ("Voidspinner") that appears in the terminal UI with a speech bubble. There is currently no way to disable it.

Request

Add a settings.json key to opt out, e.g.:

{
  "companionEnabled": false
}

Or a CLI flag: --no-companion

Current workarounds

  • --bare — suppresses the companion but also disables hooks, CLAUDE.md, auto-memory, and plugins. Too aggressive for normal use.
  • No other option exists.

Why this matters

Some users find the companion distracting in a professional/focused terminal workflow. It should be easy to opt out without sacrificing core functionality.

extent analysis

TL;DR

Adding a companionEnabled key to settings.json or a --no-companion CLI flag could allow users to opt out of the Voidspinner companion character.

Guidance

  • Consider adding a companionEnabled key to settings.json to provide a configuration option for disabling the companion character.
  • Introduce a --no-companion CLI flag as an alternative way to opt out of the companion character.
  • Evaluate the current --bare flag to determine if its behavior can be modified to only suppress the companion character without disabling other features.
  • Assess the impact of disabling the companion character on the overall user experience and functionality.

Example

{
  "companionEnabled": false
}

This example shows how the settings.json file could be updated to include the companionEnabled key.

Notes

The introduction of the companionEnabled key or --no-companion flag would require updates to the application's configuration parsing and CLI flag handling.

Recommendation

Apply workaround by adding a companionEnabled key to settings.json or introducing a --no-companion CLI flag, as this would provide users with a simple way to opt out of the companion character without sacrificing core functionality.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING