All plugins

kvnloo

GitHub profile2 plugins in the catalog2

Plugins by kvnloo

2 plugins by kvnloo in the catalog, most-starred first.

kvnlooglideKevin Rajan's Hermes frontend for Tern, built on alt-glitch/hermes-tern (MIT) and carrying about 890 commits of its own. One install gives hermes tern, which draws the chat as native Tern UI, plus /glide, a guided setup that makes Hermes learn from you and run more of its work locally. Added over the original: charts from Markdown tables, OpenUI and ephemeral-ui answer cards, 3D artifacts beside the chat, written artifacts and session links, LSP diagnostics cards, live wait tiles for subagents, fork-a-session panes, /rewind, /undo and /tree, native /settings and a /models provider hub, a Vim composer, a command palette and shortcut preferences, queue-or-steer busy input, opt-in live voice with helper lanes beside the thinking orb (role, model and real state from a local lane broker), a work dock, a thinking-orbs indicator, frontend channels (hermes tern --channel), and tool cards that report refusals, truncation and partial failures instead of hiding them. /fleet (with /hosts and /portfolio) shows read-only cards of local hosts, agents, GPU/CPU gauges, k3s pods and open issues and pull requests for named repositories; /intel shows read-only local intelligence (hill-climb results, skills, memory, failures, traces). Inactive on released Hermes: Tern browser blocks, image delivery across hosts, plan review with a todo HUD, native /btw side questions and read-only MCP/SSH report sheets need plugin gateway methods (ctx.register_gateway_method) that released Hermes does not have yet; they turn on when it does. Glide guards two scarce resources: your attention and the agent's context window. /glide focus shows your current phase, next deep-work window and usual stop time, learned from your own local session timestamps (or from z0intelligence's circadian and a loopback Flowkit flow estimate when installed); a deep-work block holds non-critical agent notifications and approval asks for one digest at the end while critical ones still pass, and one wind-down card saves a resume note for the next session. /glide (also hermes glide onboard) is a chain of approve cards: detect the machine and local runtimes (and z0intelligence if installed); build a corrections memory from your past local sessions (your messages that start "no,", "actually," or "correction:") and quote up to three matching corrections into each new turn through a pre_llm_call hook, using deterministic BM25 with no embeddings or model calls; a skill router catalog; a measured CPU hill climb whose referee says KEEP, REVERT or INCONCLUSIVE; offload of small tasks to an installed Ollama model with estimated savings; and an optional Taste board pane beside the chat. Disclosure — Derived from hermes-tern (alt-glitch/hermes-tern, MIT). Network: GitHub's API with the optional GITHUB_TOKEN (and GITHUB_ENTERPRISE_TOKEN only to the Enterprise hosts the user lists) for the pull request view, and through gh for /fleet repository cards; the user's own auxiliary model for live process and table charts; the frontend downloads image URLs from tool results and public 3D-model URLs it shows beside the chat, refusing private, loopback and link-local addresses on every redirect hop; /glide taste talks only to a loopback Taste Atlas server (127.0.0.1:8789 by default); /glide focus reads a Flowkit server (127.0.0.1:8787 by default, GLIDE_FLOWKIT_URL overrides) if one answers; live-voice helper lanes poll only a loopback lane broker (127.0.0.1:8791 by default) and stay off unless you name its token file in the plugin's lanes_token_file setting; no telemetry. Commands: runs the tern CLI to open files and splits, open/xdg-open for http(s) links the user clicks, and !cmd shell commands the user types in the composer; /glide runs nvidia-smi, ollama list/ollama run and, if installed, z0int doctor --json and circadian show --json, each only on an approved step, and while corrections are on it runs z0intelligence's corrections reader on every turn; /fleet runs ps, nvidia-smi, tailscale status --json, read-only kubectl get/describe and gh issue list/gh pr list, and /intel reads local snapshot files; every child gets a timeout and a minimal environment plus only that tool's own credentials (gh token, KUBECONFIG), never provider keys; the hill climb runs a local CPU benchmark; nothing is installed or downloaded. Tools and prompt: when the user grants tools.override in the profile it replaces Hermes's browser tools with a Tern-pane browser (needs plugin gateway methods); it adds system-prompt sections for pull requests and answer cards and, once turned on, quotes up to three of the user's past corrections into each turn. Reads outside its data: the profile's Hermes session database, read-only (local sessions only; cron, delegated and hidden sessions skipped), the session's background-process output, and for /fleet and /intel read-only local workspace and z0intelligence state files and /proc. Writes only under the profile. Install this or hermes-tern, not both: both register hermes tern.CommunityDesktop app2kvnloosol-piTwo mechanisms ported from NVIDIA's SoL-Pi (NVlabs/SoL-Pi, MIT). ObservationPack: a tool result over 10 KiB goes to the model in full twice, and after that the outgoing request carries a stable placeholder (id, size, 1 KiB head/tail excerpt) that the model pages back with obs_recall. The stored transcript keeps every byte, and the placeholder is byte-identical on every later request, including after a restart. Action Fusion: sol_pi_write / sol_pi_patch run Hermes' own write_file / patch, and with then_run also one follow-up command through Hermes' terminal tool, so an edit and its check take one model turn. Both are off until enabled in sol-pi.json in the Hermes home. Disclosure — rewrites only the per-call provider request copy through llm_request middleware (no context engine, no core patching). Writes archived tool results and an append-only ledger.jsonl under <hermes home>/sol-pi/<session>/ (0700/0600). Reads sol-pi.json in the Hermes home. sol_pi_write / sol_pi_patch are registered only when actionFusion is on. Fused edits and then_run run through Hermes' write_file / patch / terminal in the calling task/session; dangerous-command approval and the write denylist apply, but nested dispatch currently skips ACP/Zed edit approval, /rollback checkpoints and other plugins' pre_tool_call guards. No host-side reads of edited files. No network calls, telemetry or credentials.Communitymemory