Repository navigation
v0.35.3
apogee — v0.35.3 — 2026-11-13
Workspaces on Windows that sit behind an NTFS junction now work end to end, two
safety gaps around project settings and git signing are closed, and apogee now
tells you more about what MCP discovery and project adoption leave out.
New
- A notice when an MCP server's tool list is cut short — if apogee stops reading a server's tools at 64 pages or 512 tools, or skips a tool whose schema is larger than 64 KiB, startup now shows one line per server naming each reason (
apogee: mcp server <name> — tool list cut short: …). After a reload, the same reason follows that server'sconnectedorreconnectedline; before, the list was trimmed without a word.
Improved
- The adoption question says what it does not cover — when apogee asks whether to trust a repository's MCP server or reaction, the question now ends with a dim
not pinned: anything it reads or runs beyond these, andapogee project adoptprints the same line. Files the server or reaction pulls in on its own can still change later without apogee asking you again, and the question now says so.
Fixed
- A project behind a Windows junction is found and can be adopted — a workspace reached through an NTFS junction now finds the
.apogee/folder above it instead of quietly running without its project settings, and adopting it no longer fails withadoption store: resolve Project root. Projects you already adopted stay adopted. - Project settings behind a Windows junction are read — a project
.apogee/config.yamlreached through a junction is now applied instead of skipped, and one that is there but cannot be read now saysthe project layer is skippedinstead of being dropped in silence. A~/.apogeefolder that is itself a junction is still recognised as your global settings, sosessions.watch-homesstill refuses it. - Saving a project setting behind a Windows junction works — saving to this project from
/settings, or answering "Always in this project…", now writes the project's.apogee/config.yamlinstead of failing withresolve Project root. - Project settings stay protected when the workspace is a link — if you open apogee in a folder reached through a symbolic link or junction, the model can no longer write, move or delete the project's
.apogee/config.yamlby spelling its path through that link or through a../path; it is refused on every platform, as it already was by its real path. - Git refuses a repository that sets its own
gpg.ssh.defaultKeyCommand— git runs that setting as a program when signing, so a repository could have used it, for example during a Rebase, to run a command outside the sandbox. The git tools and git actions now refuse such a repository, as they already did forcore.sshCommandandgpg.program, and the refusal names the setting. apogee updateno longer gives up on a slow machine — the check that the downloaded binary starts now waits up to 5 minutes instead of 30 seconds, and a timeout saysthe downloaded binary did not answer --version within 5m0s; the installed binary is unchanged. A leftover background process can no longer hold the update past that limit.- The hint under a shown document names a gesture your terminal supports — it reads
cmd+click to openin Zed, VS Code, iTerm2, WezTerm and kitty,drag to select and copyin macOS Terminal.app (where cmd+click did nothing), andcmd+click to open · drag to copywhere apogee cannot tell which terminal it is in, such as inside tmux or over SSH.
Docs & install
- Corrected manual figures — the manual now says the
/settingspane holds some ninety keys, that nineteen of them take effect at the next start, and showsapogee update --check's full message ending in— run: apogee update. The MCP section lists the discovery limits and the notice above.