Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Feature Request] Companion customization & context window alerts [1 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#46196•Fetched 2026-04-11 06:26:37
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
OMNES-VAOMNES-VA
Participants
OMNES-VAOMNES-VA
Timeline (top)
labeled ×4renamed ×1
RAW_BUFFERClick to expand / collapse

Bug Description Feature Request: Companion customization & context window alerts

I'd love the ability to configure Nape's(my companion) behavior beyond the current fixed UI. Specifically:

  1. Context window threshold alerts — trigger a Nape hint when I reach a configurable % of my context window (e.g., 60%, 80%). This would help me decide when to /compact before losing context mid-task.
  2. Custom hint triggers — ability to define conditions (via settings.json or hooks) that prompt Nape to show a message, similar to how hooks work for tool events.
  3. Opt-in hints — e.g., "you haven't committed in 30 minutes" or "3 files changed, consider a checkpoint."

The context window alert specifically would be very practical — right now there's no passive indicator when a session is getting long, so /compact often happens reactively rather than proactively.

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.100
  • Feedback ID: 694aa1ff-4f56-4218-b90b-68e814490c34

extent analysis

TL;DR

Implementing customizable threshold alerts and hint triggers for Nape's companion behavior is likely to require updates to the settings.json file or the addition of new hooks.

Guidance

  • Review the existing settings.json file to determine if there are any configurable options related to Nape's behavior that can be modified to achieve the desired functionality.
  • Investigate the available hooks for tool events to see if they can be repurposed or extended to trigger custom hints based on specific conditions.
  • Consider submitting a feature request to the development team to add support for context window threshold alerts and custom hint triggers.
  • Look into the documentation for the current version (2.1.100) to see if there are any planned updates or roadmap items related to companion customization.

Example

No code snippet is provided as the issue does not contain sufficient technical details to create a concrete example.

Notes

The provided information is a feature request rather than a bug report, and the solution may involve updates to the application's configuration or codebase.

Recommendation

Apply workaround: Submit a feature request to the development team to add support for context window threshold alerts and custom hint triggers, as the current version does not seem to support these features.

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…
#orchestration issue#cache issue#memory leak#API versioning#request timeout

Still need to ship something?

×6

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

Back to top recommendations

TRENDING