butschster

Telegram bot webhook handler with registry-based command routing

MCP (Model Context Protocol) server for Wippy — exposes tools to LLM clients over stdio

System monitor — stats collector and TUI dashboard for Wippy applications

A runtime for driving external applications. An integration is declared in the registry and ships as a module; a project, its actors and its work are components, because that is where credentials live. Testing is the first kind of work, not the only one — output_kind decides whether a run produces a finding, an artifact somebody publishes, or a report.

Native Wippy LLM provider backed by the official Codex CLI ChatGPT sign-in — Responses transport with encrypted-reasoning continuation, a model catalog mirrored from the Codex cache, and a status page.

Interactive registry graph visualization with DOT rendering and edge rule engine

Terminal UI toolkit — Lip Gloss-inspired style system, layout primitives, and ANSI rendering

The bridge from butschster/bridge to a Telegram channel. Carries articles a person has already approved in the content machine out to subscribers: the bridge picks which one, an agent writes the announcement, and the article itself goes as the markdown it was approved as. The bot is a connection, not an environment variable, so one stand can serve several channels.

Keyword research for Kickside — Google Ads search demand and keyword ideas through a WebAssembly client, exposed as agent tools, a pullable demand source, and a deterministic demand score.

Low-level browser automation SDK via Chrome DevTools Protocol (CDP)

A fault-tolerant cost monitoring system for DigitalOcean droplets using actor model.

Text-to-Speech module using Microsoft Edge Read Aloud via WebSocket

A blog whose articles are block documents rather than walls of text — paragraphs alongside tables, charts and figure rows. Markdown in, blocks out, deterministically. One core behind an HTTP API, a Flow Block and an MCP preset, so a person in the editor and a model over MCP write the same kind of post under the same rules.

MCP tools and prompts for live Wippy runtime interaction — registry CRUD, code evaluation, process communication, system introspection, event bus, queues, key-value store, and workspace file operations

MCP tools for searching and reading Wippy documentation from LLM clients

MCP tools for multi-project filesystem operations — read, write, search, and navigate files

Autonomous NPC workers — scheduled agent routines installed as automations (cron owns timing, agents own execution), with a routines API and page.