rune/oai-web
1
0
Fork 0
Code Issues Pull Requests Packages Releases 1 Wiki Activity

Changes, bugfixes and updates to the matrix. Added 1.2v batteries

Browse Source
This commit is contained in:
Rune Olsen
2026-04-13 12:45:50 +02:00
parent beef23d48e
commit 7b140d4079
10 changed files with 179 additions and 62 deletions
Download Patch File Download Diff File Expand all files Collapse all files

51
server/web/templates/help.html
View File

@@ -34,6 +34,12 @@
<li><a href="#agents-subagents">Sub-agents</a></li>
</ul>
</li>
<li><a href="#monitors">Monitors</a>
<ul>
<li><a href="#monitors-pages">Page Watchers</a></li>
<li><a href="#monitors-rss">RSS Feeds</a></li>
</ul>
</li>
<li><a href="#mcp">MCP Servers</a></li>
<li>
<a href="#settings">Settings</a>
@@ -298,6 +304,51 @@
</p>
</section>
<!-- ── 5. Monitors ───────────────────────────────────────────────── -->
<section id="monitors" data-section>
<h1>Monitors</h1>
<p>
The <a href="/monitors">Monitors</a> page lets you watch web pages and RSS feeds for changes, then automatically dispatch an agent or send a Pushover notification when something new appears. Monitors run on a schedule in the background — no manual checking needed.
</p>
<h2 id="monitors-pages">Page Watchers</h2>
<p>
A page watcher fetches a URL on a schedule, hashes the content (or a CSS-selected portion of it), and triggers an action when the content changes.
</p>
<p>Fields when creating a page watcher:</p>
<ul>
<li><strong>Name</strong> — displayed in the monitor list</li>
<li><strong>URL</strong> — the page to watch</li>
<li><strong>Schedule</strong> — cron expression (e.g. <code>0 * * * *</code> = every hour)</li>
<li><strong>CSS Selector</strong> — optional; restricts the hash to a specific element on the page (e.g. <code>#price</code> or <code>.headline</code>). Leave blank to watch the entire page.</li>
<li><strong>Agent</strong> — agent to dispatch when a change is detected</li>
<li><strong>Notification mode</strong> — <code>agent</code> (dispatch the agent), <code>pushover</code> (send a push notification), or <code>both</code></li>
</ul>
<p>
The table shows <strong>Last checked</strong> and <strong>Last changed</strong> timestamps. Use the <strong>Check now</strong> button to force an immediate check outside the schedule.
</p>
<p class="help-note">
Page watchers use plain HTTP (not a real browser). For JavaScript-heavy pages where the interesting content is rendered client-side, the CSS selector approach may not work — the agent's browser tool is better suited for those.
</p>
<h2 id="monitors-rss">RSS Feeds</h2>
<p>
An RSS feed monitor fetches a feed on a schedule and triggers an action for each new item since the last run.
</p>
<p>Fields when creating an RSS monitor:</p>
<ul>
<li><strong>Name</strong> — displayed in the monitor list</li>
<li><strong>Feed URL</strong> — any RSS or Atom feed URL</li>
<li><strong>Schedule</strong> — cron expression (e.g. <code>0 */4 * * *</code> = every 4 hours)</li>
<li><strong>Agent</strong> — agent to dispatch for new items</li>
<li><strong>Max items per run</strong> — cap on how many new items trigger the agent in one run (default: 5)</li>
<li><strong>Notification mode</strong> — <code>agent</code>, <code>pushover</code>, or <code>both</code></li>
</ul>
<p>
Already-seen item IDs are tracked so the same item never triggers twice. The monitor sends <code>ETag</code> / <code>If-Modified-Since</code> headers to avoid downloading unchanged feeds unnecessarily. Use the <strong>Fetch now</strong> button to force an immediate run.
</p>
</section>
<!-- ── 5. MCP Servers ─────────────────────────────────────────────── -->
<section id="mcp" data-section>
<h1>MCP Servers</h1>