claude-code - 💡(How to fix) Fix Request Auto-Dream rollout for my account (tengu_onyx_plover server flag)

Summary

Requesting that my account be added to the Auto-Dream rollout cohort. The feature is present in the binary I'm running but the server flag (tengu_onyx_plover) hasn't been enabled for my account yet.

Environment

• Claude Code version: 2.1.143
• Platform: Linux (Ubuntu) on x86_64
• Plan: Max
• Authenticated via OAuth

What I've verified locally

The auto-dream subsystem is fully shipped in my binary. strings $(which claude) returns:

Enable background memory consolidation (auto-dream). When set, overrides the server-side default.
autoDreamEnabled
tengu_auto_dream_skipped
tengu_auto_dream_fired
tengu_auto_dream_completed
tengu_auto_dream_failed
tengu_auto_dream_toggled
tengu_onyx_plover
[autoDream] lock held by live PID
[autoDream] recordConsolidation write failed
[autoDream] readLastConsolidatedAt failed
[autoDream] listSessionsTouchedSince failed
...

The /dream slash command is also registered in the binary (with userInvocable: true, alias learn, and an isEnabled() gate).

What's blocking access

I've set "autoDreamEnabled": true in ~/.claude/settings.json per the binary's documented override behavior, but:

1. /memory in any session does not show an Auto-dream: on/off toggle line — the option simply isn't present in the selector
2. Per multiple third-party writeups, this means the server-side feature flag tengu_onyx_plover hasn't been deployed to my account
3. The binary description string says "When set, overrides the server-side default" which suggested an OR-gate, but empirically it behaves as AND-gated (client setting cannot bypass the server gate)

Use case

I'm an active Claude Code user across multiple long-running projects (months of session history per project). Memory accumulation is a real pain point — I currently work around it with the community replica grandamenium/dream-skill, but I'd prefer to use the canonical Anthropic implementation since:

• The community version is explicitly described as a replica of the unreleased Anthropic feature
• Maintaining a manual Stop hook + dream-pending flag pattern feels fragile vs. the native implementation
• Switching is essentially free for me — the memory file format is documented as compatible

Request

Could my account be added to the tengu_onyx_plover rollout cohort? Happy to provide my account email via support channel or DM if needed.

Documentation feedback (minor)

The binary description "When set, overrides the server-side default" is misleading — it sounds like the client setting can unilaterally enable the feature, but in practice the server flag is required. Suggest clarifying to: "When set, takes precedence over the server-side default once the feature has been enabled for your account."

Thanks!