Understand your local usage report

Roodof __PLER_VERSION__

Roodof reads retained Claude Code and Codex logs on this computer. It calls no model, sends no report to an external service and does not change the agents' logs. This help works without an Internet connection.

Three terms, three different meanings

Account limits

Limits applied to your account by the provider. Roodof shows the latest recorded samples; it does not query your provider account live.

Usage alert

A token or dollar threshold you set for one session. Roodof alerts at 80% and 100% while open; it does not change account limits or stop the agent.

API price equivalent

Recorded usage calculated at standard API prices. This is not your actual bill or subscription spend. Unpriced usage is unknown, not free.

Windows installation

Close Roodof and run PLER-Setup-0.9.28.exe. Administrator rights and a separate Python installation are not needed. Roodof installs for your user account and opens; use Start or the desktop shortcut afterwards. A same or newer installed version is kept; an older version is replaced only while Roodof is closed. Installation does not delete your history or agent logs.

Removal from Windows Settings → Apps keeps saved history by default; deleting history is a separate explicit choice. The portable ZIP is also available: extract the entire package into a new folder and open Roodof.exe. Roodof-Demo.cmd in the ZIP opens invented records. Compatible desktop updates can be selected in Updates. This is a free beta without a Windows publisher signature; clean-Windows and real-user acceptance remain pending.

One next action at first launch

After reading finishes, See your sessions opens all-time sessions when records are ready. Add a log folder opens source settings when no records are found. Inspect the issue opens diagnostics for read issues or unusable files. Missing records are not assumed before the first read finishes.

Other options keeps retry, help and skip. Available sessions remain accessible there when some records could not be read. Inspecting sources/issues does not mark setup complete. Seeing sessions or explicitly skipping is remembered; reopen from Settings → Record sources → Getting started. The interface tour never starts automatically.

When you cannot find a session

Empty results show the active period, agent, project and optional record-status filter. Search all time widens only the period; Search all projects only the project; Search both agents only the agent. Search text and other choices stay selected. Clear search removes only text and keeps the record-status filter. Other options can offer further recovery actions and an explicit clear-all action.

Use Add a log folder for another installation, or Inspect read issues for unreadable records. Try again retries the current selection after a connection failure. These actions do not guarantee a match; Roodof shows the local records it can read. Search text is not added to API queries or persisted view preferences.

Work linking and Settings

In a session, open Link to a work. If other works are available, choose Link existing work or Create new work; only the selected form is visible. Otherwise the new-work form opens. Collapsing keeps the draft; membership changes only when saved. Linked works and unlink controls stay visible outside the editor. My work → Add sessions preselects the chosen work.

Settings has Record sources for folders and getting started, Usage alerts for watched sessions, and Backup & support for recovery, history, reconnection, diagnostics and reports. Open a tool row to continue. Switching groups performs no write and keeps entered fields. Use Left/Right, Home and End on group tabs. Read-issue and reconnection shortcuts reveal the target tool directly.

Find a session and set an alert

1. In Sessions, search by title, project or model. Press / outside an editor to focus search. Agent and period filters define the main scope. Use Columns to customize the view; your choices are remembered.
2. Open a row. Read total tokens and input/cache/output first. API price equivalent is not your actual bill; partial and unavailable records are labelled.
3. Open Usage alert → Set an alert. Choose tokens or dollars, pick a quick threshold or enter your own, then Save alert. The threshold covers total usage since the session began. Roodof notifies at 80% and 100% while open; it does not stop the agent. Saved alert state is shown separately from your draft.

Models, full record fields and method notes are below the primary controls. Monitoring pauses when sources/pricing are incomplete or observations are stale; logs may arrive late. Settings → Usage alerts returns you to watched sessions.

Your first useful result

1. Open the desktop beta. Extract the entire Windows ZIP into a new folder and open Roodof.exe. Python and the desktop runtime are included. To explore invented records instead, open Roodof-Demo.cmd; demo work disappears when it closes. Close the demo window before opening your own records.
2. Find your sessions. The first-use screen checks local Claude Code and Codex records. Choose See your sessions. If records are missing, use Add a log folder, check your filters, or open Settings → Read status and diagnostics. No provider account is connected and ChatGPT web conversations are not included.
3. Name the work and link a session. Create a work item in My work, open a session's details and link it. Identify sessions by available title, project, agent, time or code. Missing titles are explained in details. Work totals cover whole linked sessions within the main filters; they do not establish an exact task cost.
4. Choose an optional session warning. Set a token or dollar usage alert in session details. Dollar thresholds use the API price equivalent. Warnings occur at 80% and 100% while Roodof runs. Up to 20 selected sessions are monitored roughly every 10 seconds; this is an alert, not an agent stop or a provider spending cap. Dollar figures are comparison values, not a subscription bill.

The beta is free and needs no Roodof account. Close the desktop window to stop the app and its monitoring. Terminal/Python installations still open a browser. To move from 0.2.31 or earlier, close the old app and extract the new desktop package into a new folder; the first transition is manual. Keep a checked private backup.

Start and choose your data

Open Roodof normally to read your own logs. Use pler demo or the Windows package's Roodof-Demo.cmd for invented data only. The demo never reads your agent folders.

Use the complete startup address printed by Roodof when opening a tab manually. It grants access to that running report; do not share it. After an update, close Roodof and reopen it using its new startup address.

Default sources are Claude Code's local projects folders and Codex's sessions and archived sessions folders. Your selected roots and readable files determine coverage; finding files does not prove complete account history. Use Settings → Log folders to choose, check, add or remove an extra source without a terminal. Choose the agent home (.claude / .codex) or its projects / sessions / archived_sessions log folder. Standard sources stay enabled. Removing a source does not delete original logs or retained private history. Extra folder selection stays on this computer and is not restored from a backup; reselect it after restoring history. Private backups can contain source paths from retained history. Environment variables and terminal folder options remain supported. WSL roots must be explicitly selected and the distribution must already be running.

pler --version shows the installed version. The version in this help belongs to the running installation.

Read the period and quality correctly

Active sessions: a period selects sessions by last activity and includes each selected session's full recorded total. A session spanning several months can therefore contribute its full total to a seven-day active-session view.

Dated usage within the period: this is limited to complete, unambiguous usage records with stable response identities and usable recorded times. The end is fixed at the scan's observation time. Cumulative or unresolved histories cannot be allocated to dates and are excluded with coverage information. The page and terminal show it only when every selected session's usage could be dated; otherwise only the JSON export carries it, with its coverage counts. Do not treat the dated subtotal as complete account usage.

Token components add up as shown; reasoning is already part of output. Tokens are not prices, savings, work quality or a worker ranking. Unknown usage or attribution must remain unknown. Use the quality controls to find affected sessions before making a comparison.

Project and agent filters select report rows. Quota meters remain account-wide. Session search narrows the list rather than the exported summary. Check the main filters before downloading JSON.

Read the exact accounting and observation contract

Keep history and reset a cache safely

Roodof stores private local metadata: counts, times, identities, models, project paths, branch names and edited targets. It does not retain prompt, reply, command or tool-output text in its metadata cache or archive.

The default local folder is %LOCALAPPDATA%\pler on Windows, ~/Library/Caches/pler on macOS and ~/.cache/pler on Linux. PLER_CACHE_DIR changes that folder. The rebuildable reader caches and retained history currently share this folder.

Do not delete that whole folder as a cache repair. The file metadata-archive.json may be the only remaining copy of metadata from deleted agent logs. It cannot be rebuilt when its source no longer exists.

• pler cache reset removes only known rebuildable caches: the log readers' and the code counts. The Roodof archive, quota samples and retention preferences stay in place.
• pler archive off pauses archive use and new retention without deleting the saved archive. pler archive on enables it again. Live logs can still be read while retention is off.
• pler archive clear immediately removes retained archive history. The page's clear action asks for confirmation. Clearing does not change agent logs; metadata from already-deleted sources is lost permanently.

Default and environment-selected sources can be retained. A one-off --claude-dir or --codex-dir report selection is not archived. The archive drops files unseen for 365 days and is limited to 2,048 files and 64 MiB. Coverage warnings identify lost or unverified history. Removing the application does not automatically erase this private data folder.

If you need to preserve retained history, close Roodof before making a private backup of the archive. Treat it as sensitive local metadata and do not attach it to a support report.

Recover history in the app

Settings → Backup & support → Back up & recover → Recover history from a backup: choose a trusted private Roodof ZIP, select Review contents, choose an existing local parent location and select Prepare location. Review the version, date, counts and new destination, then explicitly confirm Recover into new folder. Open history is never overwritten. Reviews changed in another window or older than ten minutes must be repeated.

After recovery, save drafts, confirm the switch and select Open recovered history. The old window and readers close before the selected history opens. Normal desktop launches remember the choice; Return to previous history switches without deleting either history. Launches with an explicit data folder or environment override remain scoped to that run; terminal commands keep their existing scope. Browsers can recover a folder, but opening it requires the desktop app. Recovery is disabled in demo mode.

Original agent logs and machine-specific log folder selections are excluded from backups. Add custom log folders again in recovered history. Backups and recovered folders can contain private paths/work notes and are unencrypted. Validation does not establish who supplied a file. If a disk error leaves the outcome uncertain, reload status before starting another recovery. An unavailable selection opens the starting history with a warning; malformed selection files are preserved.

Back up and recover your Roodof history

In Settings → Backup & support → Back up & recover, choose Download private backup. The backup contains retained metadata, session verdicts, the retention preference, saved Claude quota observations, your work names and links, verified local session identities and usage alert settings. It covers saved data regardless of report filters; it does not scan original logs. Reader/code caches, demo data, agent settings and the running page's access token are excluded.

This file is private and unencrypted. Unlike a masked JSON report, it includes original source/project/edited paths and retained identifiers. Store it privately; do not send it as a support attachment. SHA-256 checks detect damage, not a trusted publisher or a maliciously rewritten file. Use only your own trusted backup.

Choose Check backup to validate a selected file on this computer and see its date, version and counts. The check does not restore data. Confirm in your browser downloads that a prepared backup was actually saved.

Terminal equivalents:

pler backup create "my-history.pler-backup.zip"
pler backup check "my-history.pler-backup.zip"
pler backup restore "my-history.pler-backup.zip" --to "recovered-history"
pler --data-dir "recovered-history"

For terminal commands, the Windows portable package uses PLER.cmd instead of pler. The destination must be a new local folder with an existing parent; existing folders and files are refused. Restore validates first, prepares a complete separate folder and leaves the current data unchanged. For terminal launches, open that folder explicitly with --data-dir on each subsequent launch, including backup commands. No current profile is switched automatically.

Recovery keeps original times, reader versions and source roots. To replay history, use the same selected source roots on the same computer. Moving source paths or recovering onto another computer is not automatically remapped. Original logs are not in the backup; never-read deleted logs cannot be recovered. Retention age/size limits and old-reader warnings still apply, and old quota samples stay old. Keep the previous data folder until you have checked the recovered report.

Interpret quota and observations

Account limit warning: the page warns at the top when a limit is reached or will fill within an hour at the current pace (a weekly limit: within a day). Watch account limits reads the logs again every 5 minutes while the page is open; desktop notifications show each new warning once if the browser allows them. The warning is a forecast from the last samples, not a provider message.

Quota values are dated local samples, not a live provider-account lookup. Old or elapsed samples are shown as unknown/stale. A forecast assumes the observed pace continues. Contradictory mixed-meter history cannot support a trustworthy forecast. Small falls of a few points and an early provider reset are normal meter behavior, not contradictions.

Recorded usage and plan prices: the last 30 days of dated recorded responses at standard API list prices, alongside the selected or logged plan's monthly list price. This view uses all selected source folders and all projects, independently of page/report filters. The exact interval is shown in UTC. Actual payment, discounts, credits, extra usage and historical plan membership are not verified; a low recorded equivalent does not prove savings or subscription value.

Unpriced responses remain unknown, not free. Read failures, lost or unchecked archives, unreconciled usage, conflicting meters and multiple source groups withhold unsupported conclusions. A lower-plan threshold comparison requires fresh samples on at least 14 distinct UTC dates spanning at least 14 days, without a gap over two days. These are Roodof's minimum observation rules, not provider guarantees. Even then, the comparison is conditional on the plan assumed for those samples and does not establish that a smaller plan would be enough. The comparison expires when required samples become stale or their reset passes; the open page updates that message without changing your plan selection. Ultra's five-hour exemption depends on account verification; its overall fit is not inferred from a weekly-only meter.

API price equivalent: what the recorded responses would cost at the providers' public standard prices, each by its own model and prompt size. It is a comparison point for a subscription or budget, not your bill. Responses without a published price are left out and the priced share is shown. Roodof measures retained records only. Requests absent from those records cannot be counted, and no general error margin has been established.

Did it pay off? Your one-click verdict on a session, Useful or Wasted, saved only on this computer. Roodof sums tokens and the list-price equivalent per verdict for the selection. It records your judgement; Roodof does not infer quality.

Tests and builds: Roodof recognises the agents' own test and build commands and shows how the last run with a visible result ended. The command text is read only in memory. A result is not visible when the output was piped on, the command ran in the background or another step followed. A passing run does not prove the work is right.

Claude Code quota needs the optional terminal status line. pler statusline --install shows the proposed setting and asks before changing it; pler statusline --remove removes only Roodof's own unchanged line. Ordinary Claude desktop conversations and desktop quota capture are not demonstrated coverage.

Code still in place: for commits made during a session that are still in the current HEAD's history, the share of the lines they added that HEAD still has, counted by content. File contents are read only in memory. A rewritten line or a moved file counts as not kept; kept code is not proof that it is right.

Git activity is a time association and does not prove who made a change or whether it was useful. A subsequent-edit pair means independent nonoverlapping sessions named a shared target within seven days. The gap is between session boundaries; whole-session tokens are not the cost of that edit.

Share and get help

JSON can include shortened project labels, dates, models and counts. It is reduced, not anonymous. Review the selection and private names before sharing. Never send the startup access link, access headers, complete logs, cache/archive files, credentials, prompts or command output.

To report a problem, record the application/parser/schema version, operating system, runtime/package, browser, expected result, observed result, quality reason and a minimal invented example. Use the support address below; no response-time guarantee is promised.

Roodof is a personal local application. Shared-server hosting, team roles, complete billing/account reconciliation and mixed-account identity are outside the demonstrated scope. Automated tests exist for Windows, macOS and Linux; clean-machine installation, real browser/screen-reader coverage, signing and a professional pilot are separate release checks. This early beta is unsigned.

Link sessions to your work

In My work, create a short name for an actual task. Open a session's details and link it to one or more work items. You can rename an item, remove a session link, or delete an item after reviewing the confirmation. Deletion removes only the work item and its links, not logs, usage, session verdicts or copies in older backups.

Work subtotals follow the main period/agent/project filters and include each selected session in full. A shared session appears in several work subtotals, while the overall assigned-work summary counts its usage once. Do not add work subtotals. This does not split one session between tasks or prove an individual task's cost, completion or quality.

Known sessions outside the current filters are separate from unavailable references. Moving a source or changing a session identity does not silently attach its link to a different session. A missing reference contributes no invented total and can be removed explicitly. Existing uncertainty about usage or attribution stays visible.

Your work names and opaque links are local private metadata in work-items.json. Ordinary JSON reports omit them even with project masking off; private backups include them. No prompt, reply or command is collected for grouping. The demo keeps its work in memory only. A damaged or unsupported store is reported and not overwritten; keep the file and recover from a trusted private backup if needed.

Close, remove or get help

Close the Roodof desktop window to stop the app and its monitoring. In terminal/browser mode, use the page's Close button or Ctrl+C. On Windows, the portable package can be removed by deleting its extracted folder after the app closes. Private data stays separately in %LOCALAPPDATA%\pler or your selected data folder. Back up retained history before removing that data. If you enabled Roodof's optional Claude status line, remove that integration before removing its installation; see the status-line instructions above.

Support: plersolutions1st@gmail.com. Include your version, operating system and the step that failed. Do not include conversations, private backups or startup access links. The application does not send this email or upload a report.

This is an unsigned early beta. Physical clean-machine, platform and screen-reader checks remain separate open acceptance work.

When records are missing or uncertain

Start with the reason in Before comparing these records. File access warnings cover all selected source folders, even if the current page filters exclude their sessions. Session and price explanations follow the main filters. Search and the affected-session list filter do not change totals.

• Temporary read or access failure: let the agent finish writing, check your read access to the selected folder, then choose Read logs again. A persistent malformed record may need support for its format; do not edit the original log to hide the warning.
• Stopped or unavailable WSL: open the distribution yourself and check its selected log folder before reading again. Roodof never starts a stopped distribution.
• Older or unchecked Roodof archive: make the original selected source accessible and re-read it if it still exists. Without originals, keep the saved metadata with its quality limits. Rebuilding the reader cache cannot verify an old interpretation.
• Deleted sources: retained metadata remains usable within its original quality limits. Back it up before removing local data. An earlier checked private backup can be restored into a new folder; see recovery steps. Neither a retry nor a cache rebuild can recreate originals. Logs deleted before Roodof ever read them cannot be recovered, and Roodof cannot detect how many such logs existed.

What you can conclude: inspect recorded values and affected sessions. With missing usage or uncertain attribution, a lower total or different split does not prove savings or improved efficiency. Unpriced usage is unknown, not free. The API price equivalent is not a subscription bill. None of these warnings establishes current account quota.

Cache and archive are different: Rebuild reader cache resets only rebuildable reader/code caches and reads sources again. Use it for a suspected cache problem after source access is working; it does not repair permissions, missing history, unsupported formats or reading limits. Clear Roodof archive deletes retained history and is not a repair step. Preserve the archive and backups.

Reading limit or excluded path: page filters are applied after reading and cannot fix these problems. For a separate terminal inspection, use pler report --days 0 --claude-dir PROJECTS_FOLDER --codex-dir SESSIONS_FOLDER. Both folder options are repeatable and replace that agent's default discovery for this report only; they do not change the open page. Use supported local folders, not individual files. Do not change or split original oversized records or turn off path protections. If a single source still exceeds a limit, keep it unchanged and report the safe reason code, version and an invented example to support.

Record a work's goal and your outcome

Choose a work in My work, then open Edit goal and outcome. Enter the intended result and an optional result/remaining-work note, up to 1,000 characters each. Choose Not assessed, Partly completed, Completed or Not completed, then save. These are your entries, not a Roodof quality score. The recorded outcome time is when you entered or revised the result, not a measured work finish time.

The goal and outcome describe the whole work and stay visible when filters hide linked sessions or their sources disappear. Recorded observations below follow the main filters: each linked session's latest visible test/build result, and sessions with coincident Git activity. Counts are sessions, not individual test cases or distinct commits. Missing evidence stays unknown. Passing tests never complete a work automatically; failed tests never replace your outcome.

Drafts survive work selection, filter reads and language changes in this open window. Save them before closing the app. Discard draft and use saved cancels local edits without a write. If another window changed the saved goal or outcome, Roodof keeps your draft and shows the latest saved version. Review it before keeping your draft for a later explicit save or discarding your draft. A disconnected save needs a saved-work reload before retrying because the first request may already have succeeded.

Titles, goals, outcome notes and links are private local metadata. Ordinary JSON reports omit them even without project masking; private backups include them and are unencrypted. Deleting a work removes these entries and links, not source logs, session verdicts or copies in older backups.

Earlier work files open without rewriting them; the first real edit saves the new work format. Older Roodof builds may not read that format. Keep a checked compatible backup before returning to an older build; recover into a new folder rather than overwriting current data. No provider, task account or PR is linked or queried by this feature.

Missing titles and read diagnostics

A session can use its work/project name even when usage records were read. Open its details to see the title reason. Title indexes are read up to 4 MiB each and 64 MiB per refresh, newest sessions first. Claude rename lookup reads the first and last 64 KiB of the original transcript; a rename in the middle may be missed. A bounded or partially read title is not guaranteed to be the latest rename. Titles are not archived; retained-only sessions use a fallback. WSL title files outside the permitted selected-root scope are not read.

Open Settings → Read status & diagnostics for fixed reason codes and next steps, independently of screen filters. A failed new attempt keeps any previous usable snapshot; its read time is shown so old counts are not mistaken for a successful new read. You can open Settings even before any successful scan.

Download diagnostics saves only Roodof version, read time/state and fixed codes/counts. It contains no log contents, session titles, provider/session IDs, private paths, raw exceptions or access keys; it is not sent automatically. This is separate from a private history backup, which can contain private paths and work metadata. Keep original logs and retained history when retrying; clearing history does not repair a failed read.

Reconnect settings after a move or copy

Close older Roodof windows first. Add the new local or already-running WSL log folder and read records again. Open Settings → Reconnect a moved session’s settings. Select old settings whose record is missing or only in retained history, then a currently loaded live target. Searches page through all loaded records, independently of report filters and the separate 400-session work picker.

Choose Preview transfer. Work links move once per work; the target’s other links, work notes and frozen follow-up history remain. If reviews or alert thresholds conflict, explicitly choose which to keep. Check the target code, tick the confirmation and choose Reconnect settings. Notification history follows the chosen threshold. Incomplete sources or pricing can still pause monitoring. Usage totals are not combined and physical identity is not certified.

Undo last transfer reverses affected memberships/settings while preserving unrelated later edits and work notes. Changes to an affected membership, review or threshold block undo. A new transfer replaces the previous undo copy. Clear undo copy removes only that private local copy. It can contain saved work notes and annotations; it is absent from regular reports and private backups. Backups contain the resulting annotations.

Interrupted writes are completed under the shared metadata lock before this version exposes annotation files. An unexpected external edit or corrupt recovery file stops changes and is preserved. Close Roodof and privately preserve the whole local data folder and a checked backup; do not send the recovery file to support. Agent logs, session codes and accounting formats remain unchanged.

Navigation

Language, Help and Updates are in Settings → General. Close the desktop app with the Windows window button. Record review is a separate page for coverage, observations, calculation methods and chart guidance. Its counter separates all observations from warnings.