Local-first tooling for Claude Code / the extended read
You have explained your project to your agent more times than you can count. FrankinWOLFF decides what your agent knows, when it knows it, and how that context is organized. It runs entirely on your machine.
It is in the last stretch of testing before its first public build. When it ships, the installer, the hook engine bundle and their sha256 checksums will appear right here, served only from frankinsuite.com. Verify the hash before you run it, the same way you would with anything you download.
A note for early builds: like the rest of the suite right now, the first FrankinWOLFF release will be unsigned until code signing is in place, so Windows will warn you when you run it. That warning is expected. The published checksum is how you confirm the file is the one we built.
Five sessions, five cold starts. Everything you established in 001 is gone by 002. Session logs get pruned, context windows compact, and you type the same explanation again.
Session history disappears. Claude Code trims old session logs when it starts up. The work you did last month is not there to refer back to.
Every session begins at zero. Your architecture, your naming, the decision you made in week two and the reason behind it. None of it survives unless you say it again.
Long runs wander. By turn eighty the working context is full of stack traces and the original goal has been pushed out of view. The agent is still confident. It is just no longer solving your problem.
Your sessions stop being disposable. Retention is set once during install, and the default is 36500 days. Old sessions stay readable instead of being trimmed away.
Context arrives before you type. When Claude Code launches, hooks fire and load the project rules, the decision log, and where you left off. You start in the middle, not at the beginning.
Only what matches the task. Your notes are tagged and indexed, so the agent receives the fragments relevant to what you are working on rather than everything you have ever written.
Documentation before the thread is lost. Turn counting tracks how far you have gone since you last wrote anything down, and asks for a progress entry while the reasoning is still fresh.
A dashboard, not a config file. Pick or scaffold a project, see its state in four floating widgets, and launch Claude Code with the right environment already set.
That is one hundred years of session history. The number is deliberate. The point of a retention setting you will never reach is that you stop thinking about retention at all, and start treating past sessions as something you can actually go back and read.
The whole installer. Written for people running Claude Code twenty or more hours a week on modest hardware, which is where context loss hurts most and where heavy tooling is not an option.
Nothing leaves your machine. No account, no sync service, no telemetry. Your project context is a set of files on your own disk, in formats you can read without this program.
Distributed from a domain we own. No code host, no marketplace, no storefront that can remove it. The download below is served from frankinsuite.com and nowhere else.