V5 / CUSTOM SCENARIOS

Write a world
of your own.

User-authored XML examples for Lilith V5. These are website-only recipes, not files bundled with the application. Each example targets this specific version.

Only scenarios introduced in V5 are listed. Earlier additions are available under their version tabs.

WEBSITE EXAMPLEV5

A recurring break reminder

Create an hourly interval reminder while Lilith is running. It uses the scheduler’s normal coalescing and restart policy rather than replaying missed reminders after a shutdown.

stretch_breaksRead full XML ↗
WEBSITE EXAMPLEV5

A weekday greeting on a cron schedule

Schedule the saved greeting scenario at 09:00 Europe/London on weekdays. This defines the schedule; it does not run the greeting immediately. The bundled greeting.xml must remain available in the same trusted scenario catalog.

weekday_welcomeRead full XML ↗
WEBSITE EXAMPLEV5

Start a named focus timer

Create a 25-minute reminder through the V5 scheduler. Use a separate status command to check the remaining time or a cancellation command to stop it. No nested scenario or workspace write is performed.

Make the example yours.

These XML files are documentation downloads only. Reading or downloading one does not install it, execute it, or add it to the Lilith source archive.

Start with the bundled Scenarios directory from Lilith V5. Copy that matching catalog to a trusted editable folder and add your example XML alongside it. Keep the filename equal to its scenario ID.

Point LILITH_SCENARIOS_ROOT at that folder before starting Lilith. A custom root replaces the bundled catalog rather than merging with it, so keep the bundled files you still need, including greeting.xml for startup and scheduled greetings. Then ask Lilith to run the scenario by name and supply its required values.

Saved XML is trusted application content. Embedded C# executes with the host's permissions and requires the .NET SDK; it is not sandboxed. Workspace and scheduling operations keep their selected version's access and approval rules. Examples are authored against the documented contract; they are not live model execution guarantees.