Token usage, notes, and repository insights

Use Token Usage to review recorded AI activity, Notes for personal working documents, and LOC History or Treemap to explore a repository's size and changes. These features are available in Logonomic Free, Logonomic, and Logonomic Pro; usage and quota figures depend on what each provider exposes.

Contents

• Token Usage
• Check account quota
• Notes
• Repository LOC History
• Tracked Files Treemap
• Usage dates and measurement reference
• Preserve or recover usage history

Token Usage

Open Token Usage to see usage from your configured CLI profiles. Its calendar shows dated token activity; Accounting history and the repository table preserve accepted totals and their recorded details.

1. Configure your CLI launcher and profile in Launchers.
2. Open Token Usage and let saved history load.
3. Select the source profiles to include.
4. Click the circular-arrow recount button beside the total to scan their local history.
5. Choose the date basis beside the calendar, and read its explanation. Hover an accounting total for its token breakdown and any recorded cost.

Not scanned means the profile has not yet been counted. Loading, Queued, and Not loaded are progress states, rather than zero usage. The bundled OpenCode integration does not supply Token Usage figures.

Select accounts and dates

Click a source row to include or exclude it. This selection controls the calendar, combined total, repository table, and profiles scanned by the main recount button. A single source is always included; with several sources, keep at least one selected.

The calendar covers the most recent 365 days, including today. Click a square for one day or drag across squares for an inclusive range. Press Escape while the calendar has focus, or click unused calendar/page background, to return to the full year.

Source-row activity totals follow the selected dates. Choose Dated activity · … for proved token increments in the named desktop timezone, or Provider dates · … when a source supplies evidence in its own calendar. Provider dates keep that recorded meaning; they are not converted to the desktop timezone.

Accounting history · all accepted records, including its categories, costs and repository amounts, does not follow the activity range. Its coverage shows Instant evidence, Provider-dated evidence and Daily evidence unavailable. These amounts describe the accepted history as a whole. The unavailable amount is not usage assigned to the selected dates.

Saved lifetime summaries, when available below the rows, have their own dates and do not follow the selected range. They are reported separately and are not added to the charts.

Read totals and costs

Token Usage counts local CLI history on this workstation, including readable history from use outside Logonomic. It does not cover all activity under the same login on other devices or services. A source profile identifies the history being read; changing that profile's signed-in account does not reassign its older usage to the new account.

The activity calendar counts only total-token increments whose dates are established by source evidence. A cumulative conversation total or a latest activity date alone cannot establish those increments. Missing or conflicting date evidence stays outside the daily calendar while the accepted accounting remains available. An unavailable daily figure is not verified zero.

Hover an accounting total for the provider-defined total, input/output and cache categories, and Observed cost where available. These details cover accounting history, independently of the activity range. Categories differ by provider and can overlap—for example, cached input may already be part of input tokens. Use the provider's total rather than adding every category.

Observed cost comes from source records. A suffix such as 3 of 5 records describes partial coverage; an absent cost is unknown, not zero. It is not a calculated invoice or remaining subscription allowance. The combined tooltip groups breakdowns and costs by provider, and those subtotals can overlap across copied profiles.

Two profiles can contain the same history. Accounting history retains each profile's total, while combined figures remove duplicates where there is sufficient evidence. For example, profiles containing 1,000 tokens and the same 1,000 plus 300 can retain accounting totals of 1,000 and 1,300, with a combined total of 1,300. Hover a duplicate indicator to see each source's contribution.

Estimated or a ~ prefix means some selected information is incomplete or duplicate removal is uncertain. Hover for the reason. Dated activity can cover only part of the accepted history; Logonomic does not spread the remainder across days or move it to a conversation's latest date. A calendar record count refers to contributing usage records, not terminal sessions. Use the Sessions panel for terminal/session history.

Read the explanation below the account/calendar area and its day and account tooltips alongside Usage date reference. It identifies the selected basis and any unavailable evidence. Proved earlier activity can remain in its original day even when the conversation later continues.

Repository usage table

The table allocates the selected sources' accepted accounting history to repositories, independently of the activity calendar's dates. Click a column heading to sort by repository, provider, or Displayed total; click again to reverse the order. Hover a name for its checkout path. Linked worktrees may appear beneath their main checkout, with each row retaining its own usage.

Unattributed includes tokens that could not be safely assigned to a repository. Other repositories combines smaller entries when the table is very large. Both contribute to the displayed total.

Wait for Loading or Updating to finish before using the table. If repository detail is unavailable or inconsistent, read its message and the source statuses rather than treating the missing allocation as zero activity.

Recount, stop, repair, and reset

Use the circular-arrow button to recount selected sources, or right-click a row and choose Recount source history for that source alone. Recount reads existing local history and updates saved results; retained figures can survive even when their original source files are gone.

Choose Stop to cancel an active scan, then wait for Stopping scan… to finish. Previously accepted results remain when a scan is stopped before completion; Stop cannot undo a result already accepted.

A failure banner names the source and offers an appropriate action:

Use an ordinary recount or the offered repair first when you only need updated figures. Clear & Rescan… opens Clear saved source history? Choose Not now to leave history unchanged, or Clear & Rescan to rebuild only that source. Other sources keep their accepted figures. Deleted or unreadable CLI history cannot be reconstructed; rebuilding can reduce the selected source's totals.

Before rebuilding, Logonomic preserves the whole profile's accepted detailed usage history. Readable history becomes a verified Before Clear & Rescan copy in Saved usage history. Damaged originals are retained separately for investigation. If preservation fails, the rebuild stops and accepted history is kept; read the diagnostic before trying again.

The calendar's context menu also offers Full Reset, which rebuilds detailed usage for all configured sources, including those outside the current selection. Only CLI history that still exists and can be read can be reconstructed.

Full Reset opens Rebuild all usage history? Choose Not now to leave history unchanged, or Save copy & rebuild to continue. Logonomic saves a recovery copy of readable accepted history before replacing it; if the copy cannot be saved, the reset stops. Unreadable originals are retained separately for recovery. CLI files and separately reported lifetime summaries stay unchanged.

Let loading, migration, or another scan finish before starting a conflicting operation. If a failure says Current totals were kept, or shows Previously saved / delayed updates, the visible saved figures do not establish that the latest scan succeeded. A persistent storage error calls for recovery from a verified snapshot or support-directed repair.

Check account quota

Quota indicators show the provider's remaining allowance and reset windows. Token Usage shows recorded consumption from local history. Different time periods, other devices, and provider-specific weighting can make the two disagree.

Hover an account indicator for window names, reset times, freshness, and errors. N/A means unavailable. A failed refresh can leave an older reading visible, so check its freshness.

Open the account logo's menu for Refresh now, Check sign-in status, and refresh settings. Automatic refresh normally checks at startup and every five minutes; Manual refresh leaves updates to you. Several launchers can share a quota indicator when they use the same provider login, while their usage profiles remain separate. See Launchers, accounts, and add-ons for provider setup and account controls.

Notes

Notes are personal text documents in your Logonomic profile. They remain available as you change repositories or end sessions. Include a repository or session name in the title if you want that association to be visible.

Create and organize a note

1. Open Notes in the side panel.
2. Click Create note (the plus button).
3. Type in the new note's editor. Notes autosave about two seconds after the last edit; Ctrl+S saves explicitly.

Click a title to reopen a note. Filter notes searches titles without regard to case; Escape clears it. Sort by name or by date. Date order uses creation time, so editing a note does not move it to the top.

Rename, export, and delete

Use a row's Rename note action to edit its title, then Apply rename or Cancel rename. Escape cancels; an empty title receives an automatic Note N name.

Export note writes the note's current text to a separate file at the path you choose. An open note exports its editor text, including unsaved edits, even when saving the original fails. Exporting leaves the original note's unsaved state and save error unchanged. Choose a destination outside managed note storage. To share through Git, export into a repository and commit the copy with your normal workflow. Later note edits do not update that export.

The trash action is Move to Deleted notes. It closes the note's editors and preserves the saved text and distinct unsaved drafts. Deleted notes survive application restarts and stay there until you restore or permanently delete them. Closing a tab alone leaves the note in the ordinary Notes list.

To recover one, choose Deleted notes, find the note, and select Restore note. The restored note opens. Saved text and distinct drafts can return as separate notes. If the original file still exists, it also returns as an (original file) note, keeping changes from other editors separate from the restored copies. Check their titles and contents before removing a copy you no longer need.

To erase a deleted note, select Delete permanently, check the title in Delete note permanently?, then choose Cancel or Delete permanently. Permanent deletion removes all preserved versions and cannot be undone.

Saving, external changes, and storage problems

Closing a note normally attempts to save pending work. A failed save leaves it open with the error; correct the cause and press Ctrl+S to retry. Reloading unsaved text offers Save, Discard, or Cancel, as described in Reloading a modified document.

For editor search, shortcuts, and external-change handling, see Git, files, and diffs.

For backup, close Logonomic and copy the whole notes directory from the profile's persistent data. This preserves bodies, titles, the note list, and any Deleted notes. See Settings and reference for profile locations.

If deletion or restoration reports a storage error, keep the note and its files intact while you resolve the error. Check the active profile and file permissions. Preserve the entire notes directory before manual repair or restoring a complete backup; do not remove leftover bodies or drafts merely to clear an error. Include the message when contacting support.

Repository LOC History

Use LOC History to see how a repository's committed text size changed over time.

1. Select a repository and open LOC History.
2. Let its saved history load or its first index finish.
3. Choose Directory or Language under MODE.
4. Choose All, 1y, 6m, or 3m under RANGE.
5. Hide series you do not need, then hover the plot for date, line count, and commit.

The view follows repository selection while visible. Use Rebuild LOC history cache after new commits or branch changes when you want a fresh measurement. If indexing fails, fix the reported Git or repository problem and click Retry. Only one index job runs at a time. For No data in range, try All first; shorter ranges are measured back from today.

What “LOC” means here

LOC is the count of nonblank physical lines, including comments and other text in recognized file families. History measures complete committed trees along HEAD's first-parent chain. A merge point measures the merged tree without separately plotting every side-branch commit. Uncommitted edits are outside this view.

Only files in the recognized file families below contribute to the total. Binary files, files over 2 MiB, symbolic links, and nested submodule contents are excluded. Committed generated and vendor files count when their extensions are recognized.

Read and navigate the plot

Directory mode groups by up to two directory levels: src/widgets/private/file.cpp belongs to src/widgets, and root files to .. Language mode groups the same counted files by family.

The filled plot is stacked. Its top edge is the sum of visible series; each band's thickness is that group's count. The series list shows the latest count in the chosen range. Hover the plot to inspect an earlier sample and its commit. Dates use UTC commit timestamps.

Drag to pan through time and use the wheel to zoom around the pointer. Click the active range again to reset its horizontal view. For vertical or combined navigation, see Plot gestures.

Tracked Files Treemap

Use Treemap to find large tracked files or see where local changes are concentrated.

1. Select a repository and open Tracked Files Treemap, or its repository-details Treemap action.
2. Choose Sizes for current file bytes or LOCs for nonblank text lines.
3. Hover a rectangle for its path and measurements; click to keep it selected.
4. Double-click a directory to focus it, or a file to open it.

Larger rectangles mean larger values. Directory regions contain their descendants. Double-click the focused directory's header to go up one level; Escape clears file selection.

The map includes tracked files in the current working tree. It excludes untracked files and does not measure the total disk use of .git or deleted history. Small and zero-value files may be difficult to see; use Worktree for a complete filename list.

Diffs: area and change intensity are separate

Enable Diffs to color files by added plus removed lines relative to HEAD, including staged and unstaged edits. Replacing ten lines with ten new ones gives 20 changed lines. Rectangle area still follows the selected Sizes or LOCs measure; stronger color marks more change relative to other files in this map.

With Diffs off, double-clicking a file opens it. With Diffs on, it opens the file's diff against HEAD. Before a repository's first commit, the comparison uses an empty base.

Unchanged files appear neutral gray. If Git cannot supply changes, the tooltip explains that failure. Use a folder diff to account for untracked, deleted, binary, and other changes that this map cannot fully represent.

Refresh and unavailable measurements

Click Refresh tracked files from Git for a current view. Repository changes can also trigger updates. While updating, or after a failed refresh, the panel can retain the old map with a status message; check that message before treating it as current.

An unavailable measurement is not zero. A directory marked >= … incomplete shows a known lower bound because some files could not be measured. Binary files can have a valid byte size while their line count is unavailable; LOC counting is limited to text up to 2 MiB.

If a file is missing or will not open, refresh and select it again, then check Worktree to confirm that it still exists and is tracked.

Usage dates and measurement reference

Usage date reference

Read each figure in its selected basis:

The date-basis control chooses available evidence; it does not select an arbitrary timezone. Date-only evidence without a known timezone is not treated as an instant. Provider-saved summaries retain their supplied dates and are reported separately.

An integration can supply a conversation total without enough evidence to date its increments. Older saved history can also lack this evidence. Recounting can add reliable dated detail when the source supplies it, but cannot reconstruct missing event dates from a total. Check the source and coverage explanation before comparing days or interpreting an empty calendar.

The repository table retains at most 512 named/grouped rows, plus Unattributed. When grouping is needed, up to 511 individual repositories remain alongside Other repositories. Sorting does not change which smaller entries are grouped.

LOC History file families

Recognition ignores case. TypeScript and Qt translation files share the .ts extension, so their lines appear in the combined TypeScript / Qt translations family.

Treemap LOCs can count other readable text extensions and measure current working files, while LOC History uses this list and committed trees. Their totals can therefore differ.

Plot gestures

Preserve or recover usage history

Restore saved usage in the current profile

Use Saved usage history… in the Token Usage calendar's context menu to restore a recovery copy in the current profile in every edition, including Logonomic Free:

1. Finish or stop any active usage scan, then open Saved usage history….
2. Select a copy by its local date, source names, size, and Before Clear & Rescan, Before Full Reset, or Before restore label.
3. Read Restore saved usage history?. Restoration replaces detailed chart, source, and repository usage for all sources in this profile.
4. Choose Not now, or Save copy & restore to preserve the current readable history and restore the selected copy.

Restoration does not need the original CLI history files. It leaves launcher settings and separately reported lifetime summaries unchanged. If the saved source settings no longer match, restoration is refused and current history is kept; read the error before changing profiles or launcher settings.

Recovery copies remain available after restarting Logonomic and do not expire automatically. The dialog displays their storage location. They remain part of this local profile, so keep an external backup for protection against losing the profile or its disk. If no copy is listed, use an external backup or contact support; a recount cannot reconstruct deleted CLI history.

Damaged originals retained during reset are separate from verified saved copies. Keep them for investigation; see Usage storage problems.

Remove saved usage copies

Open Saved usage history…, select the copy by its date, sources and size, then choose Delete saved copy… in the restore dialog. Check the selected copy in Delete this saved usage copy? and choose Not now or Delete saved copy. Deletion is permanent; keep an external backup first if you may need that copy again.

The list refreshes after deletion. Current usage, other saved copies, separately retained damaged originals and external backups stay unchanged. Let an active usage operation finish before deleting a copy. If deletion fails, read the diagnostic; a partly removed copy may no longer be restorable.

Make or restore an external backup

For a normal backup, preserve the entire Logonomic profile while the application is closed; see Settings and reference. Keep original CLI history separately if you need it for future recounts. Closing Token Usage does not delete its saved history.

For a targeted backup, the shipped logonomic_token_usage_migrator exports launcher configuration and accepted token history. It excludes CLI history directories and credentials, notes, repository files, and session history. Use the copy shipped with Logonomic, close the application, and substitute your paths:

& 'C:\path\to\logonomic_token_usage_migrator.exe' --recovery-export --launchers 'C:\path\to\profile\config\llm_cli_launchers.json' --destination 'D:\Backups\logonomic-usage-2026-10-07'
& 'C:\path\to\logonomic_token_usage_migrator.exe' --recovery-verify --source 'D:\Backups\logonomic-usage-2026-10-07'

The destination must be an absolute, nonexistent directory with an existing parent. The tool reads validated configuration to find the current detailed and legacy history, including after an earlier restore. It also preserves accepted accounting caches and referenced migration proofs. Success prints Token usage recovery operation verified successfully. A failed export is not a verified backup; if the source changed during export, stabilize it and retry with a new destination.

In retail editions, restore into a fresh profile directory with:

& 'C:\path\to\logonomic_token_usage_migrator.exe' --recovery-restore --source 'D:\Backups\logonomic-usage-2026-10-07' --destination 'D:\Logonomic-restored-usage'

The same destination rules apply, and restoration refuses to overwrite an existing profile. Retail editions can select the restored profile with --user-data-dir.

For Logonomic Free, close Logonomic and its surviving runtime owners and use its shipped tool with only the source:

& 'C:\path\to\logonomic_token_usage_migrator.exe' --recovery-restore --source 'D:\Backups\logonomic-usage-2026-10-07'

Free preserves the previous configuration first and selects an imported working copy inside its fixed profile. Current history and unrelated profile data stay intact. The tool reports the previous configuration's location; start Logonomic normally after success. A running profile owner blocks restoration. Restoring usage does not restore provider installations or sign-in; historical figures remain available even when the original source cannot resume on this host.

Usage storage problems

If a reset or restore reports a preservation error, keep the diagnostic and resolve the storage or permission problem before retrying. Use a verified copy from Saved usage history… to restore accepted figures.

Unreadable originals retained during reset occupy <launcher-storage-directory>/token_usage.reset-recovery-<UUID>/, beside active token_usage. With --user-data-dir, this is <user-data-dir>/config/token_usage.reset-recovery-<UUID>/. These folders hold raw evidence for investigation and are separate from verified restore points. A failed raw copy can leave an incomplete folder; its existence does not establish a successful backup. Leave these folders intact when asking support to investigate damaged history.