Smart Templates settings

Smart Templates settings control two things:

1. where templates come from
2. how the shared request flow behaves

Core discovery settings

Templates folder

Use this when you want Smart Templates to scan one or more dedicated template folders.

Behavior:

• supports multiple folders
• if no folder is selected, Smart Templates falls back to the core Obsidian Templates folder when that plugin is configured

Naming convention

Use this when you want a specific filename to count as a template even outside the selected folders.

Behavior:

• .md is added automatically if missing
• matching filename is enough to detect the note as a template

Template headings

Use this when you want heading blocks to behave like templates.

Behavior:

• selected headings are matched against block keys
• lets you keep multiple templates inside one note

Pro-only settings

Generate model

This sets the default chat model used by Generate inside Smart Templates Pro.

Behavior:

• leave blank to use the Smart Environment default model
• can be overridden per request inside the modal

Primary action

This controls which action is used by shortcut flows inside the modal.

Behavior:

• choose Copy prompt or Generate
• does not remove the visible buttons
• mainly affects keyboard-driven flows like Mod+Select and Mod+Enter

Detection rules at a glance

Smart Templates currently detects templates from:

• configured folders
• Obsidian Templates folder fallback
• frontmatter flag smart template: true
• configured filename via template_name
• configured block headings via template_headings

Built-in defaults remain available even when no vault-backed template matches.