{% extends "base.html" %} {% block title %}{{ me.name }} — CareAgents{% endblock %} {% block bodyclass %}page-chat{% endblock %} {% block content %}
{{ me.name }}
{# Someone the holder cares for is always named here (one assistant per person spec, section 5). The holder's own chat says nothing. #} {% if whose %}
{{ whose }}
{% endif %}
{# One quiet menu, not three pills and a persona label: a first-timer at 375px read five things before the first question (2026-10 patient walk). A
, so it opens without script. #}
⋯
{# Sample records only: one plain line above the log, sticky, and written onto this tag so a real chat page renders byte for byte as before. Every sample answer opens with the same line (worker); this page shows it here only, so a bubble drops that leading copy (beta.under_banner, chat.js withoutFrame). #}{% if sample_line %}

{{ sample_line }}

{% endif %} {# Opened from a texted chart link (?chart=): the history stays hidden until chat.js has drawn the chart and scrolled to it, so the page does not paint at the top of the history first. #} {# One block for every first visit, built in app.py chat: intake first, then the taps the records can answer (labs only when some are known to be there), each naming someone the holder cares for by relationship (FHI-44). Just above the message box, outside the scrolling log, so all of them show on a short phone screen (patient tester recheck on #944). A returning visit has it hidden: chat.js shows it after an error, so the next try is one tap. A visit whose last turn failed keeps it shown, the same way. #}
{% for s in starters %} {% endfor %}
{# Made-up records answered; this account may connect its own (app.py _chat_connect_next). "after": chat.js shows it once an answer is done. #} {% if connect_next %}

Ready for your own records? {% if link_session %}Sign in again to connect your records{% else %}Connect your records{% endif %}

{% endif %}

Something confusing? Tell us.

{% endblock %}