Repository navigation
Releases
v0.35.6
apogee — v0.35.6 — 2026-11-18
A tidier conversation: groups of tool calls now say in plain words what they did and fold themselves away once finished, and the side panel can be resized while you watch another session.
New
- Finished tool groups fold themselves away — once every call in a
✦ Toolsgroup is done and the conversation has moved on, the group shrinks to its single summary line, whatever its size, unless you have already opened, folded or clicked into it; groups in resumed sessions arrive folded, and the latest group of a reply still in progress stays open. Setui.tools-auto-collapse: false(in/settingsor the config file, taking effect at once) to go back to folding by size alone underui.tools-openandui.tools-fold-over.
Improved
- Tool group headers say what the calls did — instead of
✦ Tools (3 Read, 1 Grep, 4 Terminal), a group's header now reads like✦ Read 3 files, searched 1 pattern, ran 4 commands, edited 2 files +18 −5 · 1 failed, with failed and denied calls shown in red and the wording in the present tense while work is still running (Reading 2 files). On a narrow terminal it shortens step by step down toTools (N calls), always keeping the failure count, and it reads the same way in a sub-agent's view.
Fixed
- Resizing the side panel while watching a session — dragging the panel's separator, double-clicking it to reset, and
/panel width <n>or/panel width resetnow work while you watch another session, and the width you choose is saved as your ownui.side-panel.width. The other/panelcommands and the pin stay read-only while watching. - Side-panel jumps into a folded tool group — clicking a task or changed-file row in the side panel whose call sits inside a folded
✦ Toolsgroup now opens that group and scrolls to the call, instead of leaving it hidden; only that group opens, and yourui.tools-opensetting is left alone.
v0.35.5
apogee — v0.35.5 — 2026-11-18
This release makes apogee's git support work in more repositories, and says plainly when it will not.
Improved
- Git tools keep working in a repository that sets its own merge driver — A repository whose own git config names a merge driver (
merge.<name>.driver) no longer shuts you out of apogee's git tools and footer actions: apogee switches that driver off for every git call and refuses only commands that would merge file contents, such asrebase,cherry-pick,revertor a merge that is not fast-forward-only, with a message naming the setting. Aborting or quitting an operation already in progress is never refused, and a merge driver in your global git config still runs as before. - The footer shows when apogee refuses a repository's git — In a repository whose own config names a program git would run (a repo-local
core.sshCommand, for example), the footer's git segment now readsgit refusedin the error colour instead of vanishing, and a one-time note names the setting and suggests moving it to your global git config if you trust it./git, or a click on the marker, gives that same explanation instead of "no git here".
Fixed
- A refused footer rebase no longer reports a confusing abort failure — When the footer's
rebase onto upstreamis refused before it starts, the note now gives just the reason, without a conflict list or the misleading "rebase --abort also failed: no rebase in progress"; status, fetch, pull, push and branch switching from the footer keep working in such a repository.
Docs & install
- Manual covers repository-level git settings — The manual now explains the
git refusedfooter marker and its note, how to clear it through your global git config, and that a merge driver set in the repository itself now works with apogee, with only the footer's rebase refused.
v0.35.4
apogee — v0.35.4 — 2026-11-17
This release closes two ways a repository could get git to run a program of its choosing, restores the blank lines in the Windows Console, and gets the update check and go install ready for a future v1.0.0.
Improved
- The update check is ready for v1.0.0 — The startup update notice and
apogee updatenow announce v1.0.0 and any other v1.x release newer than yours, skipping only the four burned (withdrawn) versions v1.1.0, v1.7.0, v1.8.0 and v1.8.1. Before, they skipped the whole v1.0.0–v1.8.0 range.
Fixed
- Git no longer runs a helper program a repository names for its remote — In a repository whose own config sets
remote.<name>.vcs, a Fetch or another git tool or action could run a program planted in the checkout, outside the sandbox. apogee now refuses to run git there, and the refusal names the setting. git configwrites that would make git run a program are refused in the terminal — Through theterminaltool, setting or removing in the repository's own configremote.<name>.uploadPackorreceivePack,protocol.alloworprotocol.ext.allow(other thannever), anext::url.<base>.insteadOforpushInsteadOf, or asubmodule.<name>.updatestarting with!is now refused in every mode. Otherprotocol.<x>.allowkeys, ordinary URL rewrites, thenone,rebase,mergeandcheckoutupdate modes,--globalwrites and every read still run.- The Windows Console keeps its blank lines — On Windows, the Console Read pane and the text
console_readandconsole_sendhand the model now keep the empty lines the screen shows, so a freshcmdno longer has its banner glued to its prompt. Console output on macOS and Linux is unchanged.
Docs & install
go install …@latestwill reach v1.x releases — Publishing a release from v1.0.0 up to v1.8.1 now runs a newplaceholderstep, also shown bystatus, that tags the v1.8.1 placeholder on the release sogo install …@latestinstalls it; the release binaries still report the release's own version. For any other version the step reports that it is not needed.- Only four v1.x versions are retracted — apogee's
go.modnow retracts exactly v1.1.0, v1.7.0, v1.8.0 and v1.8.1 instead of the whole v1.0.0–v1.8.0 range, so v1.0.0 and other v1.x numbers can ship. The release tool and the automatic tagging refuse a burned version, and ago.modwhose retractions differ from that list. - Release checks confirm the Go module proxy serves each release —
go run ./cmd/release smokegains agoproxycheck that fails when proxy.golang.org cannot resolve the release's version or marks it retracted, and only warns when@lateststill points at another version. It is skipped on a machine without Go. - The building manual covers the burned versions and cutting v1.0.0 — Its release section lists the four burned versions in place of the old range, describes the new
placeholderstep and whypreparenow refuses (rungit fetch --prune --prune-tagsfirst), and adds runbooks for cutting v1.0.0 and for recovery.
Internal
- The macOS sandbox is tested on a real Mac — Continuous integration now runs the macOS sandbox and single-instance lock tests on a macOS machine for every push and pull request, without holding up a release.
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.
v0.35.2
apogee — v0.35.2 — 2026-11-12
This release tidies the TUI transcript: start-up notes read cleanly at any window width, and more kinds of tool calls now fold into the grouped Tools block instead of interrupting it.
Improved
- MCP tool calls show a readable name — an MCP tool's block now reads
<server> · <tool>(for examplegithub · search_issues) instead of the rawgithub__search_issues. The approval prompt and therunning …status still use the raw name, and sessions recorded earlier replay with the label they were saved with.
Fixed
- MCP tool calls no longer break up the Tools block — a run of MCP calls among reads and searches now folds into the grouped
✦ Toolsblock and is counted there, each row led by the call's first argument (or the tool's name when it has none). Opening a row still shows every argument exactly as it was sent. git_statuscalls group with the rest — agit_statuscall now appears as aworking treerow inside the grouped✦ Toolsblock instead of splitting it with a block of its own; opening the row still shows the branch and the staged, unstaged and untracked files.run_testswith no path groups too — a test run over the whole project now shows the targetwhole project(with· <filter>when you gave one) and joins the grouped Tools block; the live status line still readsrunning tests.- Start-up session-log notes wrap cleanly — a note in the
✦ Session logblock that was written with line breaks now reads as one paragraph, wrapped at your window's width and indented under its text, instead of keeping ragged hard breaks. - One clear note per gap in Auto's confinement — when Auto mode starts on a system whose sandbox cannot block every kind of write, the TUI's session log now lists one note per gap with its consequence (for example
landlock cannot fence truncate(2) — a confined command can still empty an existing file outside the workspace (kernel < 6.2)), instead of one run-together notice. The message printed to the terminal, and byapogee headlessandapogee daemon, is unchanged.
v0.35.1
apogee — v0.35.1 — 2026-11-12
This release tidies the screen apogee greets you with at launch and fixes PDF viewing over SSH.
New
- Start-up session log — The routine notes a session opens with (the context files apogee loaded, what Auto mode cannot fence, the first notes about your model) now gather into one collapsed
✦ Session log (N notes)block instead of filling the screen; click it, or press Option-Up then Enter, to read them all. Notices that need your attention, such as a skipped MCP server, still get their own line, and each launch,/clear,/newand/sessionsrestore starts a fresh log that is never saved.
Improved
- Shorter start-up notices — Auto mode's warning about what it cannot fence is now one head line plus a short line per unfenced access, each still saying what a command could do through it. The note for a model that cannot switch its reasoning off now simply reads
<model> always reasons — compaction and titles spend part of their output cap on it.
Fixed
- PDFs open over SSH — PDFs from the built-in document server, viewed over SSH, now render in Chrome, Safari and Firefox instead of risking a blank page, while
.htmland.svgdocuments keep their stricter sandbox. - No stray "context window changed" note at launch — When you set a model but not its context window, launching no longer prints
context window changed: unknown → …as apogee learns the window; a window that really changes later still gets its note.
v0.35.0
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:— anmcp-servers:entry withauth: oauthandclient-secret-env:but noissuer: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: addissuer: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.sockand/run/podman/podman.sock. That meansdocker,podman,ghwith 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:— anauth: oauthentry inmcp-servers:can name its issuer URL;apogee mcp loginthen 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 jsonoutput carries it as a newupstream_loadingevent.
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 headlessorapogee 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 probelistsconnect(2) AF_UNIXas 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 probeand/confine statusstop listingconnect(2) UDPas unfenced. Older kernels are unchanged. - Git errors name the right command — a failed git call that starts with an option such as
-cnow reports, for example,git add: …instead ofgit -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_fileor an@filereference, 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_fileor an@filereference 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 (rmin the terminal, the source of amove_file,/undo), no longer stays listed under Changed files, live or after resuming a session; it shows again if the file comes back. apogee updatefinishes 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
/undorelies 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: …orconnected: …once it succeeds. - Key commands that leave a background process running now work — an
api-key-cmd:, credential-store helper or reactionrun: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_testson 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.diagnosticshandles Go files in nested modules — a clean Go file under its owngo.modinside the workspace is no longer reported with vet errors; vet now runs from that module, and when Go cannot load the module the result saysgo 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 adoptshows 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
~/.apogeefailed withresolve config; it now writes to the junction's target and leaves the junction in place. apogee probe modelstops 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/netv0.62.0, clearing advisories GO-2026-6866 and GO-2026-6860 (apogee's code did not reach them), together with newerx/sys,x/text,x/termandx/sync. - The docs spell out what Auto's sandbox closes on each platform — the manual, the
apogee probereference 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 embeddin...
v0.34.0
apogee — v0.34.0 — 2026-11-10
This release adds a side panel beside the conversation on wide terminals, showing live sub-agents, tasks, changed files, usage and MCP servers, along with a new /mcp report and quicker notice when an MCP server goes away. It also lets advice Reactions speak just before a request is sent, and gives a long prompt draft a scroll bar.
New
- A side panel beside the conversation — on a terminal 137 columns wide or more (117 with
ui.side-panel.show: on), a column to the right of the transcript shows your sub-agents, the task list, the files changed this session, usage and MCP servers, and readsnothing livewhen idle. Clicking a row opens what it names — a sub-agent's Run view, the task card, a changed file's edit or/usage— the panel follows the run you are viewing, and a resumed session gets its tasks, changed files and usage back. - Choose when the side panel shows and what it holds —
ui.side-panel.show(auto,onoroff) decides when it is drawn, andui.side-panel.sectionssets each section's order and whether it ispinned,autoorhidden. Both apply straight away, and/settingssaves the show setting to~/.apogee/config.yaml. /panelcontrols the side panel from the prompt —/panel on|off|autosets when it shows and/panel pin|unpin|hide <section>sets one section, each saved to your global config. A bare/panelreports the current modes, even mid-run, and says when the window is too narrow to dock the panel.- Resize the side panel — drag the panel's separator to resize it live (the new width is saved as
ui.side-panel.width, 24 columns or more, default 44), double-click it to go back to the default, or type/panel width <n>or/panel width reset. A width you choose can narrow the conversation to as few as 60 columns. - Fold and pin side-panel sections — click a section's title to fold it to one line or open it again, and the choice is remembered in
ui.side-panel.folded; click the●/○at the start of a header to pin or unpin it. A section folded because the window is short shows▶, and a click opens it for the rest of the session without touching your config. - The keyboard reaches the side panel — in navigation mode (
⌥↑/⌥↓),→moves into the panel and←back,⏎on a row does what a click would (a header has two stops: its pin and its title), and^xon a sub-agent row stops that run./help's key legend now lists these keys. - The side panel on a narrow window — when the window is too narrow to dock the panel, a bare
/panelor→in navigation mode opens it over the right edge of the conversation.←,escor a click outside it closes it again. - Sub-agent rows show when a run is waiting on you — while a sub-agent's approval is open, its side-panel row reads
waitingunder◷(?withui.glyphs: safe) in the warning colour until the question is settled or the run ends. Long runs keep the rows aligned, with clocks such as1h02mand1d02h, and the running spinner cycles through the sameui.spinner-colorcolours as the status line's. - The side panel looks like the rest of the screen — headers read like the transcript's block headings, with short summaries such as
(2 · 1 queued), a failure such as a sub-agent's or MCP server'sfailedshows in the transcript's red (as/mcpshows it too), and usage reads figures-then-bar like the status-line gauge, never over 100%. The panel starts one row below the top edge, lines up with the status line, and its separator is as quiet as the scroll track. ui.glyphs: safecovers the side panel — with safe glyphs on, the panel uses•for a pinned section,>for the current task and the viewed run, and»for a file a sub-agent wrote. The manual'sui.glyphsentry now lists every shape that looks the same in both sets./mcpshows your MCP servers — a new report, closed withesc, lists every MCP server with its transport, whether it comes from your global or project config, its state, its tool count and, for a failed one, why it failed; it stays live while open, during a Turn and while watching a session. The side panel gains a matching MCP section that appears while any server is not connected and opens/mcpon a click; because/mnow completes to/mcp, type/mofor/model.- Advice Reactions can fire just before a request is sent — an
advise:Reaction can now useon: [pre-request]oron: [post-response], and its answer is attached to the next outgoing request only, never saved into the conversation, and switched off under Bypass./advicelists these firings, andapogee probe context --livecounts pre-request advice in its first-Turn reading. - A scroll bar for long prompts — once a draft is longer than the prompt box can show, a scroll bar appears on the box's right edge (hidden by
ui.show-scrollbar: falselike the others). The mouse wheel over the box now scrolls the draft instead of the conversation. - More detail in headless JSON output —
apogee headless --format jsonwrites atask_listline each time an agent's task list changes (sub-agents included) and acontext_costline at the end of every Turn, and eachsub_agent_phaseline now carries the time it happened asdata.at. - MCP server state for programs that embed apogee — the Event stream now reports each MCP server's lifecycle (
dialling,connected,failed,disconnected) asapogee.MCPServerEvent, also written asmcp_serverlines in the interactive session's journal, andapogee.SerializeEventslets an embedding program send its own Events through the engine's ordered sink.
Improved
- apogee notices a lost MCP server at once — when an MCP server exits, crashes or drops its connection mid-session, apogee no longer waits for the next tool call to find out: it withdraws the server's tools,
/mcpand the side panel readdisconnected (lost)with the cause, and the conversation gains one line saying so. It does not reconnect on its own; retry from themcp-serversrow in/settings. - Clearer sub-agent and task labels in the conversation — a delegation's block is now headed
Sub-agent, a group of themSub-agents (N)and the task cardTasks (done/total), and a delegation waiting for a free slot readsqueuedinstead ofscheduled. Resumed sessions show the new labels too. - The navigation cursor shows without colour — the row the navigation-mode cursor stands on now also starts with a
▌, so you can see where it is on a terminal that shows no colour.
Fixed
- Small models' sub-agent calls no longer waste a Turn — a
sub_agentcall whosetoolsis["read-only"], or a list of tool names sent as a quoted string, now runs instead of being refused, andfan_outand workflow stagetools:accept the same forms. Afan_outwith an unknown tool name, or one that mixesread-onlywith tool names, is now refused with a clear message before any helper starts. /settingspointer hints stay on screen — a long setting value no longer pushes hints such as· ⏎ opens $EDITORoff the edge of the pane; the value is cut short with…instead, while the row you are editing still shows it whole.- Windows: a session journal that cannot be removed is reported — when a session ends and its journal file cannot be removed for any reason other than a session watcher still holding it open, the "session journal stopped" notice now says so instead of the file being left behind silently.
Docs & install
- The manual explains the side panel — the configuration manual gains a side-panel section covering when it shows, what each section's rows mean, clicks, resizing, the narrow-window overlay, the keyboard, and watching and resuming sessions.
v0.33.1
apogee — v0.33.1 — 2026-11-07
This release keeps apogee responsive while it waits. Changing your MCP servers no longer freezes the screen, only the servers you touched reconnect, and slow waits outside a turn now show a spinner and a clock.
New
- The status line shows a spinner while apogee waits outside a turn — during a
/modelload,/unload-model,/stop-server,connecting…to a server, resuming a session from/sessions(loading session…), a footer git action, or a bare/rename(naming this session…), the status line shows your turningui.spinnerglyph, the wait's word and a running clock (⠶ loading qwen3… · 01:04s). A slow machine no longer looks frozen, and an offline session, or one with no server chosen yet, shows no animation. - Pop-up
loading…rows animate — while the/sessionsbrowser reads its list, or the/workflowsitem view loads an item, theloading…row is led by the turning spinner, in yourui.spinner-colorandui.glyphssettings.
Improved
- Saving
mcp-servers:no longer freezes the screen — a save from the/settingsrow's editor or from a watched config file now connects the added or changed MCP servers in the background, even while the model is working. The row readsreconnecting MCP…until the new connections are taken in, thensavedorsaved — live apply failed: <server>: …, and quitting cancels any connection still in progress. - MCP servers reconnect one at a time — a saved
mcp-servers:edit now reconnects only the servers it adds or changes: an unchanged server keeps its connection and tools, a removed one is closed, and one server failing no longer costs any other its connection. A server whose reconnect fails keeps its previous connection, each server reports its result in the transcript (mcp <server> reconnected,mcp <server> connected,mcp reconnect failed: <server>: … — previous connection kept,mcp connect failed: <server>: …), and startup behaves as before. /sessionsopens straight away — the pane appears on the next frame with oneloading…row and the legendesc close, and your saved sessions replace that row as soon as they are read, so a slow disk delays the rows but never the pane. An empty or unreadable store closes it with the sameno saved sessionsorcould not list sessions: …note as before.- Listing saved sessions is much faster —
/sessions,--continueand other session listings now read only each saved session's header instead of the whole conversation, so large stores list quickly on a slow machine. A saved session whose conversation is damaged now shows in the list and reports its error when you resume it, and--continuereports that error instead of silently picking an older session. - Answering a project config MCP server prompt responds at once — adopting or rejecting an MCP server from a project's config returns immediately; the server connects in the background and reports how that went as its own transcript note, rather than as an error on your answer.
Fixed
- An MCP save while the model is working no longer interferes with the running turn — the new MCP tools are swapped in only once the turn ends, and the swap can no longer clash with the work in progress.
- A
url-safety:edit that blocks an MCP server's address disconnects it straight away — the server is cut off as you type, even mid-turn and even when your config file has an error, and the row names the disconnected server before it reports the unreadable file. A server your edited lists newly allow connects in the background and reports the result as its own transcript note. - A blocked fallback connection now reconnects to the server's configured address — when a server's move to a new address had failed and it was still running on its old one, a
url-safety:edit that blocked the old address used to leave the server gone until you retried. apogee now connects it to its configured address in the background (mcp <server> connected) whenever your lists allow it.
Docs & install
- New demo clip in the README — the animated demo at the top of the README was re-filmed on a smaller frame and is a lighter download.
Internal
- Safer tool swaps for programs that embed apogee —
Agent.SwapToolsmay now be called from any goroutine and is refused at once, never raced, while the engine is working, and the newAgent.CanSwapToolsasks the same question without swapping.
v0.33.0
apogee — v0.33.0 — 2026-11-05
The footer is the centre of this release. It now has two rows by default, a layout and colours you can set yourself, and a git menu you open with one click. run_tests also handles projects that live in a subdirectory, and config values that used to be quietly replaced by a default are now refused when apogee starts.
Breaking changes
- Out-of-range count settings are refused instead of replaced by the default — a
delegate-max-depthof 0 or below, or a negativedelegate-max-steps,delegate-fanout-rounds,delegate-max-tokens,workflow-retries,workflow-continuationsorworking-window, now stops startup, a live reload of the config andapogee probe configwith a message naming the key, and a project config with a negative workflow count is skipped with a notice. What to do: remove the key or set it to a value in range. Leaving a key out, or setting a count to0, works as it did before.
New
- Git actions from the footer — click the footer's git segment, or run
/git, to pick fetch, pull (fast-forward only), push (never forced; a branch with no upstream is pushed tooriginand set to track it), sync, switch branch or rebase onto upstream (asked first, and undone on a conflict, naming the files). Each result lands in the transcript and the branch counts refresh at once; the menu opens only while the agent is idle, and your repository's hooks never run. ui.footer.rowslays out the footer — list one or two rows of segments (host,model,effort,mode,workdir,git,spend) in the order you want them, withmodeexactly once at the right edge of its row. A saved change redraws the footer at once, and an invalid list stops startup with a message naming the setting.ui.footer.colorsrecolours footer segments — maphost,model,effort,workdir,branchorspendto a role from your colour scheme (for example{model: success, branch: warning}) to paint that segment in it. A saved edit repaints the footer at once, and an unknown segment or role stops startup with a message naming it.
Improved
- The footer has two rows by default — host, model, effort and the mode marker sit on the top row, with the folder, git state and spend below them, so a long path or branch name no longer crowds out the mode marker; the footer takes one more row of the screen. To keep the single row, set
ui.footer.rows: [[host, model, effort, workdir, git, spend, mode]]. - The Tools header says what ran — a folded group of tool calls now reads
✦ Tools (3 Read, 4 Terminal)instead of✦ Tools (7 calls), falling back to the plain count when the window is narrow. run_testsworks on projects in a subdirectory — given apath, it finds the test runner there or in the nearest folder above it and runs from that folder, so a nested Go module or a clone inside the workspace is tested as its own project instead of being refused; apaththat does not exist is refused withpath not found.run_testssays where it looked — when it finds no test runner, the message lists every folder it searched, nearest first, up to the workspace root.- The footer shortens before it drops — on a narrow window the folder and then the branch name are shortened in the middle (
~/…/tui,feat…name), and only after that do the spend, git state or effort disappear. - The footer's git counts are coloured by meaning — uncommitted changes (
Δ) and commits waiting to be pulled (↓) show in the scheme's warning colour, and commits ready to push (↑) in its success colour. - The model name in the footer has its own accent colour — a new
footer-accentcolour-scheme role makes it stand out slightly from the details around it. A custom scheme that does not set the role gets thedarkscheme's value. apogee probe configrefuses what startup refuses — a value that would stop apogee from launching, such as asessions:age like30d, an unknownui.spinneror a server with no endpoint, now fails the command with the same message instead of exiting successfully, and notices that only startup shows are listed too, each once.
Fixed
- Watching a session shows that session's folder and branch — while you watch a live session, the footer shows a
watchingmarker with the watched session's folder, branch and git state instead of your own, and your background git fetch pauses untilescbrings yours back. - Watch clocks show how long the session has been working — the
[total …]readout and the activity clock (thinking · 12s) in a watch now count from the watched session's own times, not from when you started watching, and a difference between the two machines' clocks does not throw them off. - No more stripes at the bottom of the screen — the status line, prompt box and footer now paint one even band of your colour scheme's background across the full width, including the filled cells of the context gauge. The chat area keeps your terminal's own background.
- Painted rows reach the right edge on Terminal.app — the status line, footer and other coloured rows no longer stop short of the window's right border on macOS Terminal.
- A broken
web-search-endpoint:is caught at startup — a value that is not anhttporhttpsaddress with a host (such asx y zorftp://host) now stops startup, a live reload andapogee probe configwith a message naming it, instead of every web search failing later; a blank value still means the built-in provider.
Docs & install
- Workflows manual corrects where
parallel-agents:goes — the keys table now says it belongs under a server entry inservers:, because apogee ignores it at the top level. - Go package docs state the versioning policy — the documentation for anyone embedding apogee as a Go library no longer promises a v1.0.0 at a set milestone: apogee stays at v0.x, with no stability promise, until it reaches production, and its first stable release will not use any number from v1.0.0 to v1.8.0.
Internal
- Release numbers stay clear of the retracted v1.0.0–v1.8.0 range — the release tools now refuse to tag or publish any version in that range, so a
go getof apogee never resolves to one of those old, withdrawn versions.