Hello all you users of the Swift extension for VS Code!
We are planning another VS Code Swift Community Office Hour on Thursday May 21st.
Event Details:
Hosts: @matthewbastien
When: Thursday, May 21, 2026 1PM EST | 7PM CET/CEST
Where: DM for Webex invite
Agenda:
An updated agenda and meeting minutes will be posted to a Github discussion
Everyone is welcome, so please feel free to invite anyone you think might be interested. This is a laid-back space to ask questions, share experiences, and learn from each other—whether you're an experienced developer or just starting out.
Please note that we expect members joining to adhere to the Swift's Code of Conduct.
See you all there!
Tracy
4 Likes
Thank you everyone for coming and also to those who demo'ed some cool Swift projects! Here are the minutes from the meeting:
Intro and Demos:
- @Padmashree06 was chosen as a GSoC 2026 contributor. She will be working on improved Swift DocC support in SourceKit-LSP/VS Code. Welcome to the Swift Community!
- @matthewbastien demo'ed improved Swift extension startup performance and automatic toolchain switching.
- @sebsto demo'ed working with Swift in Amazon's Kiro Agentic IDE.
- @Joannis_Orlandos demo'ed the WendyOS extension in VS Code
Q&A Session:
Q: When will the extension activation changes be available?
- A: We're having some trouble with CI, but the changes should land in a pre-release by next week. The plan is to have it soak for about a month to iron out any issues before doing an official release.
- Q: I'm having an issue where the extension is constantly re-indexing my AWS SDK when it doesn't need to. What's the best way to report this?
- A: Report any issues with indexing to the SourceKit-LSP repository and include a
sourcekit-lsp diagnose if possible. The more reports of issues we get the easier it is to find and prioritize fixes.
- Workaround: You might be able to disable background indexing as a temporary fix and have SourceKit-LSP only index when you build.
- Q: Will the Swift extension pre-release fix
PATH issues involving swiftly? My editor is preferring to use the toolchain in /usr/bin/swift over swiftly's.
- A: No, this is an issue that was fixed in swiftly itself. It will be available in swiftly v1.2.0 when that gets published. If you're still seeing this issue after the swiftly v1.2.0 release then please file an issue and we can have another look!
- Q: How often will there be VS Code office hours?
- A: We'd like to have these meetings at a regular cadence, but haven't decided on timing yet. At most it will be every couple of months. Stay tuned for more invites!
4 Likes