GitHub profilePlugins by capthvnsen
3 plugins by capthvnsen in the catalog, most-starred first.
capthvnsenalans-wayIdle check-ins, a texting voice and workspace-browser skills for a Hermes gateway on a Linux host or macOS guest VM. When the bound Telegram DM has been quiet (2 h by default, 08:00-22:00 user time, backing off when unanswered) the primary bot checks in once; morning briefs, a weekly time-saved report and cross-bot proactivity are opt-in. The workspace-setup skill walks the user through Alan's Workspace, a separate desktop app, and Tailscale. Disclosure: injects internal prompts into the bound DM (needs allow_gateway_injection); turn hooks see every session; reads ~/.config/alans-way/config.json when present; default-on Telegram reply pacing (up to 2.5 s) and remove-only reply cleanup; ships a long-running Node workspace router (SSH to the user's computer over the tailnet, VM fallback) and an operator-started HTTP bridge; setup, run by the human outside the gateway, installs services and packages, adds a tailnet-only SSH key and restarts the gateway; cross-bot proactivity shares sanitized owner-DM excerpts between profiles on one gateway. Full list: the README's Disclosures section at this pin. The plugin's Python makes no network calls; no telemetry, no stored credentials.Communityautomation9capthvnsenalans-way-computerComputer-use provider for Hermes: with computer_use.backend: alans-way-computer, the stock computer_use tool drives apps on the user's computer through the Alan's Workspace app, and on the VM's own desktop when the computer is offline. Needs the alans-way plugin's workspace setup. Disclosure: starts the workspace router as a long-running node child per session (filtered environment; desktop input enabled only for that private child, behind Hermes's computer_use approval gate); reaches the user's computer over SSH on the tailnet; resends a call refused as desktop_busy for up to 30 s without a second approval. The provider makes no network calls and stores no credentials.Communitytools9capthvnsenconductorHermes leads coding agents on your machines: any terminal coding agent, T3 Code threads, and Orca terminals. It starts a run, waits with no model, and puts one message into the chat that asked when the run finishes, errors, stalls, or needs an approval; T3 and Orca runs can be steered and stopped. It can run 10+ agents at once, one ping each. Two skills: brief researches, asks one round of questions and writes the brief; lead runs the work and checks each report. Disclosure — every start and steer of a coding agent goes through Hermes's approval prompt; it runs only the built-in agents on this machine unless the owner lists extra commands and SSH hosts in plugins.entries.conductor.settings (both empty by default); runs the agent, git status, and ssh and tmux on listed hosts (argv only, no shell strings from user text, never an approval-bypass flag); the agents edit files and run commands with your user rights under their own approval settings; children get a minimal environment plus only the keys that agent needs; keeps one wait thread per run plus a detached agent process or tmux window; writes run records to its plugin data folder and event files, exit codes and logs under ~/.conductor on the machine running the agent; reads and stores no credentials; no telemetry. Finish messages on a messaging gateway need plugins.entries.conductor.allow_gateway_injection: true. In drive mode, which only the user can turn on, it asks Hermes to send up to 5 follow-ups per run on its own.Communitytools
