Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Wiff

by xxxoooxoxoversion 0.9.1i★ 5iRuns on your computerRepository ↗
Registry nameio.github.xxxoooxoxo/wiff

How to install

What it does

Deterministic, resumable multi-agent workflows across Codex, Claude, Cursor, and Kimi.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity9/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score17/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Wiff. Follow https://mcp.popnx.com/i/xxxoooxoxo-wiff.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Wiff for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "wiff": { "command": "npx", "args": [ "-y", "@xxxoooxoxo/wiff" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Wiff tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "wiff": {
          "command": "npx",
          "args": [
            "-y",
            "@xxxoooxoxo/wiff"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use Wiff and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Wiff or shows a Wiff tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Wiff yet

Wiff runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Wiff

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Wiff for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user wiff -- npx -y @xxxoooxoxo/wiff 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Wiff tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user wiff -- npx -y @xxxoooxoxo/wiff
  4. Type /mcp in Claude Code

    You should see Wiff listed as connected

  5. Try it

    Use Wiff and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Wiff or shows a Wiff tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Wiff for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "wiff": { "command": "npx", "args": [ "-y", "@xxxoooxoxo/wiff" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Wiff tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use Wiff and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Wiff or shows a Wiff tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Wiff for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "wiff": { "type": "stdio", "command": "npx", "args": [ "-y", "@xxxoooxoxo/wiff" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Wiff tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use Wiff and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Wiff or shows a Wiff tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Wiff💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user wiff -- npx -y @xxxoooxoxo/wiff

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "wiff": {
      "command": "npx",
      "args": [
        "-y",
        "@xxxoooxoxo/wiff"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "wiff": {
      "command": "npx",
      "args": [
        "-y",
        "@xxxoooxoxo/wiff"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "wiff": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@xxxoooxoxo/wiff"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
69/wk
Connection
Runs on your computer
Latest versioni
0.9.1
Categoryi
Other
Published to registryi
Sep 10, 2026
Code last changedi
Sep 10, 2026
Maker
xxxoooxoxo
Packages
npm: @xxxoooxoxo/wiff
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account xxxoooxoxo, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 months ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @xxxoooxoxo/wiff@0.9.1

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/xxxoooxoxo-wiff.svg)](https://mcp.popnx.com/en/servers/xxxoooxoxo-wiff)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 95% of the other 20653 servers in this category
  • Published to the registry more recently than 35% of the other 20653 servers in this category
  • Basic checks equal to or better than 99% of the other 20653 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Wiff safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 2 months ago, and the latest version (0.9.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Wiff
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

wiff

Harness-agnostic, deterministic, resumable multi-agent workflows — written as plain JavaScript. Like `wf`, but wiff.

Fan a task out to a fleet of agents with a small script instead of a prayer. You write ordinary JavaScript with agent(), /goal stages, parallel(), and pipeline(); the runtime executes it in the background, journals every step, and — when a run dies halfway through — resumes it without re-paying for a single completed agent. A disposable MCP bridge talks to a persistent local daemon, so active workflows outlive the Codex, Claude Code, Cursor, or cron process that launched them while each child runs on Codex, Claude, Cursor, or Kimi.

export const meta = {

name: "audit", description: "Audit files in parallel, fix confirmed issues in isolation", phases: [{ title: "Audit" }, { title: "Fix" }], };

phase("Audit"); const findings = await parallel( args.files.map((file) => () => agent(Audit ${file} for auth bugs, { key: audit:${file}, // stable key → free replay on resume sandbox: "read-only", schema: findingSchema, // structured JSON output }), ), );

phase("Fix"); return await parallel( findings.filter((f) => f.real).map((f) => () => agent(Fix: ${f.summary}, { key: fix:${f.file}, agentType: "surgeon", // persona from .codex/agents/surgeon.md isolation: "worktree", // own git worktree — parallel writes can't collide sandbox: "workspace-write", }), ), );

When one stage must keep working until a condition is genuinely satisfied, make it a native Codex goal:

phase("Verify and repair");

await agent("/goal Make the unit tests pass and verify the final run.", { key: "tests-green", sandbox: "workspace-write", timeoutMs: 30 * 60 * 1_000, });

Wiff holds the workflow at that statement and continues the same Codex thread while its goal is active. The next stage starts only after the worker marks the goal complete; blocked, paused, or limited goals fail explicitly.

Put durable preferences in ~/.wiff/config.json, with optional project overrides in /.wiff/config.json:

{

"version": 1, "instructions": "Verify before reporting success.", "defaults": { "model": "claude-sonnet-5", "fallbackModels": ["gpt-5.6-sol"] }, "rules": [ { "name": "fix-until-green", "when": { "phase": ["Fix", "Repair"] }, "goal": "Relevant tests must pass.", "options": { "model": "gpt-5.6-sol", "effort": "high" } } ] }

Defaults fill missing agent options; matching rules are explicit user policy and override generated workflow options. Instructions are injected alongside the task, ordered fallback models may cross backends, and applicable preference changes invalidate cached results on resume.

Why

There is no harness-agnostic workflow orchestration system. Every coding harness has some multi-agent story — Claude Code has its Workflow tool, Codex has subagents, Cursor has its own agents — but each one is welded to its harness: its runs live and die with that app, its state is invisible to everything else, and none of them can be driven from anywhere but their own chat window. wiff pulls orchestration out of the harness: a persistent local daemon owns execution and durable on-disk state while each harness gets a disposable stdio MCP bridge. Any MCP client — Codex, Claude Code, Cursor, a cron job — can start, disconnect from, watch, resume, or cancel the same runs, and the orchestration itself is a script rather than a conversation.

Ad-hoc multi-agent orchestration ("spawn some subagents for this") is also great until the run is 40 agents deep and something dies. Workflows-as-code give you:

  • Determinism — the orchestration is a script, not vibes. No time, randomness, filesystem, or network inside workflow code; agents do the external work.
  • Outlive the parent — closing or killing the launching MCP bridge does not interrupt a run. The detached daemon keeps executing, and another harness can reconnect with the run id.
  • Resume, not retry — every agent call is journaled with a stable key and an input hash. A graceful daemon restart automatically resumes durable active runs. After an abrupt daemon or machine crash, explicitly resume the safely interrupted run: unchanged completed agents replay from cache instantly and for free. Agents that were interrupted mid-turn re-run with a digest of their previous attempt's transcript injected ("here's what you already did — continue"), and worktree agents inherit their partial checkout instead of starting over.

That screenshot is the feature: the host was killed mid-synthesis, and on resume the four finished agents came back from the journal in 0ms — only the interrupted one re-ran.

  • Fail-hard semantics — a rejected agent fails the workflow loudly (parallelSettled() is the explicit opt-out). No silent nulls masquerading as success.
  • Visible scheduling — agents are journaled as queued before they acquire a runtime slot and running only when backend execution starts. Queue and execution durations stay separate, while owner heartbeats make a live-but-stalled workflow visible.
  • Isolation where it matters — isolation: "worktree" gives each writing agent a fresh detached git worktree. Clean ones vanish; dirty ones are kept and listed on the run for you to inspect or merge.
  • Personas — agentType: "reviewer" injects a markdown persona as the child's developer instructions, with frontmatter defaults for model/effort/sandbox.

Install

Codex (plugin: MCP tools + the $workflow authoring skill):

codex plugin marketplace add https://github.com/xxxoooxoxo/wiff.git

codex plugin add wiff@wiff

Claude Code (plugin: MCP tools + skill):

claude plugin marketplace add xxxoooxoxo/wiff

claude plugin install wiff@wiff

Anything else — the server is on npm (@xxxoooxoxo/wiff) and the official MCP Registry (io.github.xxxoooxoxo/wiff), so registry-aware clients can install it by name, and everything else runs it with npx:

npx -y @xxxoooxoxo/wiff        # stdio MCP server

Or from a local checkout:

git clone https://github.com/xxxoooxoxo/wiff.git

codex plugin marketplace add ./wiff codex plugin add wiff@wiff

Then start a new Codex session and either invoke the bundled skill with $workflow or just ask: *"run this as a resumable workflow."*

Installing the plugin auto-approves its five workflow-controller tools so headless and desktop runs don't stop at an MCP approval prompt. Agent filesystem access is still governed per-call by sandbox.

Using from other harnesses (Claude Code, Cursor, any MCP client)

The Codex *plugin* is just packaging. The engine underneath is a plain stdio MCP server, so any MCP-speaking harness can orchestrate wiff workflows. The mental model: both the orchestrator and the workers are pluggable — whoever drives, each agent() child runs on a backend chosen from its model name: gpt-*/o* models run as native Codex threads via a local codex app-server (gpt-6-astra needs Codex CLI >= 0.153.4); current claude-fable-5-1, claude-fable-5, claude-opus-5, claude-sonnet-5, and claude-haiku-4-5 models—or the moving fable/opus/sonnet/haiku aliases—run as headless claude agents, composer-* and grok-* models (including cursor-grok-* slugs) run through the official Cursor SDK (@cursor/sdk) in-process, and kimi-code/* models run as headless kimi processes. A workflow can mix them freely (provider: "codex" | "claude" | "cursor" | "kimi" overrides the inference, WIFF_BACKEND sets the fallback for unrecognized models). On the Claude, Cursor, and Kimi backends, workspace-write requires isolation: "worktree"; Kimi's read-only mode is advisory because print mode auto-approves tools and has no OS sandbox.

Requirements on the machine, regardless of harness: Node >= 22, git if you use isolation: "worktree", and the runtime of whichever backend your agents use — Codex CLI

= 0.144.6

and/or claude CLI installed and authenticated, CURSOR_API_KEY for Cursor agents, or the kimi CLI configured with the requested full model alias (for example kimi-code/k3).

Claude Code — the plugin install above is the easy path. To wire just the server manually:

claude mcp add wiff -- npx -y @xxxoooxoxo/wiff

Tool calls go through Claude Code's own permission system; to skip per-call prompts, allow the five tools in .claude/settings.json:

{ "permissions": { "allow": [

"mcpwiffworkflow_start", "mcpwiffworkflow_status", "mcpwiffworkflow_wait", "mcpwiffworkflow_cancel", "mcpwiffworkflow_models" ] } }

Cursor / Windsurf / Claude Desktop — add the server to the client's mcp.json:

{

"mcpServers": { "wiff": { "command": "npx", "args": ["-y", "@xxxoooxoxo/wiff"] } } }

Notes for non-Codex hosts:

  • State is shared. Every harness reads and writes the same ~/.wiff/runs/, so a run started from Codex can be watched, cancelled, or resumed from Claude Code (and vice versa), and the live viewer sees everything.
  • Execution is daemon-owned. The first controller call starts one detached daemon per Wiff state root. MCP bridges may exit without affecting active work. The daemon exits after 15 idle minutes by default (WIFF_DAEMON_IDLE_MS overrides this) and writes its pid, socket, and log to ~/.wiff/daemon.json and ~/.wiff/daemon.log.
  • Controllers authenticate before sending work. A 0600 secret under ~/.wiff/control/ drives a challenge-response handshake. The bridge proves daemon identity before transmitting workflow scripts or arguments; the daemon also authenticates every controller request.
  • Ownership is an OS lease, not a stale file. A secret-derived loopback port is held for the daemon's complete lifetime. The operating system grants it to exactly one owner and releases it automatically on crash; only that owner may replace the control socket or lock metadata. If the derived port conflicts with unrelated local software, set WIFF_DAEMON_OWNERSHIP_PORT to an available loopback port; Wiff reports the exact conflict rather than treating it as a live owner.
  • The first controller supplies the daemon environment. PATH, backend credentials, CODEX_HOME, persona paths, and Wiff defaults remain those of the bridge that started the daemon. If they change, gracefully terminate the pid recorded in ~/.wiff/daemon.json (active durable runs resume when the next bridge starts) or wait for the 15-minute idle shutdown.
  • Bring the script contract into context. The `$work

Only the beginning is shown; read the rest in the repo