Skip to content

v0.35.0

Choose a tag to compare

@airiclenz airiclenz released this 12 Nov 05:22
· 113 commits to main since this release

apogee — v0.35.0 — 2026-11-11

This release tightens what Auto's sandbox lets a command reach and waits out a local server that is still loading its model. It also fixes a run of crashes and hangs on hostile or damaged PDFs.

Breaking changes

  • MCP servers with a client secret now need issuer: — an mcp-servers: entry with auth: oauth and client-secret-env: but no issuer: is refused when the config loads: in your global config apogee will not start, and in a project config that server is dropped with a notice. What to do: add issuer: to the entry, set to the issuer URL of the authorization server your client secret belongs to.
  • Docker, podman and keyring tools no longer work inside Auto's sandbox on Linux — under the bwrap backend, and under landlock on kernels with landlock ABI 9 or later, a sandboxed command can no longer reach sockets in your user runtime folder ($XDG_RUNTIME_DIR) or /run/docker.sock and /run/podman/podman.sock. That means docker, podman, gh with a keyring-stored token, libsecret or VS Code git credential helpers and Wayland apps fail there, while ssh-agent and gpg-agent keep working. What to do: run those commands outside Auto mode, or yourself in your own terminal.
  • Allow rules containing control characters are refused — a global allow: rule holding a tab, line break, escape, DEL or Unicode bidi control now stops apogee from starting and names the offending entry; in a project config the whole project layer is skipped with a notice, and adding or removing such a rule through apogee is refused. What to do: rewrite the rule as plain text on a single line.

New

  • Pin an MCP server's authorization server with issuer: — an auth: oauth entry in mcp-servers: can name its issuer URL; apogee mcp login then uses that server only if the endpoint offers it, and a saved token another server issued asks for a fresh login. The project adoption pane shows the key.
  • A notice while a server loads its model — apogee says once that <server> is still loading its model (HTTP 503) — waiting up to 10m, in the TUI, the saved session, a headless run's error output and the daemon log; --format json output carries it as a new upstream_loading event.

Improved

  • Auto's startup notice names what its fence does not stop — wherever the sandbox still lets a command reach a local unix socket, starting Auto (in the TUI, apogee headless or apogee daemon) now warns that a service of yours listening there, such as tmux, can run commands outside the fence; on macOS it also names launchd and Mach services. apogee probe lists connect(2) AF_UNIX as unfenced on every landlock kernel and on macOS.
  • A network-denied sandbox also blocks UDP on newer Linux kernels — with landlock ABI 10 or later, a sandbox that denies the network now refuses UDP sends and binds too, and apogee probe and /confine status stop listing connect(2) UDP as unfenced. Older kernels are unchanged.
  • Git errors name the right command — a failed git call that starts with an option such as -c now reports, for example, git add: … instead of git -c: ….

Fixed

  • A server still loading its model no longer fails the request — when a local server such as llama-server answers that its model is still loading, apogee now waits and retries (every 1 to 8 seconds, for up to 10 minutes; Esc stops it) instead of failing within a second. A server entry with a fallback: list keeps moving to its fallback instead.
  • The secrets check before a commit reads the whole staged change — a secret or key-file name staged beyond the first 256 KiB of a commit used to go unchecked; apogee now scans all of it, and a change too large to scan within 30 seconds asks for your approval instead of passing as clean.
  • Hostile PDFs can no longer crash apogee — a PDF that nests its structure very deeply now gets the usual "could not read this PDF" message through read_file or an @file reference, instead of crashing apogee with a stack overflow.
  • Truncated PDFs no longer hang — a PDF cut off in the middle of its page text or font data no longer leaves read_file or an @file reference running until apogee is killed; the text before the cut is returned, and a PDF whose internal index claims more objects than it holds is refused promptly.
  • PDFs with an odd-length hex string read correctly — such a PDF used to fail as unreadable; it now reads the way the PDF standard specifies.
  • gpt-oss tool calls no longer leak raw markup into answers — behind a server that leaves gpt-oss's Harmony format unparsed, a tool call's control tokens and JSON no longer show up as the assistant's answer. apogee cannot run such a call, so it nudges the model once and, if the model keeps answering that way, ends the turn with "upstream returned an empty reply (finish: stop)".
  • Deleted files leave the side panel's changed-file list — a file removed with delete_file, or gone from disk another way (rm in the terminal, the source of a move_file, /undo), no longer stays listed under Changed files, live or after resuming a session; it shows again if the file comes back.
  • apogee update finishes on a slow connection — the download used to be cut off after two minutes however steadily it was arriving; it now fails only when no data arrives for 60 seconds, with an error saying it stalled.
  • Undo snapshots work on large workspaces and slow disks — taking the snapshot /undo relies on no longer fails after 60 seconds, and a snapshot interrupted partway no longer blocks the next one.
  • A failed undo snapshot no longer slows every edit — when apogee cannot take the snapshot, it now warns once and tries again with your next message, instead of retrying and warning before every file-changing tool call.
  • A model switch that failed to bind recovers by itself — when the server changed models (or a session's first connection failed) and apogee could not bind to it, the session stayed on the old model, or none, until you picked one by hand; it now retries every 60 seconds and reports model changed: … or connected: … once it succeeds.
  • Key commands that leave a background process running now work — an api-key-cmd:, credential-store helper or reaction run: command that succeeds but leaves a background process holding its output is no longer reported as "could not run", so the key it printed is used.
  • run_tests on a single Go test file runs its package — naming a Go test file as the path used to report a failure without running any test; it now runs the tests of that file's package.
  • diagnostics handles Go files in nested modules — a clean Go file under its own go.mod inside the workspace is no longer reported with vet errors; vet now runs from that module, and when Go cannot load the module the result says go vet skipped: ….
  • The syntax check after a write stops flagging valid code — the possible-syntax-problem note on a file write no longer fires on an apostrophe in JSX/TSX text, PHP # comments, attributes and colour codes, a C# verbatim string ending in a backslash, or a Rust character literal holding a bracket.
  • PDFs opened in the browser over SSH display again — Chromium could show a PDF from apogee's document server as a blank page; PDFs are now served under a policy the browser renders, while every other file type keeps the stricter one.
  • apogee project adopt shows Allow rules safely — the question about a proposed Allow rule now prints it the way the adoption pane does, on one line with escape sequences stripped, so a rule cannot rewrite what your terminal shows.
  • Saving settings works when the config folder is a Windows junction — a save through an NTFS junction to ~/.apogee failed with resolve config; it now writes to the junction's target and leaves the junction in place.
  • apogee probe model stops reporting phantom model changes — two nearly tied candidate tokens swapping places no longer reads as a different model behind the same name. Probe records from earlier versions are skipped with a prompt to run the probe again.
  • The Inspector no longer races background workflows — with the Inspector on, a workflow running in the background no longer reads the conversation's settings and turn number while they change, so its recorded entries stay consistent.
  • For programs embedding apogee: a single file can be a writable sandbox path on Linux — naming a regular file as an extra writable path for the landlock sandbox used to make every sandboxed command fail with EINVAL; the file is now writable in place, while deleting or replacing it stays blocked. The apogee app itself only names folders there, so it was not affected.

Docs & install

  • Building from source needs Go 1.26.11 — this picks up Go's fix for security advisory GO-2026-6859.
  • Updated Go networking library — apogee now builds with golang.org/x/net v0.62.0, clearing advisories GO-2026-6866 and GO-2026-6860 (apogee's code did not reach them), together with newer x/sys, x/text, x/term and x/sync.
  • The docs spell out what Auto's sandbox closes on each platform — the manual, the apogee probe reference and the security policy now say, backend by backend, which local sockets Auto closes, which escapes it only discloses, and which tools stop working inside it.
  • Windows: Auto's sandbox limits are now documented — the security policy and the manual now state that a sandboxed command on Windows cannot use Task Scheduler or WMI to start processes, and that Docker Desktop's and WSL's named pipes stay reachable where installed, disclosed rather than closed.

Internal

  • PDF reading is now part of apogee itself — the PDF reader moved into apogee's own code instead of a third-party module, which is what made this release's PDF fixes possible; text extraction is otherwise unchanged, and programs embedding apogee no longer pull in that module.