Create Fatebook predictions directly within Obsidian and preview them via hover tooltips.
- Create new Fatebook predictions without leaving Obsidian
- Hover over Fatebook links to preview predictions
- Automatic markdown link generation for easy sharing
This plugin is not available in the Obsidian Community Plugins store. To install:
- Open Terminal/Command Prompt
- Navigate to your vault's plugin directory:
cd /path/to/vault/.obsidian/plugins - Clone this repository (requires Git):
git clone https://github.com/GarretteBaker/obsidian-fatebook.git fatebook-predictions
- Enter the plugin directory:
cd fatebook-predictions - Install dependencies and build (requires Node.js and npm):
npm install npm run build
- Restart Obsidian
- Enable the plugin in Settings → Community plugins
- Get your Fatebook API key from fatebook.io
- Open Obsidian Settings
- Go to "Fatebook Predictions" settings tab
- Enter your API key
- Use the command palette (Ctrl/Cmd + P) and search for "Create New Prediction"
- Fill in:
- Question: What you're predicting
- Forecast: Your probability estimate (0-1)
- Resolve By: Resolution date (YYYY-MM-DD)
- Click "Create Prediction"
- A markdown link will be copied to your clipboard
Hover over any Fatebook link to see a preview of the prediction.
- Open Terminal/Command Prompt and navigate to the plugin directory:
cd /path/to/vault/.obsidian/plugins/fatebook-predictions - Pull the latest changes (requires Git):
git pull
- Install dependencies and rebuild (requires Node.js and npm):
npm install npm run build
- Restart Obsidian
To work on the plugin:
- Clone as described in Installation
npm run devto start compilation in watch mode
- Windows: Download and install from git-scm.com
- macOS: Install via Homebrew with
brew install git - Linux: Use your package manager (e.g.,
apt install giton Ubuntu)
- Download Node.js from nodejs.org
- Choose the LTS (Long Term Support) version
- npm is included with Node.js
- Verify installation:
node --version npm --version
If you encounter issues or have feature requests, please open an issue on GitHub.