About Kungfu
Work should survive the agent that started it.
Kungfu is building the continuity layer for real-world agent work: an open protocol and a local runtime that let work be resumed, handed off, and audited without forcing builders into a Kungfu-owned Hub or cloud.
Continuity, not another chat
Chats end. Processes stop. Models and vendors change. The work should keep its identity, state, evidence, and next action.
Kungfu focuses on making delegated work understandable and resumable across those boundaries.
The layer we chose
KFD is the open protocol for carrying work and responsibility between independently owned Agent Hubs. libkungfu is the local runtime for admitting, recording, and continuing that work inside a host environment.
Neither requires a central Kungfu cloud. Technical contracts and package surfaces live at libkungfu.dev.
Kungfu does not compete for the Hub
Builders keep their users, accounts, billing, models, UI, Agent, cloud, and customer relationship. Kungfu does not use integration as a route into that relationship.
KFD standardizes the boundary between Hubs; libkungfu remains a public capability layer inside the host. The highest-value Hub layer stays the Builder’s domain.
How Kungfu bootstraps
Kungfu begins with a deliberately minimal human sovereign core so memory, coordination, facts, permissions, and acceptance cannot remain an invisible organizational runtime. Participation should scale only after those capabilities exist as machine-readable Work infrastructure.
Public and auditable
Kungfu is built and dogfooded in the open through public artifacts, bounded claims, and evidence-linked releases.
This site describes direction and current evidence, not a claim that every shown capability is already generally available. Follow the open-source core and public issues on GitHub.
Commercial stewardship
Kungfu Origin Technology Limited stewards the commercial product line and its public ecosystem.
The business can grow through official artifacts, optional services, support, governance, and future team or cloud capabilities without making interoperability depend on private code or customer capture.
Capital & stewardship
Kungfu has published standing principles for how any future relationship with capital should strengthen the product and ecosystem without purchasing control of the public protocol layer.