WEBSITE EXAMPLEV4
Capture a note in the workspace
Save supplied text to a root-level Markdown note. The application binds the exact path and content. This example can replace an existing note.
capture_noteRead full XML ↗
V4 / CUSTOM SCENARIOS
Write a world
of your own.
User-authored XML examples for Lilith V4. These are website-only recipes, not files bundled with the application. Each example targets this specific version.
V1 · 0 newV2 · 0 newV3 · 4 newV4 · 3 newV5 · 3 newV6 · 0 newV7 · 0 newV8 · 0 newV9 · 0 newV10 · 0 newV11 · 0 newV12 · 0 newV13 · 0 newV14 · 0 newV15 · 0 newV16 · 0 newV17 · 0 newV18 · 0 new
Only scenarios introduced in V4 are listed. Earlier additions are available under their version tabs.
WEBSITE EXAMPLEV4
Look through a project folder
List a chosen workspace folder with bounded results and have the main agent describe the available entries. The folder must already exist; this example does not create it or walk your personal folders.
project_listingRead full XML ↗
WEBSITE EXAMPLEV4
Summarize one saved excerpt
Read one bounded page of an existing UTF-8 workspace document and ask the main agent for a short summary. It never ingests the entire workspace or pretends a partial page is the complete document.
research_excerptRead full XML ↗
No scenarios match this search.
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 V4. 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.