Roadmap: 1.0 (Foundation Models 26) and 2.0 (Foundation Models 27)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- swift
- Domain
- ai, api, mobile-dev
Research direction
Start by reviewing the roadmap's listed Foundation Models API parity gaps and the current 1.0 and 2.0 compatibility plans. No files, tests, or entry points are named in the issue; done requires an agreed scope for the 1.0 cleanup and the iOS/macOS 27 breaking changes.
Written by the indexing model from the issue text.
Description
Now that @pcuenca and I are back on this, here's the plan:
1.0 — a stable release against the current Foundation Models API in iOS/macOS 26. Before tagging it, I want to tidy up the places where AnyLanguageModel grew beyond what Apple's framework offers, mostly to compensate for early limitations:
- Remove the APIs that are already marked deprecated (Llama passthrough properties, the legacy Gemini
Thinking/ServerTooltypes). - Fix
respond(to:schema:), which currently ignores itsschemaargument. - Make
InstructionsSendable, and close a few other small parity gaps. - Clearly mark our extensions (tool execution delegate, image inputs,
[custom:]options) as extensions.
2.0 — track the Foundation Models changes in iOS/macOS 27. I expect source-breaking changes around session construction, image inputs, and generation options, so that'll be a major version. Availability-gated additions (like #206) can land before then.
If there's something you need in 1.0, please say so here.
- Dominant language
- Swift
- Stars
- 948
- Forks
- 99
- Avg merge
- 19h 57m
- Merged PRs (30d)
- 50
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from huggingface/AnyLanguageModel
-
OpenAILanguageModel replays tool-call arguments as GeneratedContent's Codable form, not JSONPossibly taken @gtokman claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
huggingface/AnyLanguageModel#324 ·
Maintainers usually reply within 1 day
-
MLXLanguageModel tool calling: flaky repeat check, missing assistant tool-call turn, and tool-round limitsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 18/100
huggingface/AnyLanguageModel#328 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
huggingface/AnyLanguageModel#327 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
huggingface/AnyLanguageModel#326 · 1 comment ·
Maintainers usually reply within 1 day
-
Support the Gemini Interactions API in GeminiLanguageModelMay be free again @rizwankce claimed this 7 days ago, and no pull request is open. Open
Difficulty 5/5 Over a week Newbie friendliness 45/100
huggingface/AnyLanguageModel#302 · 2 comments ·
Maintainers usually reply within 1 day
All issues in huggingface/AnyLanguageModel
Similar issues
-
swift.md: `Date(myString, strategy: .iso8601)` example omits `try` — the initializer is throwingOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
core: RAC_LLM_OPTIONS_DEFAULT.min_p disagrees with the IDL's annotated defaultPossibly taken A pull request linked to this issue is open or already merged. Openbug core p3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
RunanywhereAI/runanywhere-sdks#1083 ·
Maintainers usually reply within 5 days
-
bug/fix needs: triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
capawesome-team/capacitor-firebase#1054 ·
Maintainers usually reply within 1 day
-
area: docs eco: swift good first issue help wanted lane: free-agent roadmap size: XS type: docs
Difficulty 1/5 Under an hour Newbie friendliness 62/100
arminazimi/evergreen#441 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day