v4.1.0Home

fur in the Shell

Foxora Shell ships fur as part of its own binary. The shell intercepts fur invocations and runs them in-process — no subprocess hop, no separate install.

How interception works

When you type a command and press ⏎:

  1. The line is captured and the prompt freezes.
  2. If it starts with fur (or one of its top-level aliases — registry, daemon, budget, sandbox, tools), Foxora Shell calls into its embedded fur library directly.
  3. Output streams line-by-line with […] placeholders that flip to [✓] or [✗] on completion.
  4. After completion, the footer briefly flashes green and a fresh prompt appears.

Anything that is not a fur command is passed through to the underlying shell (bash / zsh / fish / pwsh). Foxora Shell still renders the output through its theme and font, but the content is unmodified.

Why embedded?

  • No PATH games. fur is always there, always the same version as the shell.
  • Faster. No subprocess fork on the hot path; the registry client and signature verifier are reused across commands.
  • Tighter UX. The shell can stream typed events instead of parsing stdout.

Standalone fur

From v1.5 onward, fur is also distributed as a standalone binary so you can use it inside any terminal (iTerm, WezTerm, Windows Terminal, …). Foxora Shell just gives it the nicest possible home.

bash
# Standalone install:
cargo install fur

# Or via Homebrew:
brew install foxora/tap/fur

Looking for the full fur reference?

Every fur command, every flag, the JSON schema, the source resolution order, kit trust policy, and the operator runbooks live in the Foxora fur docs. They apply verbatim to the embedded copy.