Repository navigation
[Bug]: mdBase-tasknotes cli is not recognizing my configuration in the plugin of identifying tasks #1618
Description
Bug Description
I have configured the plugin to use the property type = Tasks to identify tasks. The CLI is writing type: task (lowercase singular) while the plugin uses type: Tasks (capitalized plural).
The _types/task.md config has default: Tasks for the type field, but the CLI is ignoring that default and writing task (the type definition name) instead.
I believe that the mdbase definition requires all lower case fields for the type property. My config proceeded that spec. If I need to change it, I will, but I still think it's an error not to flag the problem.
It also created two instances of the _type folder and task.md file in my Obsidian vault. One is in the root of the vault and the other is under the TaskNotes folder. Could this be the source of the problem?
Activity
jimbo108108 commentedon Feb 17, 2026
Here's what Claude code reported after I found the two instances of the _type and tasks.md:
What we fixed:
Removed the nested mdbase.yaml and _types/ from inside TaskNotes/ (created by our earlier mtn init). These were conflicting with the plugin-generated config at the vault root.
Updated the default collection path to point to the vault root
The CLI now correctly uses the plugin's _types/task.md config
What's still broken:
The CLI only finds tasks that don't have type: Tasks in frontmatter. All 122 existing tasks have type: Tasks, so the list command can't see them.
The test task the CLI created had type: task (lowercase), confirming the mismatch you reported to the developer.
This is worth including in your report — the CLI ignores files where the type frontmatter value doesn't match the type definition name (case-sensitive: Tasks vs task). We're blocked on this until the developer responds.
callumalpass commentedon Feb 17, 2026
Thanks for reporting this, @jimbo108108 . I'll be pushing a fix for this in the next release (hopefully in the next few hours).
test: add skipped reproduction for issue #1618 mdbase type mismatch
jimbo108108 commentedon Feb 17, 2026
Happy to help. You're doing great work.
Another issue: The CLI also wrote title in frontmatter, which existing tasks don't have,
callumalpass commentedon May 19, 2026
Thanks for reporting this. This appears to be fixed already.
The plugin-generated mdbase type definition now follows the configured TaskNotes task-identification settings, including property/value matching such as
type: Tasks; that fix was included in the 4.4.0 release notes for this issue. The existing mdbase spec tests for property-identification matching pass on the current development build. The follow-up about API/CLI-created tasks writingtitlefrontmatter when "Store title in filename" is enabled is also covered by the current fix for #1623.This looks fixed. If
mdbase-tasknotesstill cannot see existing tasks with the latest CLI package and a single vault-rootmdbase.yaml/_types/task.md, the cleanest next step would be a new CLI-specific issue with the generated schema files and one example task note.