Skip to content

Pathfinder v0.1.7

Latest

Choose a tag to compare

@skuttlebot skuttlebot released this 20 Nov 22:02
· 1 commit to main since this release
Immutable release. Only release title and notes can be modified.
43139ed

Pathfinder v0.1.7

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

Summary

  • Parallel change requests: several requests can now be in flight at once.
    Rebase, park, withdraw or supersede a request, see overlaps with other
    requests, and declare prerequisites.
  • Plans that came true are recognised: planned connections in change
    requests and hand-drawn planned edges now match the real relationships the
    scanner finds, instead of being reported as not found.
  • MCP integration monitor: a status-bar chip shows whether each AI client
    is connected properly and flags broken setups.
  • Polished rendering: shaded nodes, depth fog and depth-aware edges make the
    3D view easier to read, and it draws faster.

Parallel and deferred change requests

Change requests no longer assume they run one at a time.

  • Rebase moves a request's baseline forward to the latest scan. An AI
    agent can do a clean rebase itself; a human is only asked when the scan
    actually changed something inside the request's scope.
  • Park / unpark sets a request aside without losing its state.
  • Withdraw or supersede a request that is no longer wanted or has been
    replaced by another.
  • Overlaps warn when two open requests touch the same files. These are
    advisories; Pathfinder does not lock files to a request.
  • Prerequisites record that one request must land before another.
  • Changes outside every request's scope are attributed by scope, so drift from
    unrelated work no longer blocks a request.
  • The available lifecycle actions are now decided by the server and shown in a
    sticky Lifecycle header in the request panel, so the UI and MCP tools
    always offer the same choices.
  • Rescan is now a red button in the top bar.
  • Proposed nodes in the change-request overlay are placed among the nodes their
    planned edges connect to, instead of near one anchor at the edge of the map.

Planned edges that became real

  • A planned connection (planned_connection) is satisfied by any real
    relationship in the same direction. A plan between two files is also
    satisfied by calls between symbols inside those files.
  • Change-request verification no longer reports these as not found.
  • When a scan confirms a hand-drawn planned edge, the placeholder is retired and
    its description and comment move onto the real edge.
  • Change requests that name an edge type the scanner never produces are
    rejected up front, so a plan cannot be impossible to verify.
  • Known limit: calls made through injected attributes (for example
    self.service.client.send()) are not yet detected by the scanner, so plans
    that depend on them still show as not found.

MCP integration monitor

  • Each AI client integration is reported in one of several states, including
    broken configuration and orphaned instructions (setup text that points to a
    Pathfinder server the client no longer has).
  • A chip in the status bar shows the overall state and opens the integrations
    window. It re-checks when the window regains focus and on a timer.
  • Pathfinder records which MCP tools were called and when in
    .pathfinder/mcp-activity.json. Only tool names and times are stored, never
    arguments or results.
  • GET /api/integrations/health returns the states.
    pathfinder integrations list exits with code 1 when any integration needs
    attention, so it can be used in scripts.

Graph viewer

  • Nodes are drawn from cached shaded sprites, glow only marks state, the 3D
    view adds depth fog, and edges use depth-aware gradients within a fixed
    budget. Large graphs draw noticeably faster.
  • Nodes behind the camera target shrink and fade more, which makes 3D depth
    easier to read.
  • Compare defaults From to the scan before the latest. Closing Compare
    clears the diff overlay and sidebar.

Validation and upgrade notes

  • The development test suite passed on 2026-11-20: 184 tests, no failures or
    skips, including new tests for change-request lifecycle actions, edge
    matching, the integration monitor, MCP activity logging and node styling.
  • 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.
  • Restart Pathfinder and any connected AI client sessions to load the new code.
  • Existing change requests keep working. Hand-drawn planned edges that the code
    already satisfies are retired on the next scan.