← Home

Quickstart

Ten minutes, three commands, one screenshot. No hub required for this walk-through — fukura runs fully offline until you opt in to a hub.

1Install

# macOS / Linux
curl -sSL https://fukura.dev/install.sh | bash

# or from source
git clone https://github.com/boostbit-inc/fukura && cd fukura && cargo install --path .
The installer drops fukura (and the fuku alias, if available) into your PATH. Verify with fuku --version.

2Initialise a repo

cd ~/your-project
fuku init
Creates .fukura/, starts the background daemon, and installs the shell hook for your current shell (zsh / bash / fish / powershell). Every command you run from now on is observed; failed ones are captured automatically.

3Cause a capture

# run something that fails
cargo build

# wait a few seconds, then
fuku search "error"
You should see an auto-note titled after the captured error, with stderr trimmed + redacted and tagged by the adapter that classified it (cargo, git, kubernetes, or the generic fallback).

4View it in the browser

fuku open <note-id>
Renders the note as styled HTML (dark or light theme). Useful for sharing a link internally without standing up the hub yet.

5Hand it to your agent

# user-scope (~/.claude.json)
fuku claude-code register

# or project-scope (.mcp.json in the repo)
fuku claude-code register --scope project
After a Claude Code restart, the agent has five new tools: fukura_classify, fukura_search, fukura_record, fukura_preflight, fukura_record_attempt. Next time Claude Code runs into the same cargo error, it searches the local corpus first and its attempts are recorded with measured outcomes.

6Optional: sync to a team hub

fuku hub --url https://hub.acme.dev --token "$FUKURA_HUB_TOKEN" ping
fuku hub --url https://hub.acme.dev --token "$FUKURA_HUB_TOKEN" sync-attempts
Set up the hub first (see deploy guide), or sign up for the managed tier. Sync is idempotent and incremental — only new attempts are shipped each run.

Full command reference: every flag, every subcommand. Concept reference: EKP spec, Hub API, MCP integrations, effectiveness loop.