All 26 Dependencies

Every package OpenFang depends on, ranked by repo health score.

OpenFang frames itself less as an agent framework and more as an operating system for agents — a persistent kernel process that manages agent memory, skills, extensions, and communication channels, rather than a library you import into a script that exits when the task is done. It compiles to a single binary from roughly 137,000 lines of Rust across 14 crates.

The crate layout mirrors an OS-like design: `openfang-kernel` is the core process, `openfang-runtime` executes agent logic, `openfang-memory` persists agent state, `openfang-skills` and `openfang-extensions` add capabilities, `openfang-channels` and `openfang-wire` handle communication protocols and multi-channel input/output, and `openfang-hands` appears to handle tool/action execution. Separate CLI and desktop crates, plus an SDK, provide different ways to interact with the running kernel.

Dual-licensed under Apache-2.0 or MIT (standard for Rust projects), OpenFang is explicitly pre-1.0 ("feature complete but still pre-1.0... expect rough edges") as of its most recent documented version, so it's an actively evolving project rather than a mature, stable-API tool.

Join founders buildingwith open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on Substack
Join 750+ subscribers

Search