Skip to content

Seek 0.3.0

Choose a tag to compare

@SynrgStudio SynrgStudio released this 08 Nov 16:09

Install it, and add it to Claude Code and Codex when they are on this PC, from PowerShell:

irm https://raw.githubusercontent.com/SynrgStudio/seek/main/install.ps1 | iex

Running it again updates Seek, with agent sessions open too: they get the new version from their next call.

Or download seek.exe, put it anywhere, and give its full path to your MCP client as a stdio server with no arguments. It isn't signed yet: Windows may warn you the first time.

Built from this release's commit, with the tests passing.

SHA-256  a58414d6697f4066c315d065a8f2ca41e6d635f56988e3c438bd178525dd51d7  seek.exe

What changed

The second half of the review: what it suggested.

  • A session's tool calls run at the same time, each on a thread and a connection of its own. Before, a session's calls were served one after the other, so a find sent during a slow grep waited for it (#13).
  • find follows a renamed folder: what is inside is walked (with a budget) and counts as created since the index, and what the index lists under the old name is hidden. Before, after mv old new nothing inside new could be found until the index was renewed (#16).
  • A drive whose watcher couldn't start (a BitLocker drive still locked, a drive that appears later) is tried again every five minutes. Before, its changes went unseen until the background process restarted (#15).
  • grep searches a file over 16 MB when it is the path given, reading it in parts along line boundaries, with the line numbers and the context as if it were read whole. The limit stays for the files met on a walk of a folder, which are named as not read (#8).
  • seek --status says how the background process is: each drive's index, its age and names; what was created and deleted since; the drive watchers and the batches they lost; the folders kept in memory for grep; and whether Jolt's index is used (#14).