73 Commits

Author	SHA1	Message	Date
Gustav the Bot	d5b4abd2ac	fix(fff-mcp): answer pre-initialize probes instead of exiting (#797) (#798) ... rmcp 1.7.0 aborts startup on any pre-initialize request except ping, so a client probing with server/discover (SEP-1442 stateless spec) killed the process before it could fall back to the legacy handshake. Wrap the stdio transport so unsupported pre-init requests get -32601 and the server keeps waiting for initialize. Full stateless support is out of scope. Closes #797 Co-authored-by: gustav-fff <286169375+gustav-fff@users.noreply.github.com>	2026-08-18 20:22:38 -07:00
Dmitriy Kovalenko	459ebcdbdb	chore: release 0.10.5	2026-08-16 09:00:23 -07:00
Dmitriy Kovalenko	a166255d8f	chore: release 0.10.4	2026-08-15 14:35:20 -07:00
Kh05ifr4nD	ffd8eb9c08	fix(mcp): standalone constraints in multi_grep (#753) ... * fix: apply standalone constraints in multi_grep * chore: use pub(crate) --------- Co-authored-by: Dmitriy Kovalenko <dmitriy@iusevimbtw.com>	2026-08-14 22:11:24 -07:00
Dmitriy Kovalenko	6398d32c0c	fix: Do not exit MCP if the parent process is alive (#770) ... closes #703 Bumped inactivity timeout to an hour and make it actually check every minute if parent is alive and working	2026-08-13 17:39:14 -07:00
Gustav the Bot	c6194b848d	fix(mcp): declare readOnlyHint on all tools (#771) (#774) ... find_files, grep, and multi_grep only read the filesystem but declared no MCP tool annotations, so plan-mode / read-only clients blocked them. Add annotations(read_only_hint = true, destructive_hint = false, open_world_hint = false) to each #[tool]. Closes #771 Co-authored-by: gustav-fff <286169375+gustav-fff@users.noreply.github.com>	2026-08-13 08:42:55 -07:00
Joe Taber	cc289f0f93	chore: rename old fff.nvim repo refs (#762) ... * chore: point residual repo refs at dmtrKovalenko/fff Update install URLs, download targets, and docs after the GitHub rename from fff.nvim to fff. Preserve the existing Neovim package name (fff.nvim) in lazy/vim.pack snippets so upgraders keep the same install dir and lockfile identity. * chore(docs): align Neovim package name with repo basename Drop the explicit fff.nvim package name so lazy/vim.pack use fff from the repository URL. Mild migration cost for existing installs (new plugin dir + clean of the old one). Drop this commit to keep the lowest-pain name=fff.nvim install snippets from the previous commit.	2026-08-11 21:40:21 -07:00
Gustav the Bot	dd87489d6b	fix: add missing clap attribute to no_content_indexing (#754) (#765) ... The no_content_indexing field lacked its #[arg(long = ...)] attribute, so clap treated it as a positional with a SetTrue action. Debug builds panicked on any invocation; release builds exposed [NO_CONTENT_INDEXING] as a positional and rejected --no-content-indexing. Closes #754 Co-authored-by: gustav-fff <286169375+gustav-fff@users.noreply.github.com>	2026-08-11 11:28:58 -07:00
Dmitriy Kovalenko	e2cad2f09e	chore: release 0.10.3	2026-08-06 20:26:51 -07:00
Gustav the Bot	9033efb60f	fix(fff-mcp): compare CARGO_PKG_VERSION to stable release tag (#721) (#729) ... * fix(fff-mcp): compare CARGO_PKG_VERSION to stable release tag (#721) The update check compared the embedded 40-char git SHA prefix against the release tag string, which never matched a semver tag. It also hit /releases?per_page=1 (prerelease-inclusive) while install-mcp.sh is pinned to a stable tag, so the suggested installer could not silence the notice when the API returned a nightly. Compare CARGO_PKG_VERSION against /releases/latest (stable-only) with a leading `v` stripped from the tag. Closes #721 * test(fff-node): retry watch subscribe in exit test --------- Co-authored-by: gustav-fff <286169375+gustav-fff@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>	2026-07-29 18:29:52 -07:00
Vinicios Lugli	84a9cd556f	feat(mcp): expose home and fs root scanning options (#720) ... fff-core gates indexing of $HOME and / behind enable_home_dir_scanning and enable_fs_root_scanning, and every other surface (C, python, nvim, node/bun) exposes them. fff-mcp did not, so it aborts at startup whenever an editor or agent launches it from a home directory. Add --enable-home-scan and --enable-root-scan, also settable via FFF_ENABLE_HOME_SCAN and FFF_ENABLE_ROOT_SCAN. Both default off, so the guard is unchanged unless opted into.	2026-07-29 11:09:19 -07:00
Dmitriy Kovalenko	686a84959d	chore: release 0.10.1	2026-07-20 16:05:07 -07:00
Dmitriy Kovalenko	31be224223	chore: release 0.10.0	2026-07-16 12:15:31 -07:00
Dmitriy Kovalenko	a9df55d18e	feat(sdk): Expose file watcher (#674) ... * feat: Expose fff watcher * fix: Snapshots * fix: Snapshots * fix: CI cache	2026-07-16 12:14:10 -07:00
Dmitriy Kovalenko	b4590ca108	refactor: Split grep.rs into a few modules (#667) ... * refactor: Split grep.rs into a few modules * fix(git regression): Watch reflog for consistent git events burst handling	2026-07-10 02:35:44 -07:00
Dmitriy Kovalenko	1cd8d31da4	feat: Significantly faster & better per-platform optimized file walking & gitignore matcher (#645) ... * feat: Zlob walker * feat: Use outcome gitignore rules ; Conflicts: ; crates/fff-core/src/file_picker.rs ; crates/fff-core/tests/scan_correctness_contract.rs * chore: get rid of ripgrep crates in default build * refactor: use '/' as canonical internal path separator The zlob walker emits '/'-separated relative paths on every platform. Instead of converting every walked path to native '\' on Windows, make '/' the canonical internal separator throughout the index and convert native inputs to '/' on the (fewer) inbound lookup paths. Native separators are re-applied only at OS/state boundaries: - write_absolute_path nativizes for git-cache keys, frecency, Win32 APIs - frecency keys additionally canonicalize on Windows (dunce), with a raw-string fallback so watcher deletes never drop the op Removes several scattered Windows compensations (score.rs fuzzy folds, constraints.rs collect fold) now that stored paths are already '/'. relative_path emitted to Lua is now '/' on all platforms.	2026-07-02 15:39:47 -07:00
Gustav the Bot	03e1a1a15e	feat: expose follow_symlinks for SDK/MCP/python paths (#628) ... * feat: expose follow_symlinks for SDK/MCP/python paths Closes #627 Bumps FFF_CREATE_OPTIONS_VERSION to 2 (append-only). Adds --follow-symlinks flag to fff-mcp, follow_symlinks kwarg to the pyo3 finder, and followSymlinks option to @ff-labs/fff-node. Default stays false everywhere; follow_symlinks is preserved across reindex in C and Python. Watcher cycle handling is unchanged — caller must ensure the indexed tree has no symlink loops. * fix build --------- Co-authored-by: gustav-fff <286169375+gustav-fff@users.noreply.github.com> Co-authored-by: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com>	2026-06-26 16:58:55 -07:00
Gustav the Bot	b55a566da0	fix(mcp): self-exit after idle timeout (prototype for #633) (#634) ... * fix(mcp): self-exit after idle timeout to mitigate orphan processes Some MCP clients (e.g. Claude Code) spawn fff-mcp per session but don't close stdin on session end, leaving orphan processes consuming CPU (#633, #497). Add an idle watchdog: each tool call bumps a last-activity timestamp, a background task ticks every 60s and exits(0) after --idle-timeout-secs (default 900) without activity. Set to 0 to disable. Also configurable via FFF_MCP_IDLE_TIMEOUT_SECS. Stopgap before the daemon-based process model. Notifications/pings do not count as activity, so a chatty-but-dead client cannot keep the process alive forever. * fix: cleanup --------- Co-authored-by: gustav-fff <286169375+gustav-fff@users.noreply.github.com> Co-authored-by: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com>	2026-06-26 16:18:36 -07:00
Dmitriy Kovalenko	28321da228	chore: release 0.9.6	2026-06-21 11:48:22 -07:00
Dmitriy Kovalenko	797c045aa9	chore: release 0.9.5	2026-06-18 09:21:34 -07:00
Dmitriy Kovalenko	7d7910b6ba	chore: release 0.9.4	2026-06-09 15:35:38 -07:00
Dmitriy Kovalenko	8092cfa3fa	chore: release 0.9.3	2026-06-05 23:44:39 -07:00
Dmitriy Kovalenko	8da90c6a93	chore: release 0.9.2	2026-06-05 23:23:38 -07:00
Dmitriy Kovalenko	b27368a0e6	fix(nvim): do not error on home dir scan + improve logging (#575) ... Doing more expanding on log and more deliberate sigsegv handling	2026-06-05 21:32:45 -07:00
Dmitriy Kovalenko	1e055f9d7b	chore: release 0.9.1	2026-06-04 01:26:32 -07:00
Dmitriy Kovalenko	a0a93f2093	chore(ci): Bump the version not bumped automatically	2026-06-02 17:00:05 -07:00
Dmitriy Kovalenko	c1a1ea6c2c	chore: release 0.9.0	2026-06-02 16:38:55 -07:00
Dmitriy Kovalenko	5bdc727e6d	feat(sdk): Expose glob public api (#541) ... * feat(sdk): Expose `glob` public api also allow to configure the abillity to run fff in the home dir or file sytsem root * fix(ci): clippy lints + missing test-c-api Make target - constraints.rs: drop redundant deref, fix GlobPattern type alias for non-zlob build - file_picker.rs: use vec! macro for single-element ConstraintVec init (clippy) - Makefile: add test-c-api alias to test-c-smoke for external-tests workflow - glob-bench.ts: pageSize=100 (realistic, avoids JS marshaling overhead)	2026-06-02 13:32:47 -07:00
Dmitriy Kovalenko	030a583b37	chore: release 0.8.4	2026-05-25 11:50:08 -07:00
Dmitriy Kovalenko	21a3078f69	chore: release 0.8.3	2026-05-25 09:22:18 -07:00
Dmitriy Kovalenko	5c3a615e76	chore: release 0.8.2	2026-05-23 19:28:56 -07:00
Gustav the Bot	c84db53454	fix: Upgrade rmcp to 1.7.0 for Content-Length framed stdio (#388) (#505) ... Refs #388 Co-authored-by: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com>	2026-05-22 11:02:34 -07:00
Gustav the Bot	16b34f5eec	fix: add follow_symlinks option (#375) (#507) ... Expose follow_symlinks configuration option for following symbolic links during file indexing. - Add follow_symlinks field to FilePickerOptions (default false) - Thread option through FilePicker, ScanConfig, walk_filesystem - Add lua config: vim.g.fff.follow_symlinks (default false) - Pass config from lua -> rust FFI init_file_picker Root cause: WalkBuilder.follow_links() hardcoded to false at file_picker.rs:1738 Refs #375 Co-authored-by: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com>	2026-05-20 12:18:03 -07:00
Dmitriy Kovalenko	6645a68ebc	chore: release 0.8.1	2026-05-15 16:41:12 -07:00
Dmitriy Kovalenko	97c1812668	chore: release 0.8.0	2026-05-15 14:58:41 -07:00
Dmitriy Kovalenko	1104a8deaf	fix: LMDB stale readers and automatic compactions (#468) ... * fix: LMDB stale readers and automatic compactions closes https://github.com/dmtrKovalenko/fff/issues/460 * chore: Update docs for - fix: LMDB stale readers and automatic compactions * chore: Fix CI - typos, rustfmt, stylua, lls	2026-05-12 16:55:51 -07:00
Dmitriy Kovalenko	ff817190d3	chore: release 0.7.2	2026-05-07 10:11:57 -07:00
Dmitriy Kovalenko	e8dd50ce5a	chore: release 0.7.1	2026-05-05 16:11:46 -07:00
Dmitriy Kovalenko	4c5c92ac38	chore: release 0.7.0	2026-05-03 18:18:11 -07:00
Dmitriy Kovalenko	52b1e86b63	fix(mcp): accept 'pattern' as an alias for 'query' on grep/find_files ... multi_grep uses 'patterns' while grep/find_files use 'query'; LLMs routinely confuse the two and trip on 'missing field `query`' (#311). Add a serde alias so the wrong-but-intuitive name also works without changing the published JSON schema.	2026-05-03 16:44:31 -07:00
Dmitriy Kovalenko	362ba12517	fix(mcp): treat maxResults=0 consistently across tools ... Previously 'maxResults: 0' was asymmetric: grep/multi_grep truncated the output list to zero items while find_files interpreted 0 as 'unlimited' and returned the full (potentially huge) result set. Centralize the parsing through normalize_max_results() and treat 0 (plus negatives and non-finite values) as 'use the default'. Also round fractional values instead of truncating (0.4 → 1, 10.7 → 11). Fixes #400 (issue 3).	2026-05-03 16:44:31 -07:00
Dmitriy Kovalenko	f401061fa6	fix(mcp): stop surfacing regex-fallback warning alongside matches ... When a grep pattern like 'foo(' triggers regex compilation and fails, the core engine already falls back to literal matching and returns the correct results. Prepending '! regex failed: ...' on top of those results only confuses LLM callers (issue #425) — they see the error before the matches and conclude the call failed. Drop the warning from the formatter output entirely; the core still populates the field for debugging and other bindings.	2026-05-03 16:44:31 -07:00
Dmitriy Kovalenko	24a4a7ae75	fix: bound LMDB growth + deprecate unsafe no-lock mode (#441) ... * fix: bound LMDB growth + deprecate unsafe no-lock mode Adds runaway-growth safeguards (closes #437) report of multi-GB frecency cache. Deprecates the old unsafe_no_lock mode. Refs: #437 * chore: Update docs for - fix: bound LMDB growth + deprecate unsafe no-lock mode	2026-05-03 15:01:12 -07:00
Dmitriy Kovalenko	1bcbce2bc6	feat: Improve stability of file search discovery in background (#431) ... * feat: Improve scan runtime performance and RSS * chore: Comprehensive randomized fuzzy mutation testing It's such a shame that we keep commiting regressions that are leading ot the missed events from the file watcher. I want to minimize this to 0. * chore: Update docs for - chore: Comprehensive randomized fuzzy mutation testing * chore: Update docs for - chore: Update docs for - chore: Comprehensive randomized fuzzy mutation testing * test: Verbose stress test output	2026-05-02 09:28:14 -07:00
Dmitriy Kovalenko	84ba575a3f	feat(pi-fff): Improve instructions and add more features (#414) ... * feat(pi-fff): Improve instructions and add more features So what I've done is simple: I run autoresearch to fine tune the prompts for the best results, then thrown it all away cause autoresearch is a fucking trash and manually fine tuned by running "analyze X" in various repos and asking AI what went wrong * chore: Update docs for - feat(pi-fff): Improve instructions and add more features * chore: Update docs for - chore: Update docs for - feat(pi-fff): Improve instructions and add more features	2026-04-26 12:47:22 -07:00
Dmitriy Kovalenko	4b13a91aa5	chore: release 0.6.4	2026-04-22 12:41:32 -07:00
Dmitriy Kovalenko	1b79eecb58	chore: release 0.6.2	2026-04-22 10:35:22 -07:00
Dmitriy Kovalenko	8f23da638b	chore: release 0.6.1	2026-04-19 13:47:48 -07:00
Samuel Huber	cfea91ce88	feat: Official pi fff extension (#374) ... * feat: add pi extension for FFF file search Add @ff-labs/pi-fff package providing pi coding agent integration: - Overrides built-in find/grep tools with FFF-powered versions - Adds multi_grep tool for SIMD-accelerated multi-pattern search - Replaces @-mention autocomplete with FFF frecency-ranked suggestions - Commands: /fff-health, /fff-rescan, /fff-mode (with immediate switch) - Streamlined implementation: 26% code reduction (800→590 lines) Published as pi package: npm:@ff-labs/pi-fff * docs: fix install instructions - Remove git install option (doesn't work for monorepo subfolders) - Remove config file from mode precedence (no longer used) - Keep npm as only recommended install method * feat: add root pi manifest for git installs Add pi configuration to root package.json pointing to packages/pi-fff. This enables: pi install git:github.com/dmtrKovalenko/fff.nvim The root stays private (not published to npm), but pi can now discover the extension from the git repo structure. * docs: add git install instructions Now that root package.json has pi manifest, git installs work: pi install git:github.com/dmtrKovalenko/fff.nvim * fix: address PR review feedback - Add config file persistence for /fff-mode (fixes 'persist' claim) - Add readConfigMode() and writeConfigMode() helpers - Use applyEditorMode() in /fff-mode command (DRY) - Add publishConfig.access: 'public' for npm publishing - Fix @types/node to ^22.0.0 (align with repo) - Remove ignoreCase parameter (FFF doesn't support force case-insensitive) - Run Biome formatter (fix tab indentation) * update toolnames and add to release pipeline * do not override default tools * Make an option to override the default tools * fix: macos tests * better toolnames mangement --------- Co-authored-by: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com>	2026-04-19 13:44:08 -07:00
Dmitriy Kovalenko	2465c2cad6	chore: release 0.6.0	2026-04-18 17:01:43 -07:00