Skip to content

v0.2.2 — A Light in Dark Places

Choose a tag to compare

View all tags
@shiv207 shiv207 released this 22 Oct 18:35
· 35 commits to main since this release
v0.2.2
fc99fad
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

"May it be a light to you in dark places, when all other lights go out." The graph that used to light up only at the end now lights up as you work, and the updater has somewhere to walk.

v0.2.2 is a patch release. The side-panel graph builds live, the "Invalid prompt" error is closed off at the last step before the request, and rift upgrade is a walk to Mount Doom.

The Phial of Galadriel: the graph lights up as the agent works

  • It appears the moment work starts. The panel was drawn from the plan, the session diff and graphwrite. The diff only arrives after the turn, and models rarely write a plan or call graphwrite, so in an ordinary run it stayed empty until the very end. The task is now the root from the first second.
  • Files show up as they are written. They are read from the edit tools while they run, and merge with the finished diff without duplicates.
  • Each edit lands under the step that was active. RIFT replays the todowrite calls in order, so an edit is credited to the todo in progress when it happened, not the one in progress now.
  • No plan, still a shape. Edited files are grouped by directory, with the directory of the newest edit marked active.
  • A graph the agent declared keeps moving. Edits none of its nodes list yet appear under it as "Edited since the last graph update". The agent's own nodes are never changed.

The Black Gate stays shut: "Invalid prompt" is closed off

  • One last check before the request. RIFT keeps its own markers in part metadata, and one reaching providerOptions ends the session with "Invalid prompt: The messages do not match the ModelMessage[] schema". v0.2.1 stopped one route in. That marker has now come through two routes, so the final message list is checked just before it goes to the SDK and anything that is not a record is dropped. A marker added later cannot end a session either.
  • Run against the real failing prompt from a session log, it had one invalid message before the check and none after.
  • A TUI that was started before v0.2.1 keeps its old code until it is restarted.

The Road to Mount Doom: updating is a journey

On a real terminal, rift upgrade shows a marker walking from the Shire while it installs:

  ━━━━━━━━━━━━━━━━━━━━━━━━◆───────  Lothlorien
  • Real places on the way: The Shire, Bree, Rivendell, Moria, Lothlorien, Rauros. The marker never reaches the end before the install does, and finishes the last stretch to Mount Doom when it completes.
  • A line from the books for every release, chosen from the version number, so a release always gets the same one and the next release gets a different one. The TUI's update dialog shows it too.
  • Plain where it should be. Piped output, CI, TERM=dumb and RIFT_NO_ANIMATION=1 keep the plain spinner. A failed install shows no arrival and prints the same error as before.

Install

curl -fsSL https://raw.githubusercontent.com/Datum-Collective/RIFT-coding-agent/main/opencode/install | bash

Already on RIFT? rift upgrade.

Assets 14
Loading