Skip to content
Castellan

All release notes

Reeve: release notes

Each version, newest first.

0.12.5

It carries the Steward's kit 2.36.1: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.36.1: GenieX 0.8.0 is the NPU's server on a Snapdragon.

Before you update

  • Nothing: it updates itself as usual. This kit comes after 2.36.0; 2.33.0 (Steward 0.19.4) is still to be released and doesn't depend on it.

0.12.4

It carries the Steward's kit 2.35.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.35.0: A release of an agent Castellan sells goes to the Exchequer, and no longer to the public releases repository.

Before you update

  • Nothing: it updates itself as usual. Agents for sale stop appearing in the public releases repository once the Exchequer 0.6.0 is deployed with its migration applied. Until then, releases go there as before.

0.12.3

It carries the Steward's kit 2.34.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.34.0: An agent's rounds never stop silently.

Before you update

  • Nothing: it updates itself as usual. This kit comes after 2.33.0 (Steward 0.19.4); if 2.33.0 isn't released yet, release it first.

0.12.2

Reeve carries the Steward's kit 2.32.1, which names the app you bought: Castellan.

What changed

  • The Steward's kit 2.32.1: the kit names the app the person bought, Castellan. A message that said Manor now says Castellan's Settings: when the graphics card is kept out while the NPU serves, Reeve's log says so in those words. What it does is unchanged.

Before you update

  • Nothing: it updates itself as usual.

0.12.0

What's new

  • The NPU is used whoever made it: GenieX on a Snapdragon, OpenVINO Model Server on an Intel Core Ultra, FastFlowLM on an AMD Ryzen AI 300 and later. Castellan's Set up local AI (or the Smith's Set up, or accelerators setup) installs its server and models; you no longer install GenieX and pull its model by hand.
  • accelerators names the NPU's maker and generation, and says plainly when the manor can't use it.

What changed

  • The model setup (the accelerators, their order and idle times) is read from %USERPROFILE%\.manor\accelerators\config.json once it exists; Reeve's own settings stay in his config.json. Without the Smith, accelerators setup writes there too.
  • install no longer points Reeve at GenieX unless GenieX is installed on a Snapdragon; otherwise it says to run Set up local AI.
  • The messages that said "Reeve isn't set up" now point to Castellan's Set up local AI.
  • A manor whose settings give it no name is called Castellan, the product's name, on Reeve's page and in the manor tool, as on every agent's title bar (the Steward's kit 2.32.0).

Before you update

  • Nothing to do: the model setup is copied from Reeve's config.json into Manor's folder, word for word, the first time the Smith (or Reeve's keeper) reads it; Reeve's file is left as it was. The Steward's kit 2.32.0 must be released first.

0.11.3

It carries the Steward's kit 2.29.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.29.0: Every agent's page fits a phone: the title bar's action and wide tables no longer push the page sideways.

Before you update

  • Nothing: it updates itself as usual.

0.11.2

Its worktree tidy clears every worktree whose work is safe elsewhere, and says what it's waiting on.

What changed

  • worktree-tidy also removes a clean worktree whose commits were rebased or cherry-picked into the default branch (the same changes, new commits), after 2 idle days as before.
  • It also removes a clean worktree whose commit is pushed to one of origin's branches but not merged (its pull request still open, or closed), once it has been idle for 7 days. Only the folder goes: its branch stays, here and on GitHub.
  • Its result now counts the worktrees that will go once idle long enough, so a round that removes nothing says why.
  • A worktree with uncommitted changes, or a commit only on this PC, is still never removed: git-hygiene names it for you.

Before you update

  • Nothing: it updates itself as usual. The changed worktree-tidy script waits for approval before it runs, as any changed job does.

0.11.1

Approve a job on the home page: read its script, check its fingerprint, press Approve. No terminal.

What's new

  • Approve under Needs you. Each job waiting for approval now shows what it does, why it waits (a new script, or one changed since you approved it), a View the script link that opens its text, read-only, and the script's SHA-256 fingerprint (beside the one approved before, when it changed). Approve approves exactly that script: if it changed after the page showed it, nothing is approved and the page says so.
  • A job that changes your repositories has a card and an Approve of its own, so it's never approved along with others. The jobs that only read can also be approved together, with Approve all read-only jobs.

What changed

  • Reeve's page, its install and its messages no longer ask you to run a command to approve a job: they point to Needs you. Once approved, a job's "needs approval" warning goes away at once, and it runs at its next round.
  • The Accelerators card points to Settings → Set up only.

Before you update

  • Nothing: it updates itself as usual. Jobs already approved stay approved.

0.10.1

It names no folders of one particular PC.

What changed

  • Its entry for Manor (manor-agent.json) no longer names a Node in a folder only one PC has: it runs on Manor's own Node, or one installed in the usual place.
  • It looks for the GitHub CLI on PATH and where its installer puts it, no longer in a folder only one PC has; its scheduled rounds, should the Node that installed them be gone, fall back to the usual Node folder.
  • The README's examples use your own folders, not one PC's.

Before you update

  • Nothing: it updates itself as usual.

0.10.0

Safer repository jobs: nothing that could be lost is removed, and on a new PC the jobs that change your repositories wait for you to turn them on.

What's new

  • The four jobs that change your repositories (fast-forward, repo-sync, worktree-tidy and project-branches) each have a switch: Turn on and Turn off on the home page's Jobs, or reeve jobs on <name> and reeve jobs off <name>. On a new install they start off. Once you turn one on, its first run is a dry run whose report says exactly what it would do, and changes nothing; it acts from the run after. One that is off can still show you what it would do: Dry run on the home page.
  • Each of those jobs is approved on its own, after you read its script: Needs you gives each its own command, and reeve jobs approve won't approve one together with other jobs. The jobs that only read are still approved together.
  • Delete merged branches on GitHub too, a new setting (advanced) in Settings: the GitHub repositories of Manor's non-employee projects whose merged branches Reeve may also delete on GitHub. Empty unless you list some.

What changed

  • worktree-tidy no longer removes a worktree holding git-ignored files such as a .env, a local database or a local config: removing the folder would have deleted them with it. It keeps such a worktree and names the files in its report. Build output (node_modules, dist, build, bin, obj, .next, coverage, __pycache__, .venv, target and the like) doesn't count.
  • worktree-tidy no longer touches the agents' own working folders (Reeve's checkouts, the Steward's and the Wright's work folders). Before removing a worktree it finds the links inside it however deep they sit, so a deep node_modules link never takes what it points to with it.
  • project-branches no longer deletes branches on GitHub unless you list the repository in the new setting, and then only a branch whose pull request was merged at the commit the branch is at now. It never deletes one just because its commits are already on main, which a teammate's brand-new branch can be. Merged branches on this PC are still tidied as before.
  • fast-forward leaves alone a checkout with files marked assume-unchanged or skip-worktree, whose local edits git hides, and says so.
  • reeve checkout --dir only works on Reeve's own checkouts, in its checkouts folder. It refuses any other folder rather than reset and clean it.
  • The jobs read git's messages in English on every PC, whatever Windows' language.
  • docs-refresh refuses a package name or version in a lockfile that isn't one (a version that is a path, say), so a crafted lockfile in any repository can't make it write or delete outside Reeve's docs folder.
  • npu-health no longer warns every hour on a PC without an NPU: it says there is nothing to watch.
  • The copies of text you hand to triage are deleted after 14 days instead of kept for good.

Before you update

  • Your jobs keep their settings: on a PC where Reeve already ran his jobs, the four that change repositories stay on, with no dry run, and anything you paused stays paused. New installs start with them off.
  • One change you may notice: project-branches stops deleting merged branches on GitHub until you list the repository under Delete merged branches on GitHub too in Settings.
  • Five job scripts changed (fast-forward, repo-sync, worktree-tidy, project-branches and npu-health), so each waits for approval again before it runs: read it, then approve it.

0.9.2

It carries the Steward's kit 2.28.1: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.28.1: Security fix: a value with curly quotes in it could break out of a PowerShell string.

Before you update

  • Nothing: it updates itself as usual.

0.9.1

A fix to the Claude Code setup line on Reeve's page: it pastes into PowerShell exactly as shown, whatever your folders are called.

What changed

  • Connect your AI to Reeve gives Claude Code a command to paste. A folder name with curly quotes in it (‘ ’ ‚ ‛, which PowerShell treats as quote marks), or with characters like ;, & or $, could end the quoted path early when pasted into PowerShell, and run the rest as a command. Each path in it is now quoted so PowerShell reads it back exactly.

Before you update

  • Nothing: it updates itself as usual.

0.8.0

Kept off the cloud: see how many tokens Reeve read so your AI assistant didn't have to, and roughly what that saved.

What's new

  • Kept off the cloud, a new card on Reeve's home page: the tokens Reeve read on this PC on your AI assistant's behalf (the logs he triaged, the files he summarized or asked about, the docs passages and code he read), this month, last month and all time, with about what they'd have cost and what each tool read. Everything is an estimate and says "about", counted conservatively: only what Reeve read from your PC, less what he sent back, with big inputs capped and repeated calls counted once.
  • What your AI assistant's model costs per million input tokens, a new setting in Settings: the price the card counts at, $3.00 until you change it. On a plan rather than paying per token, you save usage limits rather than money.
  • The status tool ends with the same totals in one line, and the home page offers them to Manor and other tools on your PC.
  • Only counts are kept (per day and tool, older days rolled into months): never your files, logs, questions or answers.

Before you update

  • Nothing: it updates itself as usual. The count starts with this version: calls made before it aren't counted.

0.7.1

It carries the Steward's kit 2.28.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.28.0: Required settings: an agent that can't work without something from you waits for it, and onboarding asks for it.

Before you update

  • Nothing: it updates itself as usual.

0.7.0

Reeve is the local AI layer, and his page says so: connect your AI to him from it, and see every repository's pull requests, worktrees and space on one screen.

What's new

  • Connect your AI to Reeve. Reeve is an MCP server: his page now has the setup for Claude Code, Claude Desktop, Cursor, Gemini CLI, VS Code and Codex, with this PC's own paths, ready to copy, and the line to put in your AI's instructions so it asks Reeve before reading big files, logs or docs itself.
  • At a glance, at the top of the page: how the jobs went, how much needs you, and new alerts with Mark seen.
  • Pull requests on the Repositories board. Each repository on GitHub shows its open pull requests and how many wait on you. Details lists them with what each waits for (ready to merge, needs review, checks failing, conflicts, draft…), and Refresh pull requests asks GitHub again. Reeve only reads them: the Steward still merges the team's.
  • Each repository's worktrees and merged branches, under Details: every worktree with its size, when it was last used and why one has to stay, and the local branches already merged, from Heiward's developer check.
  • Where the space has gone, above the repositories: the disk your worktrees, build outputs, package caches and temporary files take, from Heiward's developer check, with Clean up in Heiward. This was meant to arrive in 0.6.4 and didn't; this release brings it.
  • Your projects from Heiward. Repositories you bundled into a project on Heiward's page sit together on the board, with each project's space, pull requests and merged branches added up.

What changed

  • The page is reorganized: the jobs come first, then what needs you; a job's warning shows its summary with what it went through folded; long job summaries are cut to two lines; and the repository groups fold to one line (a long one starts folded, and your browser remembers).
  • On a phone, wide tables scroll inside themselves instead of the whole page.
  • Reeve now introduces himself as the local AI layer: a model on this PC that knows your repositories and does the reading for stronger AI models.

Before you update

  • Nothing: it updates itself as usual. Pull requests show when the GitHub CLI (gh) is installed and signed in; the space, worktrees and projects when Heiward is hired and his developer area is on.

0.6.11

Each accelerator is called what your PC calls it. It carries the Steward's kit 2.27.0.

What changed

  • The NPU, each graphics card and the processor are named from what Windows calls them, the way Manor shows them: by the model alone, without (R), (TM) or a last "NPU", "CPU" or "GPU": "Qualcomm Hexagon", "Qualcomm Oryon", "Qualcomm Adreno X2-90". A name kept in config.json is no longer used; it was never meant to be set by hand.
  • The Steward's kit 2.27.0: An accelerator's name is what the PC calls it, never a setting.

Before you update

  • Nothing: Manor updates it as usual. A name in config.json from before is ignored, and taken out the next time the file is saved.

0.6.10

Its page is drawn from smaller parts.

What changed

  • The page's code is split into smaller components, so it is easier to keep right. It looks and works as before.

Before you update

  • Nothing: it updates itself as usual.

0.6.8

Reeve updates again: 0.6.7's release was stopped by its own earlier publishing, and this one brings it.

What changed

  • Reeve 0.6.7 couldn't be released: it had been published already by an earlier attempt, and the next attempt, which builds the release afresh, found the files there different from its own and stopped. Two builds of the same version never come out byte for byte alike (each records when it was built), so 0.6.7's check for "the same files" could only recognise the very same build. Now a release found already published counts as published when it was built from the same commit, with its files whole; one from another commit is still an error, since a version is only ever published once.
  • This release brings 0.6.7's change too.

Before you update

  • Nothing: Manor updates it as usual.

0.6.7

Publishing a release that's already out with the same files no longer counts as a failure.

What changed

  • When Reeve 0.6.5 was released, it was published once, and then a second attempt found it already there and failed ("a release with the same tag name already exists"). The Steward then reported Reeve's release as failed though it was out. Now, when publishing finds the release already there, it compares that release's files with the ones just built. The same files count as published; other files are still an error, since a version is only ever published once.

Before you update

  • Nothing: Manor updates it as usual.

0.6.5

Reeve updates again: 0.6.3 couldn't be installed, and this one brings it.

What changed

  • Reeve 0.6.3 moved its page to the one every agent shares, but its installer still looked for the old page's files. So it refused its own release ("This release is incomplete (no dashboard/dist/index.html)"), and Manor's update to 0.6.3 failed every time. The installer now checks for the page Reeve actually ships.
  • Building a release now runs the same check before it makes the zip, so a release its own installer would refuse can't be published again.
  • This release brings everything in 0.6.3 (below), which reached no one.

Before you update

  • Nothing: Manor updates it as usual. If Manor still shows "Updating Reeve to 0.6.3 failed", it clears once Reeve is on 0.6.5.

0.6.3

Reeve's page looks and works like every other agent's: a shorter Settings page, and a tour for new hires.

What's new

  • A tour. When Manor hires Reeve it offers his tour: what he does, where your repositories are, then his page, section by section. Open it again any time at #/tour.
  • The manor's page frame. The title bar, on and off duty, the theme and Back to Manor are the same as on every agent's page.

What changed

  • Settings is short. It has your repositories (where Reeve looks, others, and the ones left alone), plus the request timeout and Foundry Local's idle time under Advanced. The accelerators stay on the Smith's page, and the note at the top sends you there.
  • Gone from Settings: the Foundry Local fallback's model names and command, the search index's size, and who raises the toast. A value you set in config.json still counts.
  • Notifications follow Manor: Reeve raises no toast while Manor's Notify me is off or during its quiet hours.
  • An empty search-folder list means the usual folders on this PC, as no list did before.
  • Reeve's role no longer says "on the NPU": his model runs on whatever accelerator this PC has.
  • Jobs that only fit one PC are gone: test-phone (a particular phone), maestro-runs and aletaster-orders. reeve triage still reads a Maestro run when asked.
  • The Steward's kit 2.26.0.

Before you update

  • Nothing: it updates itself as usual. Your settings are kept. The three jobs that went stop running; their old results are left where they were.
  • Manor 0.6.2 or later adds Notify me and quiet hours. With an older Manor, toasts work as before.

0.5.8

It carries the Steward's kit 2.26.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.26.0: The kit names no one's GitHub account, private repository or folder.

Before you update

  • Nothing: it updates itself as usual.

0.6.1

No one's folders or private links: Reeve looks where your repositories are.

What changed

  • Fast-forward, Git hygiene and Worktree tidy no longer fall back to one fixed folder when reeve repos can't answer: they look at no repositories that run, and their result says why.
  • The dashboard's "Taking turns" explains the shared model queue in words, instead of linking to a page you may not be able to open.
  • The descriptions of where reeve repos looks no longer name one PC's folder: it looks in the usual folders (source\repos and the like in your user folder, Projects, src and the like at the top of each drive) and every folder Claude Code has worked in, as before.

Before you update

  • Nothing: it updates itself as usual. The three jobs' scripts changed, so they wait for approval again (the Steward approves merged scripts in its rounds, or reeve jobs approve <name>).

0.5.7

It carries the Steward's kit 2.25.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.25.0: The rest of the settings audit's shared helpers, and a tour that fits the page it's on.

Before you update

  • Nothing: it updates itself as usual.

0.5.6

It carries the Steward's kit 2.24.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.24.0: What every agent asked Manor, its owner or GitHub for by hand, from the kit.

Before you update

  • Nothing: it updates itself as usual.

0.5.5

It carries the Steward's kit 2.23.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.23.0: Settings in React, and short; and a new hire's tour of its page.

Before you update

  • Nothing: it updates itself as usual.

0.5.4

Reeve's Settings page no longer edits the accelerators: they are the Smith's.

What changed

  • The accelerators, their order and the NPU's and graphics cards' idle times are gone from Reeve's Settings page, and so are its This PC and Set up sections. One card takes their place: "Accelerators are the Smith's: open its page", or, where the Smith isn't installed, "Hire the Smith in Manor to set up or change the accelerators."
  • The "Other settings" box, which showed the rest of config.json as raw JSON, is gone. Keys the page doesn't show are kept as they are.
  • Reeve's page refuses a save that names the accelerators, their order or their idle times, and says where to change them instead.
  • Reeve still reads the accelerators from config.json exactly as before, and "Where its work runs" still lists them.

Before you update

  • Change the accelerators on the Smith's page (its Settings). Without the Smith, hire it in Manor, or set them up with reeve accelerators setup, which stays.
  • Anything you kept in "Other settings" stays in config.json; it just isn't shown on the page any more.

0.5.3

It carries the Steward's kit 2.22.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.22.0: The react part's components are GamerNexus's UI kit, in the manor's look.

Before you update

  • Nothing: it updates itself as usual.

0.5.2

It carries the Steward's kit 2.21.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.21.0: A page drawn in the browser, with React: the kit's react part.

Before you update

  • Nothing: it updates itself as usual.

0.5.1

What's new

  • The kit 2.20.0: what this PC has (whether it has an NPU, and its cards) is kept in hardware.json, and Reeve's keeper refreshes it once a day. An entry said to be the NPU on a PC without one is the graphics card, by its name, whatever model it serves.

What changed

  • REEVE_CHAT_DEVICE and REEVE_EMBED_DEVICE no longer default to Npu: with none said, the kit decides from what this PC has.
  • The MCP server's instructions and its tools' titles speak of "the local model" on "this PC", not "this laptop's NPU".
  • The Accelerators section says when it can't read the accelerators, and keeps the last look, instead of vanishing or freezing without a word.
  • Where its work runs speaks of GenieX and npu-embed on the NPU only on a PC whose config lists the NPU.

Before you update

  • Nothing: it updates itself as usual.

0.5.0

What's new

  • Projects on the rounds. Each non-employee project's checkout is among the repositories Reeve looks after, even outside his search folders, and it is never left alone: Manor's settings put it on the rounds. The home page lists projects in their own group, with Manor's name for each.
  • Alerts name the project. An alert about a project says which, by Manor's name for it, in its title (and a new projects field at /api/alerts). Its id doesn't change.
  • Merged-branch cleanup (a new job, project-branches). In each project whose entry doesn't say "cleanBranches": false, it fetches origin and deletes the branches fully merged into the project's branch: here, and on GitHub when the entry names its repository and gh lists its open pull requests (at most 20 there a round). Never the project's branch, main, master, develop, gh-pages, release/*, hotfix/*, a checked-out branch or one with an open pull request. Squash-merged branches and branches with no commit for 30 days are only listed.
  • Every deletion can be undone. Each is logged with the branch's tip in %USERPROFILE%\.reeve\branches\deleted.jsonl; the home page and reeve branches show the last ones with the command that puts each back.

What changed

  • Manor's own repositories (Manor, the Steward's employees, the agents in Manor's registry) are never treated as projects, and never have branches deleted by this job.

Before you update

  • The new job's script needs your approval before it runs: read jobs\project-branches.ps1, then node $HOME\.reeve\app\src\cli.ts jobs approve project-branches. Until then the home page shows it as needing approval, and nothing is deleted. node $HOME\.reeve\app\src\cli.ts branches clean --dry-run says what it would delete.

0.4.32

What's new

  • A release's notes, and so its What's new link in Manor, are its entry here: what's new, what changed, and what to do before updating. A version with no entry lists its changes since the release before instead.

What changed

  • Reeve carries the Steward's kit 2.19.0 (it carried 2.18.0), which makes these notes.

Before you update

  • Nothing: it updates itself as usual.

0.4.31

It carries the Steward's kit 2.18.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.18.0: Non-employee projects: repositories that ride along with the manor.

Before you update

  • Nothing: it updates itself as usual.

0.4.30

A job that fails only because the PC is offline is waited out, not raised as an alert.

What changed

  • When a job fails with the signs of a missing network (or times out) and the PC is found to be offline, its last result stands: no new alert in Manor's banner and no toast. It runs again at its usual time, and docs-refresh retries then.
  • The home page says so above such a job's summary: "Offline N min ago: it runs again when due. As it last went through:".
  • A job's own failure, or any failure while the PC is online, is reported as before.

Before you update

  • Nothing: it updates itself as usual.

0.4.29

Reeve's releases are built, and published in the public Manor-releases.

What changed

  • A release is a built, minified copy of Reeve rather than its readable source, and it is published in the public Manor-releases, so any PC can download it without signing in to GitHub.
  • Reeve starts the same way as before: its tasks, its MCP server in Claude Code and Manor need no change.
  • It carries the Steward's kit 2.17.0.

Before you update

  • Nothing: it updates itself as usual.

0.4.28

It carries the Steward's kit 2.16.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.16.0: Every agent's page uses the width of the window.

Before you update

  • Nothing: it updates itself as usual.

0.4.27

It carries the Steward's kit 2.15.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.15.0: Offline is waited out, never a failure.

Before you update

  • Nothing: it updates itself as usual.

0.4.26

It carries the Steward's kit 2.14.0: the parts every agent of the manor shares.

What changed

  • The Steward's kit 2.14.0: The title bar stays at the top as the page scrolls.
  • Reeve's tests expect the NPU first in the automatic order, as the kit has it since 2.13.0.

Before you update

  • Nothing: it updates itself as usual.

0.4.25

Manor can find Reeve on GitHub and offer to hire it.

What's new

  • Every release publishes manor-agent.json beside its zip, listed in its checksums, so Manor 0.4.35 and later finds Reeve on GitHub and offers Hire on its role's card.

Before you update

  • Nothing: it updates itself as usual.

0.4.24

The NPU comes first: it takes every request it can, busy or not.

What changed

  • When the NPU is the first accelerator that serves a request and fits it, and it hasn't failed lately, it alone takes the request, even when busy. A graphics card or the processor takes only what the NPU can't do: a kind it doesn't serve, a request too big for it, or one after it failed.
  • A model still loading on the NPU is waited for, not passed over for the card.
  • With gpuWithNpu on, background work waits when the NPU's line is full, instead of going to the free card.

Before you update

  • Nothing: it updates itself as usual.