Repository navigation
v0.28.0
apogee — v0.28.0 — 2026-10-21
Your own reactions can now brief the model when a session starts and again after the conversation is compacted. Compaction also gets a reaction notice of its own.
Breaking changes
- Go embedders:
apogee.ObserveRunnerhas a fourth method — if you wrote your own implementation of this interface, it will not compile against this release, because the interface now also requiresCompactionFinished(fold apogee.CompactionFold, turn int). What to do: add that method to your implementation. It is called once after each compaction that replaced the conversation, and likeSessionStartedit should only queue its work and return.
New
advise:reactions onsession-started— anadvise:entry (a command or a webhook) withon: [session-started]now loads instead of being refused, and its answer briefs the model at the start of the session; an entry may also putrun:besideadvise:onsession-started. Puttingadvise:on a Moment it does not support now gets an error that lists all four it accepts:post-tool-result,file-changed,session-startedandcompaction-finished.- Re-brief the model after compaction — an
advise:entry withon: [compaction-finished]starts as soon as compaction begins (automatic, on context overflow, or with/compact), and its answer is placed just ahead of the next message the model reads, never inside the summary. Each new answer replaces that entry's earlier briefing instead of piling up, and a compaction that fails, is cancelled or has nothing to compact runs no re-brief. run:reactions oncompaction-finished— a newcompaction-finishednotice fires once each time compaction replaces the conversation, and arun:entry on it learns which kind ran from thefoldfield (auto,emergencyormanual) or theAPOGEE_REACTION_FOLDenvironment variable. Compactions inside sub-agents, and ones that fail or are cancelled, fire nothing.- Session-start briefings in headless, daemon and scheduled runs —
apogee headless,apogee daemonand/scheduleruns now deliver asession-startedadvise:answer with their very first request.apogee probe context --liveincludes that briefing when it measures the first Turn. - Entries you adopt before your first prompt still brief that session — a
session-startedadvise:entry switched on before you send the first prompt starts right away and briefs that session: whether you adopt a project's reactions in the start-up pane, in/settingsor withapogee project adopt, or a live reload of your config adds it. One switched on after the first prompt waits for the next session.
Improved
/adviceshows session-start briefings —/advicenow lists each firing of asession-startedadvise:entry under its Turn, as<reaction> (user origin) @ session-started, with the exact text the model read (capped and redacted).
Fixed
- Reloading reactions in a resumed session — after you resumed a session that was mid-exchange or still had input queued, a
session-startedreaction added by a live reload could fire for a session that was already under way. It now waits for the next session start. - Go embedders: failed session-start advice after an abort — a session-start advice run from an
apogee.SessionStartedFunchandler that timed out, failed or panicked was reported a second time, or its late answer attached, at the next exchange after an aborted one. A run is now reported once and then dropped, and an abort carries over only the runs that answered.
Docs & install
- Building from source needs Go 1.26.10 — building apogee now requires Go 1.26.10 or later, which clears the Go standard-library security advisory GO-2026-6809 in certificate handling (
crypto/x509). - The manual covers the new briefings — the reactions chapter documents the
compaction-finishednotice, itsfoldfield andAPOGEE_REACTION_FOLD, how background briefings work and what their failure reports look like. The configuration chapter, the README and the glossary have been updated to match.