Files
LLeMbas/src/lembas/web/templates/agents/index.html
T
HomerandClaude Opus 5 a16510aba8 The interface speaks Slovak
969 strings, an instance default and a per-person choice, and no half-done corner:
the admin prose is translated too. Design and reasoning: LLeMbas.wiki/Translations.

KEYED BY THE ENGLISH SENTENCE

A missing entry renders the key, which is the English -- so an untranslated string
looks as it always did, an English instance is byte-for-byte 1.6.0, and a
half-finished catalogue is a half-translated page rather than a page of dotted key
names. The cost is that editing an English sentence orphans its translation
silently, which is what tests/test_translations.py asserts in both directions.

No gettext: .po -> .mo is a build step and this project does not have one.

A JINJA GLOBAL, AND THEREFORE A CONTEXTVAR

`t()` is a global for the reason `brand` already documents -- render() is bypassed
by 25 TemplateResponse calls and 8 get_template().render() calls, the latter being
the SSE frames, which have no Request at all. A global is bound once at import and
the language is per person, so the active language is a ContextVar set per request.

🚨 `get_current_user` had to become `async def`. FastAPI runs a sync dependency in a
threadpool, and anyio copies the context in and discards it on the way out -- so
the language was set where nothing could see it and every page rendered in the
instance's language whatever anybody had chosen, with no error anywhere.

NOT TRANSLATED, ON PURPOSE

Everything a model reads: the 60 prompt fragments, and the dates in harness.py,
schedule/runner.py and schedule/compile.py. Only `i18n.stamp` is localised, and
only where a person reads it -- with the *format* translatable as well as the
words, because "26. septembra 2026" is a different pattern rather than the same one
with different words in it. A process locale is not an option: global, not
thread-safe, two people's pages at once.

A second fragment telling models to answer in the reader's language was written
during this work and removed: `core.style` has said it since long before, and
test_an_empty_override_turns_a_fragment_off caught the duplicate.

THE BULK PASS

1213 sites wrapped by a one-off script that only touched patterns it could not
misread. It got three wrong in a way that mattered -- `t('…')` inside `attr="…"`
where the sentence held an apostrophe, closing the Jinja string and 500ing two
pages whose partials no test renders. tests/test_translations.py now compiles all
110 templates. It also wrapped the product's own name, an SSH key header, a
keystroke hint and an example URL, all taken back out: a string is not
translatable just because it is a string.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-26 14:46:33 +00:00

100 lines
3.7 KiB
HTML

{% extends "agents/_layout.html" %}
{% from "_macros.html" import icon %}
{% block title %}Connections - {{ brand.name }}{% endblock %}
{% block heading %}Connections{% endblock %}
{% block actions %}
<a class="btn btn--primary btn--sm" href="/agents/new">
{{ icon("plus", "icon--sm") }} Add a connection
</a>
{% endblock %}
{% block agents_content %}
<p class="admin-lede">
Machines an <strong>{{ t("Agent") }}</strong> chat can work on. A model with one of these
can read files, write files and run commands <em>{{ t("there") }}</em> — never here.
Which of those it may do without asking you first is the chat's mode.
</p>
<div class="alert">
{{ icon("shield", "icon--sm") }}
<span>
Whatever this connection can reach, a model in an agent chat can reach. A
container built for the job, with one project mounted into it, is a very
different thing from a key to a machine you care about — and {{ brand.name }} cannot
tell them apart.
</span>
</div>
{% if problem %}
<div class="alert alert--error">
{{ icon("warning", "icon--sm") }} <span>{{ problem }}</span>
</div>
{% elif not enabled %}
<div class="alert alert--error">
{{ icon("warning", "icon--sm") }}
<span>{{ t("Agent chats are switched off for this instance. You can still add connections here, but nothing will use them until an administrator turns them on.") }}</span>
</div>
{% endif %}
{% if saved %}
<div class="alert alert--success">{{ icon("check", "icon--sm") }} <span>{{ saved }}</span></div>
{% endif %}
{% if not profiles %}
<div class="empty">
{{ icon("server", "empty__mark") }}
<h2 class="empty__title">{{ t("No connections yet") }}</h2>
<p class="empty__text">
Add the host, the user to log in as, and a key or password. Then press
<strong>{{ t("Check") }}</strong> — you will be shown its fingerprint to confirm before
anything is sent to it.
</p>
<a class="btn btn--primary" href="/agents/new">
{{ icon("plus", "icon--sm") }} Add a connection
</a>
</div>
{% else %}
<div class="model-rows">
{% for profile in profiles %}
{# `refused` is why this connection cannot be used at all, which is a stronger
statement than `disabled` -- that one is the owner's own choice and this one
is not theirs to make. Greyed out with the same class, because "you cannot
use this" is one visual idea however it came about. #}
{% set refused = refusals.get(profile.id, "") %}
<div class="model-row {{ 'is-off' if not profile.enabled or refused }}">
<div class="model-row__main">
<div class="model-row__title">
<a class="model-row__name" href="/agents/{{ profile.id }}">{{ profile.name }}</a>
{% if refused %}
<span class="badge badge--danger">{{ t("not allowed") }}</span>
{% elif profile.verified %}
<span class="badge badge--leaf">{{ t("key confirmed") }}</span>
{% else %}
<span class="badge badge--danger">{{ t("not checked") }}</span>
{% endif %}
{% if not profile.enabled %}<span class="badge">{{ t("disabled") }}</span>{% endif %}
{% if profile.auth == "password" %}<span class="badge">{{ t("password") }}</span>{% endif %}
</div>
<code class="model-row__id">
{{ profile.address }}{% if profile.default_dir %} · {{ profile.default_dir }}{% endif %}
</code>
{% if refused %}
<p class="text-xs danger">{{ refused }}</p>
{% elif profile.last_error %}
<p class="text-xs danger">{{ profile.last_error }}</p>
{% elif profile.server_info.system %}
<p class="text-xs faint">{{ profile.server_info.system }}</p>
{% endif %}
</div>
<div class="model-row__actions">
<a class="btn btn--sm" href="/agents/{{ profile.id }}">Open</a>
</div>
</div>
{% endfor %}
</div>
{% endif %}
{% endblock %}