Kungfu

Your agent shouldn't start over when the chat ends.

Kungfu helps a fresh agent continue the same work without asking you to explain
it all again. It does this from declared project sources, makes missing or
conflicting context visible, and preserves enough structure to continue without
reconstructing everything from conversation history.

> Kungfu UNGFU™ · Never Guess. Facts Unfold.

Why this source-identifying signature exists.
UNGFU is not a second product or runtime; Kungfu remains the product name.

Status: Coming soon. The first public CLI is being qualified against the
experience below.

The first public Alpha is additionally gated by one ordered activation
transaction. Artifact publication, Release Passport sealing, exact site
publication, public read-back, and installed-product qualification must all
bind the same product/site source SHAs, artifact root, version, tag, and
channel. Released evidence is synthesized only from those receipts; a
preparation file cannot make a released-use or first-use claim. See
Trademark public-use qualification.

An installed Kungfu gives a person or Agent the same direct answer:

kungfu release status
kungfu release verify <release-status-or-evidence.json>
kungfu release explain

The human result says what passed and what did not; --json returns the stable
KFD-3 surface. Before activation, the truthful answer is `VERIFIED, NOT
AVAILABLE`. These commands do not make trademark-registration, legal, or
first-use-date claims.

See the continuity handoff and
how it was tested, or inspect the
source protocol and retained evidence.
The current result is preparatory fixture evidence—not a provider comparison,
multi-day durability or retention result, or FO10 qualification.

Kungfu in the Agent Supply Chain

Kungfu is also the founding runtime proof for an open Agent Supply Chain:

KFD-3 discovery -> Buildchain artifact evidence -> KFD-2 assessment
  -> libkungfu / .kungfu durable work facts -> independent Agent Hubs

Kungfu and libkungfu own the fourth layer: recording, ordering, querying,
verifying, exporting, and recovering durable work facts and Episodes. The
application still owns its domain facts, and JSON is an edge projection rather
than a second authority. The public KFD Agent Hub profile lets independently
owned products carry bounded responsibility objects across that edge while
each receiver retains admission.

The current proof is exact-source and first-party: source-built runtime slices,
retained qualification, and one OpenCode-shaped reference adapter. It does not
claim OpenCode endorsement, external vendor adoption, a second independent
production Hub, public Kungfu Cloud, stable cross-platform compatibility, or
physical power-loss qualification. Read the
architecture and evaluation route.

If Kungfu is installed, ask the product itself. The first command runs the
bundled fixed KFD Hub 20 suite and explains the exact result; the second
independently rechecks the retained evidence:

kungfu agent hub qualify --output-dir ./kungfu-agent-hub-check
kungfu agent hub verify --qualification-dir ./kungfu-agent-hub-check

Use --json when an agent is the reader. A pass proves only the named local
artifact, two isolated local authority domains, and the fixed KFD package cut.
It is not KFD certification, security assessment, production fitness,
remote-network interoperability, external adoption, or evidence for an
unobserved platform.

The first-release experience

The intended one-command path is:

cd your-project
kungfu run agent

The command is the target first-release entrypoint, not a claim that a public
artifact is available today. A qualified release must let the agent:

• inspect the project and explain what it understands;
• show important omissions, conflicts, and decisions instead of guessing;
• keep the current work coherent across fresh contexts and agent processes;
• record what happened so progress and the next action do not depend on chat

history.

The first visible value should arrive within minutes. The deeper value appears
over the following days, when the same work survives context loss, changed
understanding, failed attempts, handoff, and restart.

Why it matters

• Less context pressure. The agent can select verified project context

instead of repeatedly loading the whole repository.

• Durable work continuity. Intent, current understanding, action boundaries,

and outcomes remain available after the original conversation is gone.

• Inspectable understanding. Sources, omissions, uncertainty, and evidence

stay visible to both people and agents.

Keep your work when you leave or upgrade

Kungfu treats Exit and migration as a product contract. Qualified stable
releases on the same major.minor line preserve registered authoritative
semantics, not physical provider paths, caches, or presentation. The current v4
alpha remains exact-evidence-only; it does not yet carry that stable promise.

Read the Exit, migration, and version compatibility policy
for the support boundary, current qualification matrix, and non-claims. An
installed artifact exposes its exact policy and protocol inventory without
initializing a runtime:

kungfu exit verify --info --json

The public install/update claim is still closed. The exact current matrix,
one-command behavior, activation boundary, rollback guidance, and explicit
non-claims are in Upgrade Kungfu; source fixtures
and prepared package-manager adapters are not public release artifacts.

Keep using the agents you already have

kungfu run agent is the golden path, not a required replacement for Codex,
Claude Code, VS Code, terminals, or other agent surfaces. The same local
contracts and work state must remain available through the Kungfu CLI and APIs
when an agent continues to run elsewhere.

Go deeper

• Why Kungfu begins with a minimal human sovereign core
• Inspect and reanalyze the bounded public work sample
• How the complete Kungfu system works
• Agent Supply Chain architecture and evaluation
• Documentation Guide
• Documentation Map
• Known Limits
• Build and contribute

Agents working from a source checkout should begin with AGENTS.md
and Verified Context for Agents. An
installed runtime carries its own local agent brief:

kungfu agent brief

To discover the exact Fact and Episode invariants, their owners, current
evidence routes, and residual risks from a source checkout, run:

./shifu invariant:verify -- --list --json

The human route is Invariant Verification.

Build from source

Public release artifacts are not available yet. To evaluate the current source
tree:

git clone https://github.com/kungfu-systems/kungfu.git
cd kungfu
./shifu doctor
./shifu sync && ./shifu build

Project status

Kungfu v4 is Coming soon. Source-built capabilities and qualification
slices exist, but public packaging, cross-platform evidence, strong power-loss
durability, and the institutional profile remain staged unless linked evidence
says otherwise.

Design intent, implemented behavior, qualified guarantees, and released
artifacts are deliberately distinct. Before relying on a claim, check
Contracts,
Known Limits, and the applicable retained
qualification evidence.

Kungfu's complete KFD-1 through KFD-13 adoption and claim boundary is published
in the generated KFD support matrix.
Source implementation, verification, Buildchain gating, and shipped release
support are reported separately; a declared badge is not a release
qualification.


Project links

• Product home:
• Developer and agent surface:
• Issues and questions: GitHub issue forms
• Security reports: SECURITY.md
• License: Apache License 2.0

Open system repositories

Kungfu's protocol, release infrastructure, build environments, and public
sites are developed in the open:

• Buildchain — auditable build

and release infrastructure with verifiable Release Passports.

• KFD — the open engineering standard

for reliable action and continuity under uncertainty.

• Build Images — source for

the reproducible environments used to build Kungfu system artifacts.

• kungfu.tech source —

source for the public product site.

• libkungfu.dev source —

source for the developer and agent surface.

• All public repositories — the complete

organization-level source map.