Promptfire
unlistedby sudo-litigator
Compile and export structured vault context for AI workflows.
Promptfire
Structured vault context for repeatable AI workflows in Obsidian.
Compile notes, links, folders, metadata, and search results into deterministic prompts for ChatGPT, Claude, local models, and any other external AI tool.
Why Promptfire Exists
Promptfire is for people who already keep valuable context in Obsidian but do not want to rebuild that context by hand every time they use an AI tool.
Instead of repeatedly pasting style rules, active note content, linked notes, conventions, and background material into another app, Promptfire turns your vault into a reproducible prompt assembly system.
That gives you:
- repeatable prompts instead of one-off copy-paste sessions
- explicit control over what context is included and in what order
- budget-aware prompt construction for larger vaults
- model-agnostic exports that stay local to Obsidian until you decide where to send them
How It Works
- Define one or more profiles for different workflows.
- Choose context sources such as the active note, a folder, backlinks, or a search query.
- Apply extractors, filters, priorities, and budgets.
- Preview the compiled result and export it to the target you want.
Highlights
- Multiple named profiles for different AI workflows
- Source definitions for active note, single file, folder, outgoing links, backlinks, and search query
- Section extractors for full note, frontmatter only, body only, heading-filtered sections, and code blocks only
- Regex include and exclude filters per source
- Per-source priorities and character budgets
- Per-block budgets and global prompt budgets
- Output formats for Markdown, XML, and JSON
- Output targets for clipboard, new note, append to note, append to active note, scratchpad note, and deep link
- Interactive preview with source toggles, source reordering, block toggles, format switching, and recompile controls
- Snapshot workflows for saving preview state as a reusable profile
- Vault-native configuration via
.promptfire.json
Install
From GitHub Releases
- Download the latest release assets:
manifest.json,main.js, andstyles.css. - Create this folder inside your vault:
<vault>/.obsidian/plugins/promptfire/
- Copy the downloaded files into that folder.
- In Obsidian, open
Settings -> Community plugins. - Enable community plugins if needed, then enable
Promptfire.
From Source
npm install
npm run build
Copy manifest.json, main.js, and styles.css into <vault>/.obsidian/plugins/promptfire/, then enable the plugin in Obsidian.
Commands
Promptfire: Run default output target for active profilePromptfire: Preview context for active profilePromptfire: Run default output target for selected profilePromptfire: Preview context for selected profilePromptfire: Switch active profilePromptfire: Reload vault configPromptfire: Export resolved settings to vault config
If profile commands are enabled, Promptfire also registers profile-specific commands.
Search Query Syntax
search sources support field-aware, case-insensitive queries.
Supported patterns include:
- bare terms across path, filename, text, tags, headings, and frontmatter
path:guidesname:dailytext:"prompt engineering"tag:aiheading:conventionsfm:status=active- negation with
-, for example-name:draft
Example:
tag:ai path:guides "prompt engineering" -name:draft fm:status=active
Vault Config
If Enable vault config is enabled, Promptfire loads additional settings from a vault file, by default:
.promptfire.json
You can also export the resolved settings back into that file from the command palette or plugin settings.
Documentation Map
- Documentation index
- User guide
- Configuration reference
- Query syntax
- Examples
- Architecture
- Development guide
- Troubleshooting
- Contributing
- Support
- Release process
- Changelog
Development
npm install
npm run build
Watch mode:
npm run dev
For contributor expectations, local vault testing, and documentation update guidance, see CONTRIBUTING.md and docs/development.md.
Release Assets
This repository is prepared for GitHub release-based distribution. The standard shipped plugin assets are:
manifest.jsonmain.jsstyles.cssversions.json
versions.json remains in the repository for Obsidian release metadata and does not need to be copied into the vault during manual installation.
License
MIT
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.