Files
jobboard/app/templates/settings/agents.html
T
WolfandClaude Sonnet 5.5 001fc9002b Let the model report a verdict per must-have and cap career at 39 in code when one is broken
The judge numbers an agent's must-haves (one per line) and answers met, broken or unclear for each; career is stored as the model gave it and counts as at most BROKEN_CAP when a role is served, in cv_score, Store.judgement and the SQL of Best CV match. Migration 29 adds role_judgements.musts and broken; the judge's input_key carries a format version so earlier judgements are made again. The reader lists the must-haves with their verdicts and the cap.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-03 22:40:54 +02:00

156 lines
11 KiB
HTML

{% extends "settings/_layout.html" %}
{% block title %}Search agents — roledesk{% endblock %}
{# A card per agent: `static/agents.js` fills the list from `/api/agents`,
newest first. A card shows the agent's prompts, its rules in words, its
switch and its weights; Edit turns that card into the form below, in place, and New puts
a blank one on top. The form is a `<template>` because only one card edits
at a time, so its ids stay unique. #}
{% block content %}
<h1>Search agents</h1>
<p class="lede">A search agent is what the Roles tab ranks by: describe each kind of role you want as a prompt, say where, weigh the terms, and it scores every open role against the prompt each fits best. Several agents rank the same roles differently, each with its own votes and liked companies; Viewing as on Roles picks one, and its votes are that agent's.</p>
<div class="agents-head">
<p id="agents-count" class="count" role="status"></p>
<button type="button" id="a-new">New agent</button>
</div>
<div id="agents-list" class="agent-cards"></div>
<template id="agent-form-template">
<form id="agent-form" class="agent-form" autocomplete="off">
<h2 id="agent-form-title">New agent</h2>
<label>Name <input type="text" id="a-name" required placeholder="My search"></label>
<fieldset class="prompts">
<legend>What you are looking for</legend>
<div id="a-prompts" class="prompt-rows"></div>
<button type="button" id="a-add-prompt" class="secondary">Add prompt</button>
<span class="hint">A prompt is one kind of role in your own words: the work, the level, the setting. A role is ranked by the prompt it fits best, so three kinds of role are three prompts, not one blended paragraph. Votes and liked companies count for the whole agent.</span>
</fieldset>
<fieldset class="where">
<legend>Where can the role be?</legend>
<span class="hint">Each line adds places. A role is kept when it fits at least one line, so a line more means more roles, never fewer. With every line empty a role can be anywhere. A role whose location is not known yet ranks until extract reads the posting.</span>
<div class="where-line">
<span>Only roles in:</span>
<select id="a-scope" aria-label="Only roles in">
<option value="europe">Europe</option>
<option value="countries">Chosen countries</option>
<option value="everywhere">Everywhere</option>
</select>
<div id="a-scope-countries"></div>
</div>
<span class="hint">Every role must be in this, whatever the lines below add. A company set to All countries is read within this.</span>
<div class="where-line">
<span>Anywhere in</span>
<div id="a-countries"></div>
</div>
<div class="where-line">
<span>or in the towns</span>
<div id="a-towns"></div>
</div>
<span class="hint">Towns are for places outside the countries above: with Denmark above, Malmö here adds Malmö to all of Denmark. A town inside a country above changes nothing, since the whole country is in already.</span>
<div class="where-line">
<span>Remote:</span>
<select id="a-remote" aria-label="Remote">
<option value="none">no</option>
<option value="scope">anywhere within the scope</option>
<option value="from">only when open to someone in:</option>
</select>
<div id="a-remote-from"></div>
</div>
<span class="hint">Remote roles are kept on top of the lines above. A remote role whose area is not stated yet ranks until extract reads the posting.</span>
<label class="inline where-rank"><input type="checkbox" id="a-hybrid"> Prefer hybrid<span id="a-hybrid-weight-line">, adding <input type="number" id="a-hybrid-weight" min="0" step="0.05" value="0.05" aria-label="Weight of hybrid"></span></label>
<span class="hint">This one ranks rather than filters: a hybrid role gains a little.</span>
<p id="a-where-sum" class="where-sum" role="status"></p>
</fieldset>
<fieldset class="titles">
<legend>Which titles to leave out?</legend>
<div class="where-line">
<span>Leave out titles with</span>
<div id="a-titles"></div>
</div>
<span class="hint">Separate phrases with a comma or Enter. A phrase matches whole words anywhere in the title, whatever the case: <code>account executive</code> takes "Enterprise Account Executive, UK", and <code>data engineer</code> leaves "Data Engineering Manager" alone. A shorter phrase takes more: <code>sales</code> takes Sales Engineer too. It applies to liked companies as well. A role left out keeps its row, and Show gated on Roles lists it with the phrase that took it.</span>
</fieldset>
<fieldset class="terms">
<legend>What big boards send</legend>
<div class="where-line">
<span>Only roles matching</span>
<div id="a-terms"></div>
</div>
<span class="hint">Separate terms with a comma or Enter: <code>machine learning, data science</code> is two terms, and <code>machine learning</code> is searched as one. A board then sends only roles with one of the terms anywhere in the ad, not only the title. Only applies to big boards read across Europe (All countries). Empty means no narrowing.</span>
</fieldset>
<fieldset class="terms cv">
<legend>Your CV</legend>
<span class="hint">Optional. With a CV, the judge stage reads each of this agent's best roles against it and scores skills, experience and career, which Best CV match on Roles sorts by. A role is read at most once per change of the CV, the prompts or the texts below. The CV stays in this app and goes only to the model you set up.</span>
<label>CV
<textarea id="a-cv-text" rows="10" placeholder="Paste your CV or career summary here"></textarea></label>
<label>or read it from a file
<input type="file" id="a-cv-file" accept=".md,.txt,text/plain,text/markdown"></label>
<span class="hint">A .md or .txt file replaces the text above. Nothing is uploaded: the browser reads it into the box.</span>
<div class="where-line">
<span>Languages you speak</span>
</div>
<div id="a-cv-languages" class="rule-rows"></div>
<button type="button" id="a-add-language" class="secondary">Add language</button>
<button type="button" id="a-suggest-languages" class="secondary">Suggest languages</button>
<span class="hint">A two-letter code such as <code>en</code> or <code>da</code>, and how well. Roles that ask for a language you lack, or a level above yours, get a warning on Roles; a role that names one of yours as a plus gets a star. With none, no role is flagged. Suggest languages reads them from the CV with one model call and replaces the rows above; nothing is saved until Save.</span>
<label>Avoid / drains me
<textarea id="a-avoid-text" rows="4" placeholder="Constant on-call, sales targets, large consultancies, open-plan offices"></textarea></label>
<label>Must-haves and deal-breakers
<textarea id="a-must-text" rows="4" placeholder="Permanent contract&#10;A say in the roadmap&#10;At most one day a week in the office"></textarea></label>
<span class="hint">One must-have per line. The judge reports for each whether a posting meets it, clearly breaks it or does not say; a broken one caps the role's career score at 39 in code, whatever the model scored. Rules that must hold go under Where or Other rules instead.</span>
</fieldset>
<fieldset class="weights">
<legend>How much each counts</legend>
<label>Fit to the text <input type="number" id="a-fit" min="0" step="0.05" value="0.6"></label>
<label>Newness <input type="number" id="a-recency" min="0" step="0.05" value="0.2"></label>
<label>Companies you like <input type="number" id="a-affinity" min="0" step="0.05" value="0.2"></label>
<label>Roles you liked <input type="number" id="a-taste" min="0" step="0.05" value="0.2"></label>
</fieldset>
<fieldset class="weights">
<legend>How much each counts in the CV match</legend>
<label>Skills <input type="number" id="a-cv-skills" min="0" step="5" value="30"></label>
<label>Experience <input type="number" id="a-cv-experience" min="0" step="5" value="25"></label>
<label>Career <input type="number" id="a-cv-career" min="0" step="5" value="30"></label>
</fieldset>
<span class="hint">The judge's three numbers are averaged with these shares into the CV match. Changing them re-sorts at once and asks the model for nothing; 0 leaves a number out, all three 0 means no CV match.</span>
<fieldset class="weights limits">
<legend>What the model reads</legend>
<label>Extract the best <input type="number" id="a-extract-top" min="0" step="10" value="500"></label>
<label>down to a score of <input type="number" id="a-extract-min" min="0" max="1" step="0.05" value="0.55"></label>
<label>Summarise the best <input type="number" id="a-summarise-top" min="0" step="5" value="30"></label>
<label>down to a score of <input type="number" id="a-summarise-min" min="0" max="1" step="0.05" value="0.65"></label>
<label>Judge against the CV the best <input type="number" id="a-judge-top" min="0" step="10" value="150"></label>
<label>down to a score of <input type="number" id="a-judge-min" min="0" max="1" step="0.05" value="0.55"></label>
</fieldset>
<span class="hint">Every pull scores every open role for free; these bound what the model then reads, per agent. The count is the backstop, the score the real stop. Fit is a level, the same in every run: a new role with the worst fit scores about 0.27, a perfect one about 0.87. An agent with no prompt feeds neither extract nor summarise, and one with no CV feeds not the judge.</span>
<details class="advanced">
<summary>Advanced</summary>
<div class="advanced-body">
<fieldset class="rules">
<legend>Other rules</legend>
<div id="a-rules" class="rule-rows"></div>
<button type="button" id="a-add-rule" class="secondary">Add rule</button>
<span class="hint">Must: a role must meet it. One of: a role must meet one of these or a Where line. Prefer: a role that meets it gains the weight. Values are separated by commas; salary is a number.</span>
</fieldset>
<label>Rules as sent
<textarea id="a-gates" class="code" rows="6" spellcheck="false" readonly>[]</textarea>
<span class="hint">Read only: what Save sends as the agent's gates, from Where and Other rules.</span></label>
</div>
</details>
<div class="agent-actions">
<button type="submit">Save and score</button>
<button type="button" id="a-cancel" class="secondary">Cancel</button>
<button type="button" id="a-delete" class="secondary">Delete</button>
</div>
</form>
</template>
{% endblock %}
{% block scripts %}
{# chips.css only adds to app.css; base.html has no head block for it. #}
<link rel="stylesheet" href="{{ asset('chips.css') }}">
<script src="{{ asset('chips.js') }}"></script>
<script src="{{ asset('remote.js') }}"></script>
<script src="{{ asset('agents.js') }}"></script>
{% endblock %}