wyd MCP server

wyd

wyd? — what you doing?

See what your coding agents left running.

Coding agents spawn MCP servers, headless browsers, dev servers, workers, and databases.

ps tells you what is running. wyd tells you why — which session started it, in which project, and whether it's leftover.

OpenCode
└─ chrome-devtools-mcp
   └─ Chromium ×8       1.2 GB

Agent exited 47m ago
⚠ leftover

Local, macOS and Linux. No account, no network, no telemetry.

https://wyd.sh

curl -fsSL https://wyd.sh/install.sh | sh
# or
brew install oxyplay/tap/wyd
# or
cargo install wyd
wyd
wyd upgrade   # brew or cargo, matching the install
wyd --demo    # deterministic synthetic dataset — screenshots/demos, no host scan

Each tagged release publishes the crate to crates.io and bumps Formula/wyd.rb in oxyplay/homebrew-tap automatically, so wyd upgrade stays current with no manual step. wyd upgrade still prints a hint if a formula bump is ever lagging.

Binaries: GitHub Releases. From a clone: cargo install --path .

OS daemons stay hidden. Desktop Chrome stays hidden. Agent-spawned Chromium does not.

Why wyd

Built for people who run coding agents all day and then ask what did that session leave behind?

Runtime ownership

Beyond the live view, wyd tracks coding-agent runtime sessions — which resources a session spawned, keyed by bootid + pid + starttime, so the provenance survives process re-parenting and Wyd restarts. A deterministic resolver attributes resources to a session with an explainable score when exact ancestry is gone.

agent session owns it, it names the system source instead (systemd unit, launchd, cron, tmux, ssh, snap, flatpak, or an interactive shell), with the ancestry chain. Exit codes: 0 cleanly owned, 1 leftover/unattributed, 2 not running, 5 internal error.

• Sessions view in the TUI (top-level): agent · project · state · age · id, with a details panel.
• wyd why — which session owns a process, and the evidence. When no

• wyd --json sessions — recorded sessions as JSON.
• wyd serve — a local daemon over a Unix socket (wyd.sock, mode 0600, single-instance). Keeps provenance fresh and answers read-only queries; vendors can register sessions with sessionstart / sessionend (their id maps to a Wyd session as an alias).
• wyd mcp — a Model Context Protocol server over stdio, so a coding agent can ask wyd for its sessions, who owns a PID, and its managed runs (--allow-run adds host execution).

MCP

wyd also speaks the Model Context Protocol over stdio, so a coding agent can ask the machine what it — or other agents — left running.

wyd mcp                 # read-only
wyd mcp --allow-run     # also allows starting and cancelling runs

Starts the local MCP server. Read tools are always available: listsessions (recorded agent sessions), explain (which session owns a process, by pid), listruns, getrun, readrunoutput and getcapacity. --allow-run adds startrun and cancelrun for that connection only — without it those calls are rejected with a message to restart with --allow-run. No network, no account — the answers come from the local provenance store.

Registered in the MCP Registry:

• MCP Registry name: mcp-name: io.github.oxyplay/wyd

Shortened. The full README is on GitHub.