Repository navigation
Releases
Sage 6.0.1 - the app wears the site's colours
The app now uses the palette of its own icon and landing page: a navy #080b12 canvas, sky #38bdf8 for actions and mint #6ee7b7 as the partner colour, with dark ink on the buttons and a deep-blue/teal light theme. Landing page, web app, iOS shell and desktop build all share one set of tokens again.
- public/styles.css + public/docs.css: brand, surface and info tokens replaced; no indigo (#6366f1) remains.
- package.json: 6.0.1.
Sage 5.0.3 - name the refusal
When Cerulean answers /admin/callback with an error parameter, or with no code at all, the panel used to post the empty string to the token endpoint and surface the generic invalid_grant that came back, hiding the real reason. It now names the provider own error, logs it, and never exchanges a code that was never issued. A refused exchange that does carry a code still runs one fresh attempt. Server-side only.
Sage 5.0.2 - a refused sign-in tries once more
An authorization code is single use, so a second load of /admin/callback — a reload, a link prefetch, a proxy retry, a tab restored from history — arrives with a code Cerulean has already spent and is answered invalid_grant over a sign-in that had in fact worked. The callback now starts one fresh attempt automatically, marked in the signed SSO cookie so a genuinely broken configuration still reports its reason instead of looping. A browser that already holds a session goes straight to the panel. A refused exchange carries the provider's own description and logs it; neither the code nor any token is logged. Server-side only: no app build is needed.
Sage 5.0.1 - sign-in that survives a reload
The admin callback exchanges an authorization code once, so a refreshed callback URL, a restored tab or a back button used to end in invalid_grant from Cerulean over a sign-in that had already succeeded; a browser holding a session now goes straight to the panel. A refused exchange also reports the provider's own description and logs it, so an expired code can be told apart from a replayed one or a PKCE mismatch. Neither the code nor any token is logged. Server-side only: no app build is needed.
Sage 5.0 - share a course
A read-only link to a course or a single document, opened by anyone holding it with no account: the notes and the documents, with the sharer's name on what they contributed. A share is a snapshot, not a window — it carries no memory, no answers and no settings, it cannot be written to, and it expires after thirty days. Shared documents are stored once by content hash, so the same handout shared by two people is one file with two names on it.
Sage 4.9 - accessible and multilingual
Capture state and every finished reply are now announced rather than only drawn, each reply naming the page it was grounded on and whether it came from the copy cached on the device. The citation viewer takes focus when it opens, keeps Tab inside itself, closes on Escape and gives focus back; choosing a tab lands focus in its panel; fields that hold material carry their own labels and direction. The course language sets the document's direction: Arabic, Hebrew, Persian, Urdu and Sorani render right to left, while page labels, code and citation chips stay left to right inside the sentence so punctuation is not mirrored.
Sage 4.8 - documents that work offline
Every foundation document is now kept on the device as well as in the workspace, under its own budget with a content hash, evicting the least recently used. The Foundation panel says which documents this device can ground on, and reconciling with the server refreshes the copy whose text changed and lets go of the ones the course no longer holds. A question asked with no connection is kept with the documents it was asked against, and its reply cites the cached copy by name and page.
Sage 4.7 - handoff between devices
A session in progress now moves between devices. The live session record - course, the notes so far, and which device holds the microphone - is written while a lecture runs rather than when something is saved, so opening the app on the laptop mid-class offers the phone's session and carries its notes across, deduplicated by what they say. There is one microphone: when a device starts capturing the other stops and says so. Newer wins, a late heartbeat cannot rewind the record, and a record with no heartbeat for four hours is gone.
Sage 4.6.1 - background listening
Listening survives leaving the app on iOS, and no longer interrupts an audiobook. iOS gives an app one audio session and the WebView's microphone borrows it: on default settings opening the microphone interrupted whatever was playing, and switching to another app ended the capture. The native side now sets play-and-record with mixWithOthers, holds the session while listening, and takes it back after a call or alarm. Screen capture was already a ReplayKit extension; this is the audio-only path.
Sage 4.6 - spaced revision
Spaced revision. What a practice paper lost marks on, and the quiz items and answers the model was under 60% sure of, become a review queue: a question returns after 1, 3, 7 and 21 days each time it is answered right, a miss returns it to tomorrow, and four in a row retires it. The Review tab asks only what is due, in a session sized to five minutes, with the backlog, the streak and the next date stated plainly. The queue is kept on the device, per course.