claude-code icon indicating copy to clipboard operation
claude-code copied to clipboard

Feature Request: Document Bedrock/Vertex feature availability in changelog

Open sfc-gh-mochen opened this issue 2 months ago • 1 comments

Summary

As a Bedrock user, I'd love it if the changelog could indicate when new features are not available on third-party providers (Bedrock, Vertex, Foundry). This would help set expectations and reduce confusion when features don't seem to work.

Context

After investigating the codebase, I discovered several features are gated behind Statsig feature flags that return false for third-party providers via the SX() check:

function SX() {
    return N0(process.env.CLAUDE_CODE_USE_BEDROCK) || 
           N0(process.env.CLAUDE_CODE_USE_VERTEX) || 
           N0(process.env.CLAUDE_CODE_USE_FOUNDRY) || 
           !!process.env.DISABLE_TELEMETRY || 
           !!process.env.CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
}

Features currently unavailable on Bedrock/Vertex:

Feature Gate Description
Session Memory tengu_session_memory Running session notes in summary.md
Session Memory Compact tengu_sm_compact Instant compaction using pre-written summaries
Tool Result Persistence tengu_tool_result_persistence Saving large tool results to files
Microcompact File Persistence tengu_compact_mc_files Saving cleared tool results to files for later retrieval

Example changelog entries that would benefit:

  • v2.0.64: "Made auto-compacting instant" → Could note this uses Session Memory which requires first-party API
  • Features using tengu_* gates that are disabled for third-party providers

Suggestion

When a changelog entry describes a feature that relies on Statsig gates disabled for Bedrock/Vertex, consider adding a note like:

  • Made auto-compacting instant (first-party API only)

Or a dedicated section:

Note for Bedrock/Vertex users: The following features in this release require first-party API access: ...

Why This Helps

  1. Sets expectations - Users won't spend time debugging why a feature doesn't work
  2. Transparency - Clear communication about platform differences
  3. Reduces support burden - Fewer confused users asking why features don't work

Thanks for the amazing tool! 🙏

sfc-gh-mochen avatar Dec 11 '25 16:12 sfc-gh-mochen

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

github-actions[bot] avatar Jan 11 '26 10:01 github-actions[bot]