Sybyl

Sybyl is an Obsidian plugin for solo tabletop play with provider-backed AI assistance and Lonelog-aware note formatting.

The plugin enforces a strict neutral, third-person, non-directive AI persona: it never narrates the player character, never uses second person, never invents lore. It is a referee tool, not a storyteller.

New to Sybyl? Start with the Tutorial — a step-by-step walkthrough from installation to your first scene.

For a complete reference of every command, frontmatter field, and provider option see USER_GUIDE.md.

Commands

• Start Scene — generates a scene opening
• Declare Action — interprets a declared action and dice outcome
• Ask Oracle — interprets oracle answers (yes/no, fate, or custom mode)
• Interpret Oracle Roll — narrates the meaning of a dice result
• What Now — suggests complications or consequences
• What Can I Do — lists available moves/actions given the current scene
• Expand Scene — expands the current scene into prose
• Ask the Rules — queries the active ruleset for rules clarifications
• Adventure Seed — generates a pre-session adventure premise
• Generate Character — generates a character concept
• Digest Source into Game Context — distils source documents into a compact game_context stored in frontmatter
• Insert Note Frontmatter — scaffolds a complete frontmatter block interactively
• Add/Manage Sources — manages source files attached to a note
• Update Scene Context — parses the Lonelog session log into scene_context
• New Session Header — inserts a Lonelog session break

Supported Providers

• Gemini
• OpenAI
• Anthropic (Claude)
• OpenRouter (free tier)
• Ollama (local)

How It Works

Sybyl works inside the active note. Each request is stateless and built from:

• note frontmatter (game, pc_name, game_context, scene_context, etc.)
• the current scene context
• the command-specific prompt

Source files are distilled once into a compact game_context block via the Digest Source into Game Context command. That result is reused on every subsequent request without per-request file overhead.

Development

npm ci
npm run check
npm run build

BRAT Release Flow

BRAT installs plugin builds from GitHub releases. The release job uploads:

• main.js
• manifest.json
• versions.json

To publish a BRAT-installable build:

1. Update manifest.json and package.json to the release version.
2. Update versions.json with the plugin version and minimum Obsidian version.
3. Commit and push to GitHub.
4. Create and push a matching tag, for example 0.2.0.

The release workflow verifies that the tag version matches manifest.json, builds the plugin, and attaches the release assets automatically.