Your agent gives you a resume command
To continue this session, run codex resume 019e... claude --resume <SESSION_ID>
> paste. store. resume.
rizum saves Codex and Claude Code resume commands, organizes them by project and milestone, and relaunches the right session from your terminal.
Local SQLite. No account. No telemetry.
rizum stores the resume command your agent gives you, then lets you find and relaunch it later.
To continue this session, run codex resume 019e... claude --resume <SESSION_ID>
$ rizum add -P my-app -M auth \
-N "fix login flow" \
"codex resume 019e..." $ rizum project my-app # select the session # press o to resume
rizum is not a dashboard. It saves CLI resume commands, groups them, relaunches them, and records local run time.
Capture codex resume ... or claude --resume ....
Keep sessions under a project and milestone like my-app/auth.
Open a project, select the session, and press o to relaunch it.
When rizum launches the agent, it records how long the process stayed open.
Use commands for quick capture, or stay in the terminal UI when you need to navigate saved Codex and Claude Code sessions.
You need Rust and Cargo via rustup, git, and on Linux a C compiler toolchain.
$ sudo apt install git build-essential $ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh $ cargo install --git https://gitlab.com/pidev.fun/rizum.git --locked
--locked uses the repository lockfile for a more reproducible install.
$ rizum doctor $ rizum project my-app
$ rizum add -P my-app -M auth "codex resume <SESSION_ID>" $ rizum new -A codex -P my-app -M auth $ rizum new -A claude -P my-app -M auth $ rizum time # shows recorded agent run durations
When rizum launches a session, it records how long the agent process stayed open. Useful as a rough activity signal, not as precise time tracking.