Ross ROSS = Recommend OSS · open-source software intelligence for agents

kungfu-systems/kungfu

Your agents don’t hand off the work. Kungfu keeps the same Work moving across Codex, Claude, OpenCode, and your own execution surface. observed · 2026-08-28

github.com/kungfu-systems/kungfu · homepage · C++ · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

99/100

  • Activity 99
  • Release rhythm 99
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 0
  • age_days: 3213
  • days_rel: 9
  • days_push: 7
  • n_releases_24m: 4

Full methodology

Adoption not part of the score

4502 stars · 1286 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Kungfu is an open-source continuity layer for AI agent work, consisting of a local C++ runtime (libkungfu) and an open protocol (KFD) that let a unit of Work keep its identity, state, and evidence as it moves across agents like Codex, Claude, OpenCode, and Amp. It ships as a standalone CLI plus optional TUI/GUI sidecar views, with durable project-local state in a .kungfu/ workspace.

Use cases

  • hand off an in-progress task from one AI coding agent to another without copying context
  • resume agent work after a crash or dropped connection
  • switch from an expensive model to a cheaper one mid-task while keeping the same Work
  • audit and inspect what an agent did across multiple sessions
  • run a deterministic mock-agent recovery scenario to test continuity locally
  • keep durable, machine-readable records of agent attempts, approvals, and next actions

When to choose

  • you regularly switch between multiple AI coding agents (Codex, Claude, OpenCode, Amp) on the same project
  • you need work to survive agent crashes, disconnects, or vendor/model changes
  • you want a local, auditable continuity layer without a mandatory cloud or vendor lock-in
  • you want to mix expensive and cheap agents on the same unit of work

When to avoid

  • you use a single agent exclusively and never hand off or resume work
  • you need a production-stable, generally available tool - it is currently in public Alpha
  • you want a fully autonomous multi-agent framework rather than a work-continuity and handoff layer
  • you cannot tolerate a project-local .kungfu/ workspace directory in your repos

Facets

cli-tool · maturity experimental

agent-framework workflow-automation developer-tools cli developer-tools windows cli cross-platform agent-orchestration agent-continuity work-handoff agent-memory local-runtime open-protocol multi-agent ai-agents automation command-line macos linux

3 sources

Member repositories

RepositoryRoleHealth v2
kungfu-systems/kungfumain99

For agents

markdown · JSON · MCP: product_card(name="kungfu-systems/kungfu")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem