Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-24 · high
The tool reads one manifest and locks per-tool config so a laptop and CI resolve identical output every time.
Why now: At 4 stars and 221 commits, Enozunu is early, surfacing before most teams running multiple agent tools have felt the config-drift pain it solves.
Enozunu generates target-native configuration paths for AI coding tools from a single manifest, then locks the result so every machine installs the same setup. Multi-tool setups make config drift worse. Teams running more than one agent tool, a coding assistant alongside a separate skill runner, usually hand-maintain each config file. Those files drift apart between a laptop and CI without a shared lock.
The mechanism borrows from language package managers. Enozunu reads one manifest of skill and agent source definitions and writes out whichever path format each target tool expects. A lockfile pins those generated outputs, so a developer's machine and a CI runner resolve to identical versions. Tool authors can publish an artifact with a compatible manifest instead of writing a separate installer for every agent runtime. It's Apache-2.0 licensed, with 221 commits and 4 stars so far.
Most agent tooling still treats configuration as something an engineer hand-writes per tool, an assumption that breaks the moment a second tool or a CI runner joins the repo. Enozunu treats agent config as a dependency graph, borrowing the reproducibility guarantees developers already expect from npm or Cargo.
Each link below shares sources, entities, or timing with this story.
Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Both cover Apache, GitHub; reported by the same outlet (github.com); overlapping topics (agent, dependency).
Shared entity: GitHub / Same source domain / Shared topic / Earlier coverage / Tension
Both cover GitHub; reported by the same outlet (github.com); overlapping topics (agent, commit, configuration, each).
Shared entities / Same source domain / Shared topic / What happened next
Both cover Apache, GitHub; reported by the same outlet (github.com); overlapping topics (agent, artifact).
Both cover Apache, GitHub; reported by the same outlet (github.com); overlapping topics (agent, dependency).
Shared entities / Same source domain / Shared topic / Earlier coverage
Both cover Apache, GitHub; reported by the same outlet (github.com); overlapping topics (apache 2, author).
Both cover Apache, GitHub; reported by the same outlet (github.com); overlapping topics (agent, commit).
Both cover Apache, GitHub; reported by the same outlet (github.com); overlapping topics (agent, dependency).
Both cover Apache, GitHub; reported by the same outlet (github.com); overlapping topics (agent, each).