Wiff MCP server

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

Shortened. The full README is on GitHub.