https://funday.gg/dev/docs/agents/Recent content in Agents on Funday Dev DocsHugoen-usWed, 10 Jun 2026 00:00:00 -0700https://funday.gg/dev/docs/agents/hermes-setup/Mon, 01 Jan 0001 00:00:00 +0000https://funday.gg/dev/docs/agents/hermes-setup/<h1 id="-hermes-agent-setup">🪽 Hermes Agent Setup<a class="anchor" href="#-hermes-agent-setup">#</a></h1> <h2 id="installation">Installation<a class="anchor" href="#installation">#</a></h2> <p>Hermes was installed on <code>2026-05-17</code> using the official NousResearch installer:</p> <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash</span></span></code></pre></div><p><strong>Version</strong>: <code>v0.14.0 (2026.5.16)</code></p> <h2 id="configuration">Configuration<a class="anchor" href="#configuration">#</a></h2> <h3 id="llm-provider-openrouter">LLM Provider: OpenRouter<a class="anchor" href="#llm-provider-openrouter">#</a></h3> <p>Hermes uses <strong>OpenRouter</strong> as its LLM provider, giving access to 200+ models through a single API.</p> <table> <thead> <tr> <th style="text-align: left">Setting</th> <th style="text-align: left">Value</th> </tr> </thead> <tbody> <tr> <td style="text-align: left">Provider</td> <td style="text-align: left">OpenRouter</td> </tr> <tr> <td style="text-align: left">Default Model</td> <td style="text-align: left"><code>anthropic/claude-sonnet-4</code></td> </tr> <tr> <td style="text-align: left">Vision</td> <td style="text-align: left"><code>google/gemini-flash-1.5</code> (cost-optimized)</td> </tr> <tr> <td style="text-align: left">Compression</td> <td style="text-align: left"><code>meta-llama/llama-3.1-8b-instruct</code> (cheap)</td> </tr> <tr> <td style="text-align: left">Web Extract</td> <td style="text-align: left"><code>google/gemini-flash-1.5</code></td> </tr> </tbody> </table> <h3 id="subagent-delegation">Subagent Delegation<a class="anchor" href="#subagent-delegation">#</a></h3> <p>Hermes delegates complex tasks to isolated subagents:</p> <ul> <li><strong>Max concurrent</strong>: 5</li> <li><strong>Max depth</strong>: 2 (subagents can spawn sub-subagents)</li> <li><strong>Timeout</strong>: 900s per child</li> <li><strong>Auto-approve</strong>: Enabled</li> </ul> <h3 id="discord-gateway">Discord Gateway<a class="anchor" href="#discord-gateway">#</a></h3> <p>Hermes lives in Discord as a persistent bot:</p>https://funday.gg/dev/docs/agents/discord-thread-dashboard-plan/Fri, 22 May 2026 00:00:00 -0700https://funday.gg/dev/docs/agents/discord-thread-dashboard-plan/<h1 id="discord-thread-dashboard--implementation-plan">Discord Thread Dashboard — Implementation Plan<a class="anchor" href="#discord-thread-dashboard--implementation-plan">#</a></h1> <blockquote class='book-hint '> <p><strong>Status:</strong> Planned (not implemented)<br> <strong>Last updated:</strong> 2026-05-22<br> <strong>Audience:</strong> Funday devs and agents maintaining Hermes on Discord<br> <strong>Hermes tree:</strong> <code>~/.hermes/hermes-agent/</code> (upstream: NousResearch/hermes-agent)</p> </blockquote><p>This document captures the design for a <strong>hook-driven embed dashboard</strong> in Discord: when Hermes auto-creates a thread and adds 👀 on the user&rsquo;s message, a separate <strong>embed message</strong> in the thread acts as a live status panel (edited on each agent step, finalized on completion).</p>https://funday.gg/dev/docs/agents/hermes-kanban-swarm/Mon, 01 Jan 0001 00:00:00 +0000https://funday.gg/dev/docs/agents/hermes-kanban-swarm/<h1 id="-hermes-kanban-swarm">🐝 Hermes Kanban Swarm<a class="anchor" href="#-hermes-kanban-swarm">#</a></h1> <p>Ultra-condensed quick-start for turning broad Funday goals into a <strong>persistent, delegated, evidence-gated agent swarm</strong>.</p> <blockquote class='book-hint '> <p><strong>Golden rule:</strong> Hermes orchestrates. Kanban remembers. Skills define the method. Workers execute. Verification blocks lies.</p> </blockquote><hr> <h2 id="-when-to-swarm">⚡ When To Swarm<a class="anchor" href="#-when-to-swarm">#</a></h2> <p>Use a Kanban swarm when work is:</p> <table> <thead> <tr> <th style="text-align: left">Trigger</th> <th style="text-align: left">Why</th> </tr> </thead> <tbody> <tr> <td style="text-align: left">🎮 &ldquo;Make this game perfect / more fun&rdquo;</td> <td style="text-align: left">Needs audits, fixes, proof</td> </tr> <tr> <td style="text-align: left">🐛 &ldquo;Still broken&rdquo;</td> <td style="text-align: left">Needs root-cause lanes + verification</td> </tr> <tr> <td style="text-align: left">🧠 Multi-skill work</td> <td style="text-align: left">FunOps + Svelte + deploy + UI</td> </tr> <tr> <td style="text-align: left">⏳ Long-running</td> <td style="text-align: left">Must survive restart / Discord thread drift</td> </tr> <tr> <td style="text-align: left">🧪 Needs proof</td> <td style="text-align: left">Separate verifier card prevents fake done</td> </tr> <tr> <td style="text-align: left">🧑‍🤝‍🧑 Needs specialists</td> <td style="text-align: left">Parallel profiles finish faster</td> </tr> </tbody> </table> <p>Do <strong>not</strong> swarm tiny one-shot questions. Answer directly.</p>https://funday.gg/dev/docs/agents/ompcord/Mon, 01 Jan 0001 00:00:00 +0000https://funday.gg/dev/docs/agents/ompcord/<h1 id="-ompcord--discord-bridge-amy-persona">🧠💬 Ompcord — Discord Bridge (Amy Persona)<a class="anchor" href="#-ompcord--discord-bridge-amy-persona">#</a></h1> <blockquote class='book-hint '> <p><strong>TL;DR</strong> 🚀 Ompcord keeps your Pi coding agent online in Discord. Amy is the bot persona. Each session runs in its own <strong>thread</strong> off a home channel; a single <strong>embed dashboard</strong> updates in place with live progress (todo checklists, status, steps) and relocates to stay &ldquo;sticky&rdquo; at the bottom of the thread. Administrative config settings are modified live via dropdown select menus.</p>https://funday.gg/dev/docs/agents/discord-responsive-interview/Wed, 10 Jun 2026 00:00:00 -0700https://funday.gg/dev/docs/agents/discord-responsive-interview/<h1 id="-discord-responsive-interview-embed--idiot-proof-genius-cheat-sheet">🧠⚡ Discord Responsive Interview Embed — idiot-proof genius cheat sheet<a class="anchor" href="#-discord-responsive-interview-embed--idiot-proof-genius-cheat-sheet">#</a></h1> <blockquote class='book-hint '> <p><strong>Goal:</strong> one Discord message becomes a tiny wizard: user clicks/buttons/types → bot ACKs instantly → message evolves in place → Amy gets clean structured answers → no dead air, no spam, no broken interactions.</p> </blockquote><blockquote class='book-hint '> <p>🏷️ <strong>Naming — Ompcord vs Amy.</strong> <em>Ompcord</em> is the omp⇄Discord bridge (product/plugin); <strong>Amy</strong> is the bot <strong>persona</strong> it runs. <em>You install <strong>Ompcord</strong>; <strong>Amy</strong> is who answers.</em> Rename phases 1–5 are complete at docs/command/runtime/package level: package name <code>ompcord</code>, wrapper runtime <code>ompcordd.mjs</code>/<code>ompcordd.service</code>, and compatibility for <code>amyd.mjs</code>, <code>/amy</code>, <code>/pi-discord-remote</code>, legacy config, and <code>~/.omp/amy-sessions/</code>. Repo directory stays <code>pi-discord-amy</code> until final filesystem cutover. See the <a href="https://funday.gg/dev/docs/agents/ompcord-handoff-ecosystem-research/">rename plan</a>.*</p>https://funday.gg/dev/docs/agents/amy-ssot-dashboard/Wed, 10 Jun 2026 00:00:00 -0700https://funday.gg/dev/docs/agents/amy-ssot-dashboard/<h1 id="amy-ssot-embed-dashboard">Amy SSOT Embed Dashboard<a class="anchor" href="#amy-ssot-embed-dashboard">#</a></h1> <blockquote class='book-hint '> <p><strong>Goal:</strong> Amy should expose one canonical Discord embed dashboard for state, options, feedback, context, model/provider, usage, queue, and health. Slash commands and interactive buttons should render the same state snapshot — no duplicate truth, no stale status, no Markdown pretending to be UI.</p> </blockquote><blockquote class='book-hint '> <p>🏷️ <strong>Naming — Ompcord vs Amy.</strong> <em>Ompcord</em> is the omp⇄Discord bridge (product/plugin); <strong>Amy</strong> is the bot <strong>persona</strong> it runs. <em>You install <strong>Ompcord</strong>; <strong>Amy</strong> is who answers.</em> Rename phases 1–5 are complete at docs/command/runtime/package level: package name <code>ompcord</code>, wrapper runtime <code>ompcordd.mjs</code>/<code>ompcordd.service</code>, and compatibility for <code>amyd.mjs</code>, <code>/amy</code>, <code>/pi-discord-remote</code>, legacy config, and <code>~/.omp/amy-sessions/</code>. Repo directory stays <code>pi-discord-amy</code> until final filesystem cutover. See the <a href="https://funday.gg/dev/docs/agents/ompcord-handoff-ecosystem-research/">rename plan</a>.*</p>https://funday.gg/dev/docs/agents/amy-rocket-launch/Wed, 10 Jun 2026 00:00:00 -0700https://funday.gg/dev/docs/agents/amy-rocket-launch/<h1 id="-amy-rocket-launch-channels--quick-start">🚀 Amy Rocket Launch Channels — quick-start<a class="anchor" href="#-amy-rocket-launch-channels--quick-start">#</a></h1> <blockquote class='book-hint '> <p><strong>Intent:</strong> let Amy listen in one or more normal Discord channels without instantly running every message. Amy adds <code>🚀</code>; the original author can edit/improve the message; when they click <code>🚀</code>, Amy launches the final prompt into a new thread and mirrors progress back to the channel dashboard.</p> </blockquote><blockquote class='book-hint '> <p>🏷️ <strong>Naming — Ompcord vs Amy.</strong> <em>Ompcord</em> is the omp⇄Discord bridge (product/plugin); <strong>Amy</strong> is the bot <strong>persona</strong> it runs. <em>You install <strong>Ompcord</strong>; <strong>Amy</strong> is who answers.</em> Rename phases 1–5 are complete at docs/command/runtime/package level: package name <code>ompcord</code>, wrapper runtime <code>ompcordd.mjs</code>/<code>ompcordd.service</code>, and compatibility for <code>amyd.mjs</code>, <code>/amy</code>, <code>/pi-discord-remote</code>, legacy config, and <code>~/.omp/amy-sessions/</code>. Repo directory stays <code>pi-discord-amy</code> until final filesystem cutover. See the <a href="https://funday.gg/dev/docs/agents/ompcord-handoff-ecosystem-research/">rename plan</a>.*</p>https://funday.gg/dev/docs/agents/amy-session-continuity/Wed, 10 Jun 2026 00:00:00 -0700https://funday.gg/dev/docs/agents/amy-session-continuity/<h1 id="-amy-session-continuity--resume-a-discord-thread-from-the-cli">🔗🧵 Amy Session Continuity — resume a Discord thread from the CLI<a class="anchor" href="#-amy-session-continuity--resume-a-discord-thread-from-the-cli">#</a></h1> <blockquote class='book-hint '> <p><strong>TL;DR</strong> 🚀 Every Amy Discord thread <strong>is</strong> an on-disk omp session. Grab the thread ID → point <code>omp</code> at that thread&rsquo;s <code>--session-dir</code> → add <code>-c</code>. You&rsquo;re back in the exact same conversation, now in your terminal. Daemon and CLI share one session file transparently.</p> </blockquote><hr> <h2 id="-do-it-in-one-command">⚡ Do it in one command<a class="anchor" href="#-do-it-in-one-command">#</a></h2> <p>A Discord thread URL ends in the <strong>thread ID</strong>:</p>https://funday.gg/dev/docs/agents/ompcord-handoff-ecosystem-research/Wed, 10 Jun 2026 00:00:00 -0700https://funday.gg/dev/docs/agents/ompcord-handoff-ecosystem-research/<h1 id="-ompcord--handoff--ecosystem-research-charter">🪂🔭 Ompcord — Handoff &amp; Ecosystem Research Charter<a class="anchor" href="#-ompcord--handoff--ecosystem-research-charter">#</a></h1> <blockquote class='book-hint '> <p><strong>Source session:</strong> <code>amy-jun10-1631</code> (thread <code>1514275906170912769</code>, 2026-06-10). This page is the seamless-continuation handoff: the next agent should be able to proceed <strong>without</strong> reading that conversation. Two parts: <strong>(A) Handoff</strong> — exact state + finalized rename plan; <strong>(B) Research Charter</strong> — the next session&rsquo;s main job.</p> </blockquote><hr> <h2 id="-goal">🎯 Goal<a class="anchor" href="#-goal">#</a></h2> <p>Evolve the always-on omp⇄Discord bridge toward <strong>100% intuitive, responsive perfection</strong>. The product is being branded <strong>Ompcord</strong> (bot/persona stays <strong>Amy</strong>). Because the product is <strong>still early-stage</strong>, the next session must run <strong>exhaustive, multi-source research</strong> across the entire pi/omp/discord plugin &amp; package ecosystem and <strong>publish a deep comparative report</strong> in these docs: <em>what to learn or adapt from each</em>.</p>https://funday.gg/dev/docs/agents/ompcord-ecosystem-learnings/Wed, 10 Jun 2026 00:00:00 -0700https://funday.gg/dev/docs/agents/ompcord-ecosystem-learnings/<h1 id="-ompcord--ecosystem-learnings">🔭 Ompcord — Ecosystem Learnings<a class="anchor" href="#-ompcord--ecosystem-learnings">#</a></h1> <blockquote class='book-hint '> <p><strong>What this is.</strong> The deliverable the <a href="https://funday.gg/dev/docs/agents/ompcord-handoff-ecosystem-research/">Handoff &amp; Research Charter</a> commissioned: a grounded, source-read comparison of every relevant pi/omp/discord package, scored for <strong>what Ompcord should learn or adapt while it is still early-stage</strong>. Every claim is cited to a real file path (read under <code>.bun/install/cache/…</code>) or a URL. Nothing here is hand-waved from a mockup.</p> </blockquote><blockquote class='book-hint '> <p><strong>How to read each entry (5-point contract).</strong></p> <ol> <li><strong>What it is / does</strong> — grounded one-liner. 2. <strong>Key patterns &amp; APIs</strong> — the symbols/files worth knowing. 3. <strong>Verdict</strong> — 🟢 Adopt · 🟡 Adapt · 🔴 Skip (per feature). 4. <strong>Effort · risk</strong> — <code>S/M/L</code> · <code>low/med/high</code>. 5. <strong>Cite</strong> — exact source.</li> </ol> </blockquote><p><strong>Legend</strong> — 🟢 <strong>Adopt</strong>: lift as-is / consume directly · 🟡 <strong>Adapt</strong>: copy the pattern, re-implement for Discord/daemon · 🔴 <strong>Skip</strong>: wrong substrate or premature. Effort <code>S</code>≈hours, <code>M</code>≈a focused day, <code>L</code>≈multi-day. Risk = blast radius if it breaks a live turn.</p>https://funday.gg/dev/docs/agents/langfuse-integration/Wed, 10 Jun 2026 00:00:00 -0700https://funday.gg/dev/docs/agents/langfuse-integration/<h1 id="-langfuse-tracing--robust-ingestion">📊 Langfuse Tracing &amp; Robust Ingestion<a class="anchor" href="#-langfuse-tracing--robust-ingestion">#</a></h1> <blockquote class='book-hint '> <p><strong>TL;DR</strong> 🚀 Observe every agent turn safely without blocking execution or hitting body size limits. Langfuse traces are exported via OpenTelemetry (primary) with a REST fallback (backup). Large payloads (long prompt histories, git diffs, file reads) can aggregate to hit the self-hosted Next.js <strong>HTTP 413 &ldquo;Body exceeded 4.5mb limit&rdquo;</strong> block on batch ingestion. We fix this via OTel visibility buffers, payload truncation, and chunked batch flushes. 🔌</p>