Request
Please extend afm-server to expose Apple’s
PrivateCloudComputeLanguageModel through its
OpenAI-compatible API.
Current behavior
Using afm-server 1.1.0-beta.3 on macOS 27:
/v1/models exposes only apple.local.- Direct requests to
apple.local work correctly.
/v1/models/pcc returns 404 Model not found.- Loading a
.fmadapter customizes the on-device model rather than providing PCC access.
Requested behavior
Ideally, afm-server would:
- Expose PCC through a distinct model ID such as
apple.pcc.
- Preserve
apple.local for fully on-device use.
- Report PCC availability, entitlement, quota, and unsupported-state errors clearly.
- Support OpenAI-compatible chat completions, streaming, sessions, and delegated tool calls through PCC.
- Document PCC requirements and privacy implications.
Use case
This would allow clients such as Jan to use Apple’s larger-context,
higher-capability PCC model while retaining afm-server’s
OpenAI-compatible API and client-delegated tool-calling support.
It would be especially valuable for PRIVATE document analysis, longer conversations with a top-model for close to free.
Apple documents PCC as the separate
PrivateCloudComputeLanguageModel
type.
Request
Please extend afm-server to expose Apple’s
PrivateCloudComputeLanguageModelthrough its OpenAI-compatible API.Current behavior
Using afm-server
1.1.0-beta.3on macOS 27:/v1/modelsexposes onlyapple.local.apple.localwork correctly./v1/models/pccreturns404 Model not found..fmadaptercustomizes the on-device model rather than providing PCC access.Requested behavior
Ideally, afm-server would:
apple.pcc.apple.localfor fully on-device use.Use case
This would allow clients such as Jan to use Apple’s larger-context, higher-capability PCC model while retaining afm-server’s OpenAI-compatible API and client-delegated tool-calling support. It would be especially valuable for PRIVATE document analysis, longer conversations with a top-model for close to free.
Apple documents PCC as the separate PrivateCloudComputeLanguageModel type.