@opencoven/coven-code installs three bins: coven-code, coven, and coven-cave (npm/package.json bin map). @opencoven/cli (the Coven daemon CLI) also installs a coven bin.
A global install of both packages makes the coven command depend on install order — npm/bun overwrite or refuse the colliding symlink, so users with the daemon installed can silently lose coven daemon start (or conversely get the TUI when they expect the daemon CLI).
Docs now point Coven Code installs at @opencoven/coven-code and daemon installs at @opencoven/cli (PR #137), which makes the dual-install case common.
Options:
- Drop the
coven alias from @opencoven/coven-code and keep coven-code + coven-cave (cleanest; coven belongs to the daemon CLI).
- Keep the alias but detect the conflict in the postinstall script and warn.
- Have the
coven launcher in @opencoven/coven-code delegate to the daemon CLI when ~/.coven/ exists.
Related: npm/package.json bin map, npm/bin/coven-code launcher.
@opencoven/coven-codeinstalls three bins:coven-code,coven, andcoven-cave(npm/package.jsonbinmap).@opencoven/cli(the Coven daemon CLI) also installs acovenbin.A global install of both packages makes the
covencommand depend on install order — npm/bun overwrite or refuse the colliding symlink, so users with the daemon installed can silently losecoven daemon start(or conversely get the TUI when they expect the daemon CLI).Docs now point Coven Code installs at
@opencoven/coven-codeand daemon installs at@opencoven/cli(PR #137), which makes the dual-install case common.Options:
covenalias from@opencoven/coven-codeand keepcoven-code+coven-cave(cleanest;covenbelongs to the daemon CLI).covenlauncher in@opencoven/coven-codedelegate to the daemon CLI when~/.coven/exists.Related: npm/package.json bin map, npm/bin/coven-code launcher.