Rate Your Flow
Flow report↗
82/100
illustrative
illustrative
See the shape of
how you
work.
Rate Your Flow reads your recent coding sessions and returns a local HTML report about the habits inside them.
Supports Codex and Pi session history. No client API key.
Illustrative flow
build the first pass09:14
untangle auth state10:02
ship report renderer11:38
trace the hard edge13:20
Sessions branch. Patterns emerge. Your report stays on your machine.
01 Latest 50 active sessions
02 Last 90 days
03 Local HTML output
Install from the GitHub release
One install. One command.
npm install -g https://github.com/ram4-dev/rate-your-flow/releases/download/v0.1.7/rate-your-flow-0.1.7.tgz
Run ryf after installing. Remote analysis requires a configured backend and your consent. For access, contact @ram4_dev or email Ramiro.
A small command, a useful mirror
From scattered work
to a readable signal.
-
01
Find the recent work
Ryf looks at your Codex and Pi session history from the last 90 days, then selects the 50 sessions with the most recent activity.
-
02
Show you the boundary
You see a preview before any remote analysis. The preview is redacted and does not send anything.
-
03
Make the report local
With your consent and a configured backend, a bounded redacted digest is analyzed. Ryf writes the finished report as HTML on your machine.
The output is yours
A report you can
open, keep, and revisit.
One local file turns a long stretch of work into a clear review. It is built for the end of a week, a release, or the moment you want to understand why progress felt easy or hard.
Read the project on GitHub Watch the 27-second demoRYF / SEPTEMBERLOCAL REPORT
Your work had a direction.
You moved quickly through exploration, then slowed at the handoff. The strongest sessions made the next decision visible.
Reliability88
Communication81
Context efficiency76
Productivity85
Hygiene80
Illustrative total: 82, the simple average of these five illustrative scores. Based on a selected session sample.
Privacy without vague promises
You choose when analysis leaves your machine.
Ryf does not send raw session histories as a background step. When remote analysis is available, it asks for consent and sends only a bounded, redacted digest. Your final report is generated as a local HTML file.
↳ Preview first, no send
↳ Explicit consent for remote analysis
↳ Local report output
Questions
The practical details.
What happens when I run ryf?
Ryf finds eligible local sessions, prepares a redacted preview, and writes a local HTML report after a consented remote analysis. A backend must be configured for that semantic analysis step.
Which sessions are used?
The report uses the 50 sessions with the most recent activity from the last 90 days. It supports session history from Codex and Pi.
Does it need my API key?
No client API key is required. Analysis access currently depends on a configured backend and an explicit consent prompt.
Where does the report go?
Ryf produces a structured HTML report locally, so you can open it in a browser and keep it with your own files.
A better review starts here
Rate Your Flow.
Want to try it or help shape the public release?