Rivet Works note

Codex changed one part of the Rivet Works path

Related build: Rivet Works

A lot of what I was doing in Rivet Works, specifically in the VS Code extension, is changing now that I am using the Codex extension more heavily.

I find myself needing the TODO extension less. For many TODO notes, I can tell Codex to update a doc in the repo. Later I can start a chat, tell Codex to read it, and decide what to work on next.

What still feels useful

Rivet Core desktop is still useful in my daily flow.

Current thought

I am questioning how far to continue the exact VS Code TODO-extension avenue, while still seeing clear value in Rivet Core and related tooling.