# Claude Code Feature availability by provider

> Claude subscription, API, Passion8, Bedrock, Vertex and Foundry capability boundaries, caching and alternatives.

URL: https://docs.passion8.cc/en/docs/claude-code/feature-availability
Language: en
Publisher: Passion8

Separate local Code capabilities from account/cloud features. Passion8 routes model requests through a custom endpoint; account, hosted-cloud, organizational or browser-extension capabilities do not automatically follow.

## At a glance

| Feature type | Passion8 interpretation |
| --- | --- |
| Local CLI/IDE, commands, hooks, skills, MCP, subagents | Generally local-process capabilities |
| Models, context, effort, thinking, search | Actual upstream and field forwarding |
| Caching | Provider, forwarding and TTL policy |
| Web/mobile/Remote Control/Routines/Artifacts/Chrome/computer use | Often official account/cloud features, not gateway entitlements |
| Organizational settings, analytics, review | Tied to official accounts and backend |




Subscription availability does not establish custom-gateway availability. Passion8 supplies model routing and compatible requests, not a replacement subscription identity.




Use provider authentication guidance when choosing a path, and the [protocol checklist](https://docs.passion8.cc/en/docs/claude-code/gateway-protocol) when implementing a gateway.

## Generally provider-independent local features

These run mainly in the local process:

| Capability | Description |
| --- | --- |
| CLI/IDE | Core loop in terminal, VS Code or JetBrains |
| Commands | Help, initialization, memory and project commands |
| Subagents/workflows | Isolated context and orchestration |
| Hooks/permissions | Before/after interception and rules |
| Instructions/skills/plugins | Local/repository extensions |
| MCP | stdio, HTTP, SSE and WebSocket connections |
| Checkpoints/worktrees | Local files and Git mechanisms |
| OTel | Local traces, metrics and logs |

Exceptions arise from dependencies: networked MCP, provider search and subagent model IDs must actually work.

## Subscription-dependent features

These usually require official login rather than only an API/gateway token:

| Feature | Requirement | Gateway boundary |
| --- | --- | --- |
| Web/mobile Code | Eligible subscription login | Cloud does not inherit local environment |
| Remote Control | Account pairing | Custom credentials may prevent availability |
| Routines/schedule | Cloud routine service | Different from local loop |
| Chrome | Extension and subscription | Not ordinary API functionality |
| Computer use | macOS, eligible personal plan, interactive session | Not general enterprise/third-party availability |
| Artifacts | Eligible logged-in account | API/gateway sessions usually cannot publish |
| Review/analytics/server settings | Team/Enterprise organization | Generally not supplied through third-party gateways |

## Provider comparison

| Feature | Anthropic API | Subscription | Passion8/gateway | Cloud providers |
| --- | --- | --- | --- | --- |
| Search | Usually available | Available | Upstream/forwarding | Some restrictions |
| Fast mode | Supported | Supported | Upstream/forwarding | Usually unavailable |
| Auto mode | Normally enabled | Normally enabled | Version/settings | May need enable variable |
| Advisor | Server tool | Available | Requires full compatible upstream | Usually unavailable |
| Explicit loop interval | Available | Available | Local session | Usually available |
| Self-paced loop | Available | Available | Provider-dependent | Some fall back to ten minutes |
| Routines | Not API-key feature | Available | Usually unavailable | Usually unavailable |
| GitHub/GitLab CI | Available | Available | Explicit credentials required | Foundry may differ |

## Diagnose gateway availability

| Problem | Check |
| --- | --- |
| Missing picker models | [Discovery](https://docs.passion8.cc/en/docs/claude-code/gateway) and enable variable |
| Effort/thinking/1M unavailable | Actual model plus beta/body forwarding |
| Search unavailable | Provider/server tool, not local capability |
| Remote/schedule missing | Login eligibility or feature flags |
| No server settings | Use endpoint-managed files or MDM |
| No analytics | Local OTel remains distinct from official dashboards |

## Cache effects

Provider differences affect caching:

| Action | Consequence |
| --- | --- |
| Switch official login to Passion8 | Provider/auth change usually rebuilds cache |
| Change upstream model | Model-key change usually misses |
| Change fast/effort/context | Request changes usually miss |
| Hooks/status/theme | No necessary effect unless prompt/tools change |
| Cloud sessions | Separate from local gateway cache |

Stabilize provider, model, effort and tools before long tasks. Longer intervals benefit from supported one-hour TTL; idle short-TTL caches expire.

## Alternatives

| Goal | Passion8 approach |
| --- | --- |
| View local tasks on mobile | Try eligible Remote Control, otherwise background session/logs |
| Scheduled local checks | Local loop or cron with claude -p |
| Cloud PR fixes | Official web/CI with explicitly configured credentials |
| Visual result page | Local HTML/Markdown hosted internally |
| Browser verification | Playwright/MCP; official Chrome needs account features |

## Official references

- [Feature availability](https://code.claude.com/docs/en/feature-availability.md)
- [Model configuration](https://code.claude.com/docs/en/model-config.md)
- [Prompt caching](https://code.claude.com/docs/en/prompt-caching.md)
- [LLM gateway connect](https://code.claude.com/docs/en/llm-gateway-connect.md)
- [Scheduled tasks](https://code.claude.com/docs/en/scheduled-tasks.md)