[DOCS] Session recap docs missing telemetry-disabled behavior and opt-out controls
Documentation Type
Missing documentation (feature not documented)
Documentation Location
https://code.claude.com/docs/en/common-workflows
Section/Topic
"Resume previous conversations" and the related session-return / command documentation for session recap (away summary)
Current Documentation
The resume workflow docs currently say:
When starting Claude Code, you can resume a previous session:claude --continuecontinues the most recent conversation in the current directoryclaude --resumeopens a conversation picker or resumes by name *claude --from-pr 123resumes sessions linked to a specific pull request
The commands reference currently says:
The table below lists all the commands included in Claude Code. |/config| Open the Settings interface to adjust theme, model, output style, and other preferences. Alias:/settings| |/resume [session]| Resume a conversation by ID or name, or open the session picker. Alias:/continue|
The telemetry docs currently say:
By default, error reporting, telemetry, and bug reporting are disabled when using Bedrock, Vertex, or Foundry.
There is no user-facing documentation for the session recap / away summary shown when returning to a session, the /recap command, the /config opt-out, or the CLAUDE_CODE_ENABLE_AWAY_SUMMARY environment variable.
What's Wrong or Missing?
Changelog v2.1.110 says: "Session recap is now enabled for users with telemetry disabled (Bedrock, Vertex, Foundry, DISABLE_TELEMETRY). Opt out via /config or CLAUDE_CODE_ENABLE_AWAY_SUMMARY=0."
That behavior is not documented in the product docs:
A. The feature itself is undocumented
The docs explain how to resume sessions, but not that Claude Code can generate a recap / away summary when you return.
B. Telemetry-disabled behavior is undocumented
Users on Bedrock, Vertex, Foundry, or with DISABLE_TELEMETRY=1 are explicitly called out by the changelog, but the docs do not explain that session recap is available for them too.
C. Opt-out controls are undocumented
The docs do not explain how to disable this behavior via /config or CLAUDE_CODE_ENABLE_AWAY_SUMMARY=0.
D. Manual invocation is undocumented
The command surface for manually requesting a recap is not documented in the command reference.
Suggested Improvement
Add a short, user-facing section that documents session recap / away summary behavior when returning to a session.
At minimum, document:
- When a recap appears after resuming a session
- That the feature is available for Bedrock, Vertex, Foundry, and
DISABLE_TELEMETRYusers as of v2.1.110 - How to opt out in
/config - How
CLAUDE_CODE_ENABLE_AWAY_SUMMARYworks, includingCLAUDE_CODE_ENABLE_AWAY_SUMMARY=0 - Whether
/recapis available for manual invocation, and if so, add it to the commands reference
Suggested placement:
- Add the main behavior explanation to
common-workflows - Add
/recapto the commands reference - Add the setting/env-var details to
settingsandenv-vars
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/common-workflows | Resume previous conversations should explain automatic recap / away summary behavior when returning to a session |
| https://code.claude.com/docs/en/commands | Full command reference should document /recap if it is a supported built-in command |
| https://code.claude.com/docs/en/settings | /config settings docs should expose the session recap opt-out control |
| https://code.claude.com/docs/en/env-vars | Environment variable reference should document CLAUDE_CODE_ENABLE_AWAY_SUMMARY |
| https://code.claude.com/docs/en/data-usage | Telemetry/provider-default docs should cross-reference the recap behavior for Bedrock, Vertex, Foundry, and DISABLE_TELEMETRY users |
Total scope: 5 pages affected
Source: Changelog v2.1.110
Entry text: Session recap is now enabled for users with telemetry disabled (Bedrock, Vertex, Foundry, DISABLE_TELEMETRY). Opt out via /config or CLAUDE_CODE_ENABLE_AWAY_SUMMARY=0.
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗