Kungfu UNGFU™ — Continuity for Agent Work
Built in public by one human working through agents.3,467 merged public PRs across 16 repositories in 30 days.<br>Inspect the evidence →
Download Kungfu Public Alpha · Desktop + standalone CLI<br>macOSLinuxWindows<br>Install & download →
The problem · then 3 proofs
Problem<br>New Agent<br>Failure<br>Approval
The problem · 1 of 4
Continuity for Agent Work<br>The pain · 01
One Work. Fresh Agents.
Your agents don't hand off the work. You do.
Every switch means copying context, re-explaining decisions, chasing updates, and checking what got lost. Kungfu keeps the same work moving, no matter which agent takes over.
Agents change. The Work stays. Change the execution surface—not the Work.<br>Watch the Work survive →
Proof 1 of 3 · Continuity<br>Prelude · exact contract
Continuity
Can Work survive a new Agent?
The first proof isolates continuity: one Work continues across two fresh Agent Sessions without copied chat.
The mechanism exists; the next proof asks whether it still holds under real failure conditions. Exact media and its retained evidence remain independently inspectable.<br>Watch proof →
Proof 1 of 3 · Continuity<br>Exact installed artifact · 21.7 seconds
Download the 720p MP4 replay.
Can Work survive a new Agent? This exact standalone Kungfu artifact proves only the bounded offline Agent Work Lab autoplay observed in two independently captured native PTYs; it grants no Work, release, capability, or production authority.<br>EvidenceTranscriptPassport
Proof 2 of 3 · Failure retention<br>Prelude · exact contract
Failure retention
Can Work survive failure?
Inside a disposable Project, a dropped connection and a crashed replacement process remain as Attempts under the same Work.
Work survival is only the first step. If an Agent can approve its own result, continuity still is not trustworthy. Exact media and its retained evidence remain independently inspectable.<br>Start Project Tour episode 1 →
Proof 2 of 3 · Failure retention<br>Exact installed artifact · 69.6 seconds
Download the 720p MP4 replay.
Can Work survive failure? This exact standalone Kungfu artifact proves only the bounded disposable Project Tour episode 1 observed at 4x in two independently captured native PTYs; Mock Agent output and terminal observations grant no Work, release, capability, or production authority.<br>EvidenceTranscriptPassport
Proof 3 of 3 · Review and settlement<br>Prelude · exact contract
Review and settlement
Who is allowed to complete Work?
The final proof separates Agent exit, independent review, and Kungfu settlement: an Agent can produce a candidate and evidence, but cannot approve its own Work.
The governed completion boundary is now visible. Exact media and its retained evidence remain independently inspectable.<br>Start Project Tour episode 2 →
Proof 3 of 3 · Review and settlement<br>Exact installed artifact · 120.6 seconds
Download the 720p MP4 replay.
Who is allowed to complete Work? This exact standalone Kungfu artifact proves only the bounded disposable Project Tour episode 2 observed at 4x in two independently captured native PTYs; Mock Agent output and terminal observations grant no Work, release, capability, or production authority.<br>EvidenceTranscriptPassport
Kungfu UNGFU™Never Guess. Facts Unfold.<br>Why Kungfu?
Use the best Agent when it matters. Use a cheaper one when it does not. Keep the same Work across Codex, Claude, OpenCode, or your own execution surface.
See the Agent-native loop<br>For Agent Builders
Two strategic axes
Continuity for work. An open supply chain for Agent products.
KFD explains how people, Agents, and products understand, trust, cooperate, and continue. The Agent Supply Chain connects discovery, exact-artifact evidence, purpose-bound trust, durable work facts, and portability across independently owned Hubs.
KFD-3→<br>Buildchain→<br>KFD-2→<br>libkungfu / .kungfu→<br>independent Hubs
Today: exact public contracts and first-party proof. Not claimed: a live multi-Hub market or external vendor adoption.
See the evidence-bound categoryRun the installed Agent Hub proof
For Agent Builders
Build and own your Hub. Kungfu stays beneath it.
Your users, accounts, billing, models, UI, Agent, cloud, and customer relationship stay yours. Kungfu provides KFD and libkungfu; it does not compete for the Hub.
Your Hub stays yours→<br>KFD interoperates→<br>libkungfu runs locally
Run the course Hub Starter<br>See the adoption architecture<br>Verify Kungfu's Hub capability<br>Open the exact reference source
Open core.Commercial stewardship.
Kungfu is commercially operated by Kungfu Origin Technology Limited. The core project is open source, local-first, journal-first, and its first public v4 Alpha, v4.0.0-alpha.1, is now available.
Developers can start at libkungfu.dev. Product, trust, service, and legal details live on this site.
Capital & Stewardship<br>Capital should expand the ecosystem, not control the standard.<br>Read the principles that would govern any future relationship with capital →
About ·...