Installation
fnclaude is on npm. A global install gives you the fnc binary:
npm i -g fnclaudeCheck it:
fnc --versionRequirements
Section titled “Requirements”- Bun.
fncruns under Bun. You can install the package with npm, but the binary re-executes itself underbunon launch, and fails with a pointer to the Bun installer ifbunis not on yourPATH. Node alone is not enough. - The
claudeCLI on yourPATH.fncresolves where the session should run, translates your arguments, and hands off to claude. Without claude installed it stops with a message pointing you at Claude Code.
Platform support
Section titled “Platform support”Linux and macOS. The code has a Windows fallback path, but it has never been exercised. Expect breakage there.
Configuration files
Section titled “Configuration files”Both are optional.
| Path | What it holds |
|---|---|
$XDG_CONFIG_HOME/fnclaude/config.toml |
Auto-tmux, auto-handoff, the command that opens a new terminal window for a sibling session, and environment injected into every claude child. |
~/.claude/settings.json |
cloneTemplate, worktreeTemplate, and branchTemplate under repoSettings. Shared with the claude-code-worktree-paths plugin. |
The keys are on CLI flags.