Skip to content

Pathfinder v0.1.6

Latest

Choose a tag to compare

@skuttlebot skuttlebot released this 12 Nov 23:16
· 3 commits to main since this release
Immutable release. Only release title and notes can be modified.
c1109c2

Pathfinder v0.1.6

Release notes for changes since v0.1.5, prepared on 2026-11-12.
Published packages are built by GitHub Actions from the v0.1.6 tag.

Summary

  • Scan exclusions: choose folders to leave out of scans from a folder tree,
    or skip a file's folder right from the graph or the Reconcile list. Excluded
    files leave the graph cleanly instead of turning missing.
  • A redesigned graph UI: teal theme, regrouped top bar, canvas controls, a
    single filter panel, a project overview in the inspector, and a status bar.
  • Lighter change requests: step-by-step progress tracking, optional
    verification, plain-description drafts, and fewer rescan-related blocks.
  • Portable MCP setup: client configs are no longer committed, and broken
    or foreign entries can be detected and repaired.

Scan exclusions

Open Project ▾ → Scan exclusions…, also available in Project settings…,
to see the project's folders as a tree read from disk, each with its file count.
Tick a folder to exclude it and everything beneath it. Changes are staged and
the footer shows how many files will be removed or added back. Nothing is
written until Apply & rescan.

On the rescan, nodes for excluded files are deleted together with their symbols
and connections, so they never show up as missing in the Reconcile list. Any
description, comment or tags on those nodes are deleted too. Untick a folder and
apply again to bring its files back as freshly scanned nodes.

To skip noise where you see it, use Skip folder on a node's right-click
menu, the Skip folder… button in the inspector, or the button on each
Reconcile row. They offer the file's parent folders (or just that file) and open
the tree with your choice ticked.

Rules are stored in a plain-text .pathfinderignore file at the project root
using .gitignore syntax, so they can be committed, shared, and edited by hand.
Advanced patterns in the panel accept globs and negation (*.vsix,
/review.md, !CLAUDE.md). Rules that no longer match anything are flagged
stale. Built-in skips such as node_modules, .git and other dot-folders
still always apply.

From the command line, use pathfinder ignore list|add|remove <path> [folder_or_pattern]. Changing exclusions is deliberately not exposed as an MCP
tool: what gets scanned stays a human decision.

Graph UI revamp

  • The top bar groups project, branch picker, Explore, Compare, Plan, Settings,
    Export, Help and search.
  • Canvas controls cover 3D/2D, centering, filters, display and the legend.
    Filters are one panel with Nodes, Connections, Admin and Tags rows.
  • With nothing selected, the inspector shows a project overview. With a node
    selected, it shows collapsible sections with Focus, Deep dive and Reconcile
    actions.
  • A status bar shows counts, the current git branch, operation timings, the
    last scan time and Rescan. The git branch is read from .git/HEAD; Pathfinder
    never runs git.
  • The default view and whether the legend opens are saved per browser in
    Settings.

Change requests

  • Steps can be marked pending, in progress, done, blocked or skipped from the UI
    or the MCP step_progress action. Each step can carry a longer detail and
    shows as an expandable card with a progress summary.
  • Closing a request only requires every step to be done or skipped. Validation
    evidence, scope review and a fresh scan are shown as advisories but no longer
    block closure.
  • Drafts can start as a plain description. Submitting still requires at least
    one change, one step and one validation.
  • A rescan only blocks approval or starting work when it changed a file inside
    the request's scope. Otherwise the baseline moves forward automatically.
  • MCP write tools return a compact summary by default. Pass verbose: true for
    the full request.

MCP integrations

  • .mcp.json, .vscode/mcp.json and .codex/config.toml hold paths specific to
    one machine. They are no longer tracked in git; each machine enables the
    integration once.
  • pathfinder integrations list marks broken entries, and pathfinder integrations repair fixes their command and arguments for the running
    install. The graph UI and the VS Code extension offer the same Repair action.

Validation and upgrade notes

  • The development test suite passed on 2026-11-12: 149 tests, no failures or
    skips, including new scan-exclusion unit, scan, and server API tests. The scan
    exclusions UI was also exercised end to end in Chromium.
  • Before tagging, all four archives (Windows x64, Linux x64, macOS Intel, macOS
    Apple Silicon) were built locally with scripts/package.js. The Windows
    packaged executable passed the smoke test and was checked with ignore add,
    scan and report on a sample project.
  • The release workflow builds each platform on its own runner and smoke-tests
    the Windows executable. Linux and macOS packages are built but not
    runtime-tested by the workflow. macOS packages remain unsigned; see the
    first-launch steps in the releases README.
  • MCP client setup moved to Settings → Configure MCP clients… with the UI
    revamp.
  • Restart Pathfinder and any connected AI client sessions to load the new code.
  • Projects without a .pathfinderignore scan exactly as before.
  • The new ignore npm dependency implements .gitignore matching.