According to the docs, if frontMatter.sponsors.ai.enabled is set to false, then all AI features should be disabled. I would also expect, not being a sponsor currently, to not receive these features by default. But when I create a new post via Dashboard > Create Content it loads a while and then offers me 5 titles via AI (Copilot) based on my typed title. Setting enabled to false does not result in my typed title being used immediately, it still loads the AI results, even after a VSCode restart. I have no issue ignoring the AI results, but sometimes it takes a recognizable couple of seconds until the results are returned and that blocks me from keeping what I want to write in my scattered brain :)
Long story short:
option A: the docs are out of date and the features are not sponsor-only anymore.
option B: disabling the AI features does not work somehow
option C: some weird Copilot feature adds itself to Front Matter?
option D: a combination of these
According to [the docs](https://frontmatter.codes/docs/sponsor-features#front-matter-ai), if `frontMatter.sponsors.ai.enabled` is set to false, then all AI features should be disabled. I would also expect, not being a sponsor currently, to not receive these features by default. But when I create a new post via Dashboard > Create Content it loads a while and then offers me 5 titles via AI (Copilot) based on my typed title. Setting `enabled` to false does not result in my typed title being used immediately, it still loads the AI results, even after a VSCode restart. I have no issue ignoring the AI results, but sometimes it takes a recognizable couple of seconds until the results are returned and that blocks me from keeping what I want to write in my scattered brain :)
Long story short:
- option A: the docs are out of date and the features are not sponsor-only anymore.
- option B: disabling the AI features does not work somehow
- option C: some weird Copilot feature adds itself to Front Matter?
- option D: a combination of these
<!-- github-sync-id:3573498618 -->
Over time, this became obsolete with the integration of GitHub Copilot in VS Code.
For GitHub Copilot, it needs to introduce a new setting to disable the functionality, as it right now has it automatically activated if GitHub Copilot is available.
Some of the documentation needs to be updated.
option A: As AI became available for free with GH Copilot, it became obsolete.
option B: This is for the sponsored AI only, so it needs to be removed
option C: Correct, a new setting needs to be added, as GH Copilot came with a free offering. Before, you needed a paid license, so only to those instances, the options became available.
option D: yes
I hope this clarifies it a bit.
Over time, this became obsolete with the integration of GitHub Copilot in VS Code.
For GitHub Copilot, it needs to introduce a new setting to disable the functionality, as it right now has it automatically activated if GitHub Copilot is available.
Some of the documentation needs to be updated.
---
- option A: As AI became available for free with GH Copilot, it became obsolete.
- option B: This is for the sponsored AI only, so it needs to be removed
- option C: Correct, a new setting needs to be added, as GH Copilot came with a free offering. Before, you needed a paid license, so only to those instances, the options became available.
- option D: yes
---
I hope this clarifies it a bit.
<!-- github-comment-id:3480071858 -->
I liked Frontmatter CMS and used it for a couple of blogs, but do not use generative AI on those projects, and am worried if it is being shoehorned into this good extension. Please can this be avoided, or can we at least have a working OFF switch for that nonsense?
I liked Frontmatter CMS and used it for a couple of blogs, but do not use generative AI on those projects, and am worried if it is being shoehorned into this good extension. Please can this be avoided, or can we at least have a working OFF switch for that nonsense?
<!-- github-comment-id:3606683623 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
According to the docs, if
frontMatter.sponsors.ai.enabledis set to false, then all AI features should be disabled. I would also expect, not being a sponsor currently, to not receive these features by default. But when I create a new post via Dashboard > Create Content it loads a while and then offers me 5 titles via AI (Copilot) based on my typed title. Settingenabledto false does not result in my typed title being used immediately, it still loads the AI results, even after a VSCode restart. I have no issue ignoring the AI results, but sometimes it takes a recognizable couple of seconds until the results are returned and that blocks me from keeping what I want to write in my scattered brain :)Long story short:
Over time, this became obsolete with the integration of GitHub Copilot in VS Code.
For GitHub Copilot, it needs to introduce a new setting to disable the functionality, as it right now has it automatically activated if GitHub Copilot is available.
Some of the documentation needs to be updated.
I hope this clarifies it a bit.
I liked Frontmatter CMS and used it for a couple of blogs, but do not use generative AI on those projects, and am worried if it is being shoehorned into this good extension. Please can this be avoided, or can we at least have a working OFF switch for that nonsense?
Hi @biomassboilers, no, there are no plans to put AI in it to generate content.