agent-liveness

Fluyt

For agents who think "merged" means "done".

Your agents write the code. Fluyt makes them finish the job. Fluyt is a plugin marketplace that holds one plugin, fluyt, for Claude Code and Codex. Install it in a repo and your agent sessions follow one tested ritual from issue to merge, instead of improvising a new one every session.

Status: version 1.0.0, MIT licensed. CHANGELOG.md is the record of what changed.

Why

Coding agents write code well. The work around the code is where they slip:

• the CHANGELOG entry is skipped, or the version bump is wrong;
• the release branch gets squashed and its per-item history is gone;
• the PR merges, but its issue stays open;
• a context reset wipes the session's state, and the next session starts by guessing;
• a background sub-agent goes quiet, and nobody can tell whether it is working or dead;
• ten repos with ten sessions, and no one place that knows what is running, what is blocked and what needs you.

Fluyt turns each of these into a written ritual, a specialist role or a guard hook. The process lives in the plugin. Your repo keeps only its own facts.

What you get

• One work item, shipped end to end: branch, implement, test, CHANGELOG and version, Closes #N, PR, auto-merge, then a check that the issue really closed.
• A backlog and releases that stay honest: tiered issues, a fixed selection order, and a release that is always a merge commit, never a squash.
• Orchestration: one main session that delegates to six specialist roles, runs parallel lanes in worktrees, and checks reports before trusting them.
• Hand-overs that survive a context reset: written from the tree, not from memory, so a successor can act without the transcript.
• A cross-project hub: one session that coordinates many project sessions, relays your decisions verbatim, and never runs a project's work itself.
• Onboarding and re-sync: start a new repo from scratch, adopt an existing one, or check a repo for drift after a plugin update.
• GitHub or Azure DevOps, and Claude Code or Codex, from one payload.

Fluyt ships itself with its own process.

Quick start

Requires a GitHub repo with Issues and an authenticated gh CLI (or Azure DevOps with an authenticated az, via forge-azure-devops), and a plugin-capable Claude Code or Codex client. On Claude Code, the five hooks also need Node.js 18 or later on PATH: each is a node -e one-liner, so without it their Node logic is inert, and each says so whenever it is skipped. The full guide is docs/consumer-integration.md.

1. Install the plugin

Claude Code. Merge this into your repo's committed .claude/settings.json, so anyone who opens the repo is prompted to install it:

{
  "extraKnownMarketplaces": {
    "fluyt": {
      "source": { "source": "github", "repo": "ArjenVanSilfhout/fluyt", "ref": "main" },
      "autoUpdate": true
    }
  },
  "enabledPlugins": { "fluyt@fluyt": true }
}

Keep "ref": "main". The repo's default branch is dev (integration); main is the release branch.

Or install by hand (this tracks the default branch, dev; the JSON above is the way to pin main):

/plugin marketplace add ArjenVanSilfhout/fluyt
/plugin install fluyt@fluyt

Codex.

codex plugin marketplace add ArjenVanSilfhout/fluyt --ref main
codex plugin add fluyt@fluyt
codex plugin list

Then start a new session or task, so the client loads the new skills.

2. Adopt the conventions

Run fluyt:adopt-conventions in your repo (/fluyt:adopt-conventions on Claude Code, $fluyt:adopt-conventions on Codex). It writes your Project Facts block, merges the settings, .gitignore, .gitattributes, CHANGELOG and DECISIONS skeletons without overwriting your own, interviews you for your repo's invariants, and proposes retiring local process files the plugin now covers.

3. Ship something

/fluyt:ship-work-item

On Codex: $fluyt:ship-work-item.

Staying current

Claude Code, three steps, each needed: claude plugin marketplace update fluyt refreshes the marketplace clone; claude plugin update fluyt@fluyt re-points the install record at the new payload (for a repo with a project-scoped record, run it from that folder with --scope project); then restart Claude Code, because a running session can keep the payload it loaded. Codex: codex plugin marketplace upgrade fluyt, then codex plugin add fluyt@fluyt, then start a new task. On either client, then run adopt-conventions in re-sync mode ("re-sync the conventions"). It proposes what changed and applies nothing without your yes.

What's inside

Sixteen skills, six specialist roles, five Claude Code hooks and ten templates, grouped here by what they get done.

Ship one work item

Backlog and releases

Orchestration and parallel lanes

Hand-overs across context resets

A hub for many repos

Onboarding and upkeep

Other forges and clients