{% extends "base.html" %} {% from "_macros.html" import icon %} {# What a folder hands to the chats started inside it. A page rather than a panel in the sidebar, following the admin convention: compact rows, and the full form one click away. A form per folder row in a tree that nests eight deep would be unusable, and the sidebar is the one place in the application that has to stay scannable. The whole form is one PATCH at the route that already existed. Every field is clearable, because `update_folder` reads the raw form and checks key presence rather than declaring `Form(None)` parameters -- with those, an empty box and an absent one are the same request. #} {% block title %}{{ folder.name }} - LLeMbas{% endblock %} {% block head %} {% endblock %} {% block body_attrs %} data-authenticated="true"{% endblock %} {% block body %}
{% include "partials/sidebar.html" %}

{{ icon("folder", "icon--sm") }} {{ folder.name }}

{{ icon("plus", "icon--sm") }} New chat here

Name

For you, not for any model. It is never sent anywhere.

System prompt

Used by every chat in this folder, and by folders nested inside it, unless the chat has a prompt of its own. Read each time a reply is built rather than copied when a chat is made, so editing this reaches the chats already here.

Precedence, not concatenation: chat, then folder, then model, then instance. The most specific one wins outright.

What a new chat starts as

Seeds, copied onto a chat when it is created and its own from then on. Anything chosen on the new-chat screen wins over these.

A folder set to one kind shows on only that side of the sidebar's switch, and opens the new-chat screen already on that fork.

{% if agent_profiles %} {# Only meaningful for an agent chat, and shown regardless of the kind above: somebody filling this in is on their way to setting the kind too, and a field that appears only once another field is right is a field people conclude is missing. #}
{% if agent_modes %}
{% endif %} {% endif %}
Back
{% endblock %}