{% extends "base.html" %}
{% import "macros.html" as m %}
{% block title %}Settings{% endblock %}
{% macro status(done) %}<span class="setup-status {{ 'done' if done else 'pending' }}">{{ 'done' if done else 'pending' }}</span>{% endmacro %}
{% macro step_errors(step) %}{% set errs = form_errors.get(step, {}) %}{% if errs %}<div class="errors"><ul>{% for msg in errs.values() %}<li>{{ msg }}</li>{% endfor %}</ul></div>{% endif %}{% endmacro %}
{% block content %}
<h1>Settings</h1>
<p class="small settings-toc">
  <a href="#you">You</a> &middot; <a href="#bcc">BCC capture</a> &middot; <a href="#calendar">Calendar</a> &middot;
  <a href="#backup">Backup</a> &middot; <a href="#appearance">Appearance</a> &middot; <a href="#fields">Fields</a> &middot; <a href="#messaging">Drafts</a> &middot; <a href="#enrichment">AI</a> &middot; <a href="#task-types">Task types</a> &middot; <a href="#outcomes">Outcomes</a> &middot;
  <a href="#schedule">Schedule</a> &middot; <a href="#access">Access</a> &middot; <a href="#support">Support Hermit</a> &middot; <a href="#about">About</a>
  &middot; <a href="/help/settings">Help</a>
</p>
<p class="small">{% if os_store %}Secrets are stored in <code>.secrets.toml</code> (mode 600) or {{ os_store_label }}, never in <code>config.toml</code>.{% if os_store == 'secret-service' %} A keyring is locked while you are logged out, so a daily import that runs then cannot read the password; keep it in <code>.secrets.toml</code> if the machine imports without you logged in.{% endif %}{% elif is_windows %}Secrets are stored in <code>.secrets.toml</code>, never in <code>config.toml</code>. They are plain text, readable only by your user account and never committed to git.{% else %}Secrets are stored in <code>.secrets.toml</code>, never in <code>config.toml</code>. No system keyring was found (install <code>libsecret-tools</code> and run a Secret Service such as GNOME Keyring or KWallet to use one), so they are plain text, readable only by your user account (mode 600) and never committed to git.{% endif %} Everything else is written to <code>config.toml</code>, comments kept.{% if setup_pending %} <a href="/">Skip for now</a>{% endif %}</p>

<section class="setup-step" id="you">
  <h2>You {{ status(state.you) }}</h2>
  {{ step_errors('you') }}
  <form method="post" action="/settings/you" class="record-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <label>Your name <input name="name" value="{{ you.name }}" required></label>
    <label>Addresses you send mail from (comma-separated; the first is your main address)
      <input name="addresses" value="{{ you.addresses }}" required></label>
    <button type="submit">Save</button>
  </form>
</section>

<section class="setup-step" id="bcc">
  <h2>BCC capture {{ status(state.bcc) }}</h2>
  <p class="small">How it works: when you write to a prospect, put a tracking address in BCC (or forward the thread to it later). Hermit CRM reads that mailbox over IMAP, matches each message to a company by the other person's address or domain, and logs it as an interaction. Mail you send or forward to someone at a domain no company has creates that company, named after the domain. Personal addresses and domains that fit more than one company wait on <a href="/#to-file">Home, under To file</a>. With Gmail, <code>you+crm@gmail.com</code> reaches your own inbox, so no second account is needed; a filter can file those messages out of the way.</p>
  {{ step_errors('bcc') }}
  <form method="post" action="/settings/bcc" class="record-form" id="bcc-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <label>Mail provider
      <select id="bcc-provider" aria-describedby="bcc-provider-note">
        <option value="">other (type the server yourself)</option>
        {% for key, p in mail_providers.items() %}<option value="{{ key }}" data-host="{{ p.imap_host }}"{% if bcc_form.imap_host == p.imap_host %} selected{% endif %}>{{ p.label }}</option>{% endfor %}
      </select>
    </label>
    {% for key, p in mail_providers.items() %}
    <p class="small provider-note{% if not p.works %} warning{% endif %}" data-provider="{{ key }}" id="{{ 'bcc-provider-note' if loop.first else '' }}"{% if bcc_form.imap_host != p.imap_host %} hidden{% endif %}>
      <strong>{{ p.label }}:</strong> {{ p.note }}{% if p.password_url %} <a href="{{ p.password_url }}" target="_blank" rel="noopener">Create the app password</a>.{% endif %}
    </p>
    {% endfor %}
    <label>BCC address <input name="address" value="{{ bcc_form.address }}" placeholder="you+crm@gmail.com"></label>
    <label>IMAP server <input name="imap_host" id="bcc-imap-host" value="{{ bcc_form.imap_host }}" placeholder="imap.gmail.com"></label>
    <label>App password <input type="password" name="password" value="" autocomplete="new-password" placeholder="{{ 'stored; leave empty to keep it' if state.bcc else '' }}"></label>
    {% if os_store %}<label class="inline"><input type="checkbox" name="keychain" value="1" checked style="display:inline;width:auto"> Store the password in {{ os_store_label }}</label>{% endif %}
    <button type="submit">Save</button>
  </form>
  {% if gmail_filter %}
  <p>Gmail filter (Settings → Filters → Create new filter): <code>{{ gmail_filter }}</code></p>
  <form method="post" action="/settings/bcc/test" class="inline">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <button type="submit">Test connection (dry run)</button>
  </form>
  {% endif %}
  <div class="bcc-status">
    <p class="small">Mail it cannot place waits on <a href="/#to-file">Home, under To file</a>.</p>
    {% if last_run %}
      {% if last_run.ok %}
        <p>Last import {{ last_run.at | replace('T', ' ') }}: {{ last_run.summary }}</p>
      {% else %}
        <p class="error">Last import {{ last_run.at | replace('T', ' ') }} failed: {{ last_run.error }}</p>
      {% endif %}
    {% else %}
      <p class="small">No import has run yet.</p>
    {% endif %}
    {% if inbox_alert and last_run and last_run.ok %}<p class="error">{{ inbox_alert }}</p>{% endif %}
    <form method="post" action="/bcc/import" class="inline"><button type="submit">Import now</button></form>
  </div>
</section>

<section class="setup-step" id="calendar">
  <h2>Calendar {{ status(state.calendar) }}</h2>
  <p class="small">Optional. The secret ICS address of your calendar (Google: Settings → your calendar → Integrate calendar → Secret address in iCal format). Treat it like a password.</p>
  {{ step_errors('calendar') }}
  <form method="post" action="/settings/calendar" class="record-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <label>Secret ICS address <input type="password" name="url" value="" autocomplete="off"></label>
    <button type="submit">Save and test (dry run)</button>
  </form>
  <div class="bcc-status">
    {% if calendar_last_run %}
      {% if calendar_last_run.ok %}
        <p>Last meeting import {{ calendar_last_run.at | replace('T', ' ') }}: {{ calendar_last_run.summary }}</p>
      {% else %}
        <p class="error">Last meeting import {{ calendar_last_run.at | replace('T', ' ') }} failed: {{ calendar_last_run.error }}</p>
      {% endif %}
    {% else %}
      <p class="small">No meeting import has run yet. Past meetings whose attendees match no company wait on <a href="/#to-file">Home, under To file</a>.</p>
    {% endif %}
    <form method="post" action="/calendar/import" class="inline"><input type="hidden" name="back" value="/settings"><button type="submit">Import meetings now</button></form>
  </div>
</section>

<section class="setup-step" id="backup">
  <h2>Backup {{ status(state.backup) }}</h2>
  {{ step_errors('backup') }}
  <h3>On this computer</h3>
  <p class="small">Every few minutes, to a repository outside this folder that can only grow: a reset, a deleted <code>.git</code> or a force-push loses nothing, and any version can be put back. <a href="/help/backups">How it works and how to roll back</a>.</p>
  {% set lb = local_backup %}
  <p class="{{ 'warning' if lb.level != 'ok' else 'small' }} local-backup-summary">
    {%- if lb.level == 'ok' and lb.age_minutes is not none -%}
      Last backup {{ 'just now' if lb.age_minutes < 1 else lb.age_minutes ~ ' min ago' }} ({{ lb.size }}).
    {%- elif not lb.last_ok -%}
      No backup yet.
    {%- else -%}
      {{ lb.summary }}
    {%- endif -%}
    {% if lb.last_ok and not schedule.backup_installed %} It does not repeat on its own yet.{% endif %}
  </p>
  {% if schedule.backup_elsewhere %}
  <p class="warning">This computer's backup job is set up for another folder, <code>{{ schedule.backup_elsewhere }}</code>; there is one per computer. To back up this folder instead, run <code>hermitcrm --data {{ about.data_dir }} schedule install</code>; that folder is then no longer backed up.</p>
  {% elif not schedule.backup_installed or not lb.last_ok %}
  <form method="post" action="/settings/backup/local" class="record-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <button type="submit">Start local backups</button>
    <span class="small">Makes a first backup now, then one every 5 minutes in the background.</span>
  </form>
  {% endif %}
  <details class="small">
    <summary>Where it is kept</summary>
    <p>In <code>{{ lb.dest }}</code>, outside your CRM folder, so deleting the folder does not delete the backup. To keep it somewhere else, such as another disk or a synced folder, set <code>backup_dir</code> in <code>config.toml</code>.</p>
    {% if lb.lines[1:] %}<ul class="schedule-lines">{% for line in lb.lines[1:] %}<li><code>{{ line }}</code></li>{% endfor %}</ul>{% endif %}
  </details>
  <h3>Online copy (optional){% if state.remote %} {{ status(true) }}{% endif %}</h3>
  <p class="small">The backup above lives on the same disk as your data. For a copy that survives a lost laptop, push the folder to a git remote after every change.</p>
  <p class="warning"><strong>The repository must be PRIVATE</strong> on GitHub, GitLab or Bitbucket: it holds your contacts and mail.</p>
  {% if remote_warning %}<p class="warning">{{ remote_warning }}</p>{% endif %}
  <form method="post" action="/settings/backup" class="record-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <label>Git remote URL <input name="url" value="{{ remote_url }}" placeholder="git@github.com:you/crm.git"></label>
    <button type="submit">Save and test push</button>
  </form>
</section>

<section class="setup-step" id="appearance">
  <h2>Appearance</h2>
  {{ step_errors('appearance') }}
  <form method="post" action="/settings/appearance" class="record-form theme-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <fieldset class="switch">
      <legend>Night mode</legend>
      {% for t, label in [('light', 'Off'), ('dark', 'On'), ('system', 'Follow the system')] %}
      <label><input type="radio" name="theme" value="{{ t }}"{% if t == theme %} checked{% endif %}> {{ label }}</label>
      {% endfor %}
    </fieldset>
    <button type="submit">Save</button>
  </form>
  <h3>Your own look</h3>
  {% if theme_file.active %}
  <p class="small theme-status"><strong>In use:</strong> <code>{{ theme_file.path }}</code>. It changes colours and fonts on top of the default. Delete the file to go back to the default look.</p>
  {% if theme_file.problems %}
  <ul class="small provider-note warning">
    {% for line, problem in theme_file.problems %}<li>Line {{ line }}: {{ problem }}</li>{% endfor %}
  </ul>
  {% endif %}
  {% else %}
  <p class="small theme-status"><strong>Not in use.</strong> To change colours or fonts, ask your AI tool to write <code>{{ theme_file.path }}</code>, for example "make my Hermit CRM blue". It is one block like the one below; <a href="/help/settings">Help > Settings</a> lists what you can change.</p>
  <pre class="small theme-example">{{ theme_example }}</pre>
  {% endif %}
</section>

<section class="setup-step" id="fields">
  <h2>Fields</h2>
  <p class="small">Fields of your own, on top of the ones Hermit CRM has. Their values live in the front matter of the record they belong to, like every other field, so nothing is hidden in a database. They are described in <code>fields.toml</code> next to your data.</p>
  {{ step_errors('fields') }}

  {% if custom_field_defs %}
  <div class="table-scroll"><table class="fields-list small">
    <tr><th>key</th><th>label</th><th>type</th><th>on</th><th>shown in</th></tr>
    {% for f in custom_field_defs %}
    <tr>
      <td><code>{{ f.key }}</code></td><td>{{ f.label }}</td><td>{{ f.type }}</td>
      <td>{{ f.applies_to }}</td><td>{{ f.show_in | join(', ') }}</td>
    </tr>
    {% endfor %}
  </table></div>
  {% else %}
  <p class="setup-status pending">No fields of your own yet.</p>
  {% endif %}

  <h3 class="small">Add one</h3>
  <form method="post" action="/settings/fields/add" class="record-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <div class="row">
      <label>key <input name="key" placeholder="segment" required></label>
      <label class="grow">label (empty: the key) <input name="label"></label>
      <label>type
        <select name="type">{% for t in field_types %}<option value="{{ t }}">{{ t }}</option>{% endfor %}</select>
      </label>
      <label>on
        <select name="applies_to">{% for sc in field_scopes %}<option value="{{ sc }}">{{ sc }}</option>{% endfor %}</select>
      </label>
    </div>
    <div class="row">
      <label class="grow">options, comma separated (select only) <input name="options" placeholder="smb, mid-market, enterprise"></label>
      <label class="grow">help text under the input <input name="help"></label>
    </div>
    <label class="inline"><input type="checkbox" name="messaging" value="on" checked> Outreach templates may use it as <code>{key}</code></label>
    <fieldset class="switch">
      <legend>Shown in</legend>
      {% for view in ['detail', 'board', 'companies', 'contacts', 'messages'] %}
      <label class="inline"><input type="checkbox" name="show_in" value="{{ view }}"{% if view == 'detail' %} checked{% endif %}> {{ view }}</label>
      {% endfor %}
    </fieldset>
    <p class="small">A field only appears where its record does: <code>board</code> and <code>companies</code> for a company field, <code>contacts</code> for a contact, <code>messages</code> for an interaction. Wherever it appears as a column it can be filtered and sorted like any other.</p>
    <button type="submit">Add field</button>
  </form>

  <h3 class="small">All of them at once</h3>
  <form method="post" action="/settings/fields" class="record-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <label class="grow">fields.toml <textarea name="fields_toml" rows="12" spellcheck="false">{{ fields_form.toml }}</textarea></label>
    <p class="small">This is the file itself, so what you save is what you are reading. Removing a field here stops Hermit CRM showing it; the values stay in your records untouched, and putting the field back brings them straight back.</p>
    <button type="submit">Save fields</button>
  </form>
</section>

<section class="setup-step" id="messaging">
  <h2>Drafts</h2>
  <p class="small">Every field of your own is a slot the outreach templates can use by name, written <code>{{ '{' }}key{{ '}' }}</code>; an empty one renders as its label in square brackets, the mark the templates already use for "only you can fill this in". Two of them can also play the roles the shipped wording knows about. See <a href="/help/messages">Messages</a>.</p>
  {{ step_errors('messaging') }}
  <form method="post" action="/settings/messaging" class="record-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <div class="row">
      <label>Headcount field
        <select name="size_field">
          <option value="">none</option>
          {% for k in company_field_keys %}<option value="{{ k }}"{% if messaging_form.size_field == k %} selected{% endif %}>{{ k }}</option>{% endfor %}
        </select>
      </label>
      <label>Sales-team-size field
        <select name="team_field">
          <option value="">none</option>
          {% for k in company_field_keys %}<option value="{{ k }}"{% if messaging_form.team_field == k %} selected{% endif %}>{{ k }}</option>{% endfor %}
        </select>
      </label>
    </div>
    <p class="small">With neither set, the sentences about team size use their "unknown" wording, which is a line you fill in yourself. Nothing is invented.</p>
    <button type="submit">Save</button>
  </form>
</section>

<section class="setup-step" id="enrichment">
  <h2>AI: Enrich and Ask the Hermit</h2>
  <p class="small">Enrich and Ask the Hermit use an AI CLI you already have. The Enrich button asks it for a company's or contact's empty fields; Ask the Hermit answers questions about the page you are on, then about the whole CRM. Provider <code>auto</code> takes the first of claude, codex, gemini, grok it finds; <code>custom</code> runs the command line below. "Fetch from URL" needs none of this.</p>
  {% if enrich_status.available %}
  <p class="setup-status done">In use: {{ enrich_status.provider }}</p>
  {% else %}
  <p class="setup-status pending">Unavailable: {{ enrich_status.reason }}</p>
  <p class="small">When Hermit CRM runs under launchd or systemd (<code>hermitcrm schedule install --serve</code>) it starts with a bare PATH: the CLI must be in <code>/usr/local/bin</code>, <code>/opt/homebrew/bin</code> or <code>~/.local/bin</code>, or give its full path as the command.</p>
  {% endif %}
  {{ step_errors('enrichment') }}
  <form method="post" action="/settings/enrichment" class="record-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <div class="row">
      <label>Provider
        <select name="provider">
          {% for p in enrich_providers %}<option value="{{ p }}"{% if p == enrich_form.provider %} selected{% endif %}>{{ p }}</option>{% endfor %}
        </select>
      </label>
      <label class="grow">Command (empty: the provider's own binary) <input name="command" value="{{ enrich_form.command }}" placeholder="/opt/homebrew/bin/claude"></label>
      <label>Timeout (seconds) <input name="timeout" value="{{ enrich_form.timeout }}" inputmode="numeric" size="6"></label>
    </div>
    <fieldset class="switch">
      <legend>Account</legend>
      <label><input type="radio" name="account" value="subscription"{% if enrich_form.account != 'api' %} checked{% endif %}> Subscription: signed in with a ChatGPT, Claude or Gemini plan</label>
      <label><input type="radio" name="account" value="api"{% if enrich_form.account == 'api' %} checked{% endif %}> API key</label>
    </fieldset>
    <p class="small">A subscription is not entitled to the same model ids as an API key, and asking for one it does not have fails outright rather than falling back. On a subscription, Hermit CRM asks for no particular model where that is known to matter, and the CLI answers on whatever your plan gets.</p>
    <fieldset class="switch">
      <legend>Model</legend>
      <label><input type="radio" name="tier" value="medium"{% if enrich_form.tier != 'strong' %} checked{% endif %}> Medium: {{ model_label(tier_models.medium) }}{% if tier_models.medium %} <code>{{ tier_models.medium }}</code>{% endif %} (default)</label>
      <label><input type="radio" name="tier" value="strong"{% if enrich_form.tier == 'strong' %} checked{% endif %}> Strong: {{ model_label(tier_models.strong) }}{% if tier_models.strong %} <code>{{ tier_models.strong }}</code>{% endif %}</label>
    </fieldset>
    <p class="small">{% if tier_models.strong %}Answers and enrich proposals made on the medium model offer "Retry with {{ model_label(tier_models.strong) }}". {% endif %}Override a model id when your CLI names it differently; an override is used whatever the account type.</p>
    <div class="row">
      <label>Medium model (empty: provider default) <input name="model" value="{{ enrich_form.model }}" placeholder="{{ tier_models.medium if not enrich_form.model else '' }}"></label>
      <label>Strong model (empty: provider default) <input name="model_strong" value="{{ enrich_form.model_strong }}" placeholder="{{ tier_models.strong if not enrich_form.model_strong else '' }}"></label>
    </div>
    <button type="submit">Save</button>
  </form>
</section>

<section class="setup-step" id="task-types">
  <h2>Task types</h2>
  <p class="small">Your own labels for tasks and next steps, e.g. <em>pipeline follow-up</em>, <em>prospecting</em>, <em>lost deals</em>. A type is a label and a filter; it changes no dates. Renaming a type renames it on every task that has it. Deleting one leaves it on its tasks, in grey.</p>
  {{ step_errors('task-types') }}
  <form method="post" action="/settings/task-types" class="record-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <table class="task-types">
      {% for t in task_types_form.rows %}
      <tr>
        <td><input name="name" value="{{ t.name }}" maxlength="40" aria-label="type name"><input type="hidden" name="old" value="{{ t.name }}"></td>
        <td><select name="colour" aria-label="colour">{% for p in palette %}<option value="{{ p }}"{% if p == t.colour %} selected{% endif %}>{{ p }}</option>{% endfor %}</select></td>
        <td>{{ m.type_chip(t.name) }}</td>
        <td class="actions">
          {% if not loop.first %}<button type="submit" name="move" value="{{ loop.index0 }}-up" title="Move up">Up</button>{% endif %}
          {% if not loop.last %}<button type="submit" name="move" value="{{ loop.index0 }}-down" title="Move down">Down</button>{% endif %}
          <button type="submit" name="delete" value="{{ loop.index0 }}" title="Remove this type">Delete</button>
        </td>
      </tr>
      {% endfor %}
      <tr>
        <td><input name="name" value="" maxlength="40" placeholder="new type" aria-label="new type name"><input type="hidden" name="old" value=""></td>
        <td><select name="colour" aria-label="colour">{% for p in palette %}<option value="{{ p }}">{{ p }}</option>{% endfor %}</select></td>
        <td></td><td></td>
      </tr>
    </table>
    <button type="submit">Save task types</button>
  </form>
</section>

<section class="setup-step" id="outcomes">
  <h2>Outcomes</h2>
  <p class="small">The outcome choices for an interaction, one per line, in order. The <strong>first</strong> is what a detected reply counts as; the <strong>last</strong> is what silence past the message window counts as. A sent message with no outcome and no reply is <em>unknown</em> until the window passes.</p>
  {{ step_errors('outcomes') }}
  <form method="post" action="/settings/outcomes" class="record-form">
    <input type="hidden" name="csrf_token" value="{{ csrf_token }}">
    <div class="row">
      <label class="grow">Outcomes (one per line) <textarea name="outcomes" rows="4">{{ outcomes_form.outcomes }}</textarea></label>
      <label>Message window (days) <input name="message_window_days" value="{{ outcomes_form.message_window_days }}" inputmode="numeric" size="6"></label>
      <label>Silent after (days) <input name="silent_days" value="{{ outcomes_form.silent_days }}" inputmode="numeric" size="6"></label>
    </div>
    <button type="submit">Save</button>
  </form>
</section>

<section class="setup-step" id="schedule">
  <h2>Schedule {{ status(schedule.installed) }}</h2>
  <p class="small">The daily job runs <code>hermitcrm sync --apply</code> (BCC, then calendar import). Read-only here; install or remove it from a terminal.</p>
  <ul class="schedule-lines">
    {% for line in schedule.lines %}<li><code>{{ line }}</code></li>{% endfor %}
  </ul>
  <p>Install (daily at 07:00; <code>--at HH:MM</code> changes the time, drop <code>--serve</code> to leave the web app to you):</p>
  <pre class="copy"><code>{{ schedule.install_command }}</code></pre>
</section>

<section class="setup-step" id="access">
  <h2>Access</h2>
  <p class="small">Two more ways into the same folder. Both start from a terminal, so this section is read-only.</p>

  <h3>From your phone</h3>
  <p>The app is bound to <code>{{ access.host }}</code>{% if not access.on_network %}, which only this machine can reach{% endif %}. Bind it to every interface and open the app on your phone over the same Wi-Fi:</p>
  <pre class="copy"><code>{{ access.serve_command }}</code></pre>
  <p>Then open <code>{{ access.lan_url }}</code> on the phone. To make it permanent, set <code>host = "0.0.0.0"</code> in <code>config.toml</code>.</p>
  <p class="warning">Hermit CRM has no password. Anyone who can reach that port can read and write your CRM, so use it on a network you trust, or a private one (Tailscale, WireGuard) rather than public Wi-Fi.</p>

  <h3>From an AI client (MCP)</h3>
  <p>Lets a desktop AI client on this machine &mdash; Claude Desktop, ChatGPT desktop, Cursor &mdash; read and write this CRM with no terminal: ask for your pipeline, what you owe a reply to, a brief before a meeting, and log the call afterwards. Seven read tools and three writes; the writes commit exactly as the web form does.</p>
  <pre class="copy"><code>{{ access.mcp_command }}</code></pre>
  <p>It speaks on stdin and stdout, so you do not run it yourself: paste this into your client's MCP config and it starts it for you. That also means the client must run on this machine &mdash; a phone app cannot reach it. For the phone, use the section above.</p>
  <pre class="copy"><code>{{ access.mcp_config }}</code></pre>
  <p class="small">Details and the full tool list: <a href="/help/ai-agents">AI agents</a>.</p>
</section>

<section class="setup-step" id="support">
  <h2>Support Hermit</h2>
  <p>Hermit CRM is free and open source, and stays that way. If it earns its place in your week, you can support its development with a tip on Ko-fi.</p>
  <p><a class="button" href="{{ support_url }}" target="_blank" rel="noopener">Support Hermit on Ko-fi</a></p>
  <p class="small">Opens <code>{{ support_url | replace('https://', '') }}</code> in your browser. Nothing in the app depends on it, and Hermit CRM sends nothing to Ko-fi.</p>
</section>

<section class="setup-step" id="about">
  <h2>About</h2>
  <table class="about">
    <tr><th>Version</th><td>Hermit CRM v{{ about.version }}{% if update_notice and update_notice.available %} &mdash; <span class="update-notice">v{{ update_notice.available }} available: <code>{{ update_notice.hint }}</code></span>{% elif about.update_note %} <span class="small">({{ about.update_note }})</span>{% endif %}</td></tr>
    <tr><th>Data folder</th><td><code>{{ about.data_dir }}</code></td></tr>
    <tr><th>Data format</th><td>{% if about.data_format is none %}unknown{% else %}{{ about.data_format }}{% if about.data_format != about.latest_format %} (this Hermit CRM writes {{ about.latest_format }}; run <code>hermitcrm migrate</code>){% endif %}{% endif %}</td></tr>
    <tr><th>Check the installation</th><td><code>hermitcrm --data {{ about.data_dir }} doctor</code> (add <code>--online</code> to try the IMAP login)</td></tr>
    <tr><th>Help</th><td><a href="/help">All help topics</a>, or <code>hermitcrm help</code></td></tr>
  </table>
</section>
<script>
// Picking a provider fills the server and shows how to get its app password.
// Plain progressive enhancement: without this, the server box is typed by hand.
(function () {
  var select = document.getElementById("bcc-provider");
  var host = document.getElementById("bcc-imap-host");
  if (!select || !host) return;
  select.addEventListener("change", function () {
    var chosen = select.options[select.selectedIndex];
    if (chosen.dataset.host) host.value = chosen.dataset.host;
    document.querySelectorAll(".provider-note").forEach(function (n) {
      n.hidden = n.dataset.provider !== select.value;
    });
  });
})();
</script>
{% endblock %}