Updating Seekter

Seekter improves in releases, and every release is written up in the changelog. Updating to the latest release takes a minute. Your own data never gets in the way of an update: profile/, applications/ and runs/ are yours, git-ignored, and no release ships anything inside them.

Which Version You Have

The version is a git tag, not a file:

git describe --tags

If you installed with npx, there's no git history; the newest entry at the top of your CHANGELOG.md is your version.

If You Cloned the Repository

git pull

Your folders are ignored by git, so the pull never touches them.

If You Installed With npx

npx seekter init only fills a new or empty folder, so it never writes over your work. Put the new release next to the old one:

npx seekter init seekter-new

Then move your three folders from the old one into it:

mv seekter/profile seekter/applications seekter/runs seekter-new/

Before you open the new folder, check whether your runs taught the old one anything. Runs write what they learn about forms and sources into reference/, and the new folder has the release's version of those files, not yours:

diff -r seekter/reference seekter-new/reference

Nothing listed means nothing to carry. Lines that only your copy has are lessons from your own runs. Copy those lines into the new files by hand (copying whole files would undo the release's own changes), and consider sending them upstream so the next release has them.

Then open Claude Code in seekter-new and carry on. Keep the old folder until the first run in the new one has gone well.

You can also download seekter.zip from the latest release and do the same.

Read the Upgrading Note

Every changelog entry ends with an Upgrading paragraph. It's almost always "nothing to migrate". When it isn't, it says exactly what to do: a new Node.js version, a settings key worth adding, a file worth moving.

A key added to templates/settings.json in a new release runs on its default until you set it. To see which values are still defaults:

node scripts/seekter.mjs settings --check

Your Own Changes

A run sometimes teaches the kit something: a new form trap goes into reference/, a rule goes into a skill.

• Cloned: those edits are in tracked files, so a git pull can meet them. Ship them back with /seekter-git before you update, and everyone gets the lesson.
• Installed with npx: there is no git to ship them with. Compare the folders as above before you move, and send what's new as an issue.