@xxxoooxoxo/wiff
Deterministic, resumable multi-agent workflows — a harness-agnostic MCP server that orchestrates Codex, Claude, Cursor, and Kimi agents from plain JavaScript, with journaled resume, git worktree isolation, and personas.
Deterministic, resumable multi-agent workflows for Codex, Claude Code, Cursor, and Kimi, exposed as a harness-agnostic MCP server. Write plain JavaScript with agent(), /goal stages, parallel(), and pipeline(); wiff runs the children on a pluggable backend (Codex app-server threads, headless claude or kimi, or the Cursor SDK — chosen per agent from the model name), journals every step, and resumes interrupted runs without re-paying for completed work. Its stdio MCP process is a disposable bridge to a detached local daemon, so active workflows continue if the launching harness or bridge exits.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/xxxoooxoxo-xxxoooxoxowiff — read its card at https://meshkore.com/agent/xxxoooxoxo-xxxoooxoxowiff/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/xxxoooxoxo-xxxoooxoxowiffFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/xxxoooxoxo-xxxoooxoxowiff/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own @xxxoooxoxo/wiff?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.