so i actually wanna abandon hra, but take some learnings from it, and make a super minimal bun cli. we still need the auth and cloud stuff so other clients can connect, but no ui, and we can simplify things a bit. let's make a new public repo called hraness/hot-codex.
i have the domain hotcodex.com
my goal is to be able to:
- sign into multiple codex accounts on the same machine, and track their usage, with stats synced to the cloud.
- "swap" the connected account for my chatgpt/codex application programmatically to any of the subs. it should quit the app, do the swap, relaunch the app.
- sync sessions to the cloud. support running hotcodex on multiple machines, synced to the same account. provide an ergonomic cli interface for listing and interacting with sessions, including stopping, queueing, steering, and sending messages, as well as changing model and electing fast mode. we should use my preferred defaults encoded in wrench, like basically making a reduced set of options available as the default recommended path: low (Luna Max), high (Sol Max), ultra (Sol Ultra), and a toggle for enabling fast mode. provide an ergonomic interface for reading condensed session data: just user messages and model responses should be sufficient as the default, along with turn runtime and any easily accessible metadata like files touched or git actions. there should be another command to inspect a given turn with full detail. support renaming a session, and also attaching or editing a note to a session (one note per session). sessions should default like hra to approve for me, with computer use, and all of codex's plugins, and Documents dir, and the cli should allow changing the dir/repo, but really i think about this more as projects which may include multiple repos, so a target repo is not really necessary as long as the dir gives access to a place with all the repos. support cli auth, using our established email vfn code convex auth pattern.
- make a minimally designed website with contents that match the github repo's readme, leading with the install command and instructions, and then covering features.
- be sure to utilize all the codebase conventions we've established in hra, though it's a much simpler project, like it should have a kb and property tests and writing conventions and be URP.