wyd runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 11 Sep 2026.
Local runtime provenance for coding agents. Inspect sessions and explain which one owns a process.
What the code does
We read the source, 23 h ago · rules 3dff92dd89df
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
- name: Update Formula/wyd.rb
env:
TAG: ${{ github.ref_name }}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check wyd every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to wyd
same job, measured the same waySEAM: local-first memory runtime for AI agents, with retrieval and glassbox provenance over MCP.
Runtime CSS probe — inspect layout, overflow, scroll chains in a real browser. For AI agents.
Local-first MCP runtime for coding agents with safe workspace access, AST/LSP navigation, and Git.
A capability graded local MCP runtime for Freebuff, Codex, OpenCode, and Claude Code sessions.
Session memory for coding agents: local-first recall, drift detection, on-device inference.
Local-first memory brain for AI coding agents: hooks capture sessions, beliefs injected per prompt.
Local code search for AI coding agents: hybrid search and SQL aggregation over an in-repo index.
Secure encoding-aware local workspace runtime for AI agents
wyd — questions
Answers built from our own checks of this server.