Quotum 0.10.2

Card settings

Remove the duplicate measurement scales from subscription-card settings. All selected scales remain visible on the card. Exact percentages, amounts and measurement dates remain in the values and status details. Historical read failures retain their retry action in the settings menu.

Updating

Update the hub first, restart updated background agents and reload dashboard tabs. Quit the desktop app before replacing its installation or whole portable folder. The database remains at layout 35; existing filters and layouts are retained. Back up the hub data and its separate credential-encryption key before updating.

Quotum 0.10.1

Dashboard layout fixes

• Show every selected subscription window and wallet allowance on its card, including Antigravity and OpenRouter. Shared resource filters control which scales are visible.
• Fit cards to their visible measurements and let chart legends wrap to their content. Remove the fixed blank areas and legend scrollbars introduced in 0.10.0.
• Restore compact, vertically aligned shared filters and right-align the last activity in grouped agent-session rows.
• Choose table or list layout from the displayed columns and fit automatic tables to their measured current-page rows, including short last pages.
• Preserve historical window order and wrap long scale names so their identifying endings remain visible.
• Keep exact allowance details and retry actions accessible when only wallet caps are selected.

Updating

The agent, hub and desktop app share version 0.10.1. Update the hub first, restart background agents after updating them, and reload open dashboard tabs. For desktop, quit the running app before replacing the installation or the whole portable folder.

This patch keeps the database layout used by 0.10.0. Before updating a self-hosted hub, stop it and back up its data and the separate credential-encryption key as described in SECURITY.md. Existing filters and saved layouts are retained; automatic widget heights follow their visible content.

Quotum 0.10.0

Quotum 0.10.0 adds local provider hooks and clearer control over chart series and project colours, with more resilient dashboard updates and activity capture.

What’s new

• Configure optional local programs to collect Claude, Codex or Antigravity measurements, including several accounts on one device. Independent success and failure observers can receive normalized outcomes from native or custom collection. Per-account scheduling, membership and delivery stay in Quotum. A collector can report no new data without inventing an observation or refreshing retained values. See the local hook contract for configuration and JSON examples. Hooks run trusted user code with the user's permissions; they are opt-in and are not sandboxed.
• Independently emphasize several series in chart legends with a click, keyboard or touch. Preview a series by pointing to it or focusing it. Emphasis changes presentation; shared filters continue to determine the data, Activity totals and bar values.
• Pin project colours per board in Manage projects. Activity charts, heatmaps and session tables use the same project colours, independently of project naming and layout settings.
• Keep widget and plot geometry stable through refresh, loading, errors and empty filter results. Preserve valid Activity data coherently during updates, retain historical navigation through rapid gestures, and improve date labels, monetary details and table row sizing.
• Recover activity capture automatically after temporary local storage failures, preserving the committed queue and delivery sequence. Unobserved gaps remain unknown; control-plane contact and quota collection continue independently.
• Preserve live history during calendar preparation and reserve the bounded access-check work required by history projection. Improve benchmark cancellation checks, native desktop smoke checks and retained failure evidence without treating unexplained browser startup or timing failures as repaired.

Updating

Stop the hub and back up its data before replacing it. Keep its encryption key backed up separately. Upgrade the hub before the agents, then reload open dashboard tabs. The database upgrades automatically from layout 33 to 35; rollback requires the old image and the pre-upgrade backup.

Measurements, agent-work history, boards, settings, encrypted connections and existing device-to-account associations are preserved. Project colours are optional board settings. Legend emphasis, shared data filters, table columns, widget visibility and provided-data permissions remain independent.

Existing 0.9 agents remain compatible. Custom collectors require the new hub's account-membership and collection-completion capabilities; upgrade the hub before enabling them. Native collection needs no new configuration. Run quotum update on each machine (or use its original installation method), then restart the agent with quotum stop and quotum start, or restart its service.

For the desktop app, choose Quit before installing the update. For the Windows portable package, replace the entire extracted folder; keep your existing profile and data. Desktop downloads remain available for Windows x64 and Linux x64. Updates are manual.

Quotum 0.9.0

Quotum 0.9.0 adds shared board filters and a closer view of recorded agent activity.

What’s new

• Filter resources, subscription windows, balances and key caps together across cards, charts and tables. Projects, devices and clients share the same filter row. Each reader explores their own selection; the owner can save the board’s opening defaults.
• Inspect recorded agent-hours in the new Activity heatmap, as a day-by-hour matrix or compact calendar. It follows the selected period and work filters, with interval navigation and distinct empty and unavailable states.
• Activity totals and bar values follow enabled legend series, including exact active time, recorded sessions and average concurrency. Hover or focus a legend entry to inspect its totals. Monetary legends show details and currency provenance in the same heading area.
• Use a consistent Nord Warm palette for project and device activity.
• Restore relative activity indicators and remove intrusive work-evidence warnings from subscription cards. Recorded work and attribution remain available in analytics.
• Fix historical quota charts losing their interior lines and hover values, and historical Codex funds falling back to credits despite a valid recorded currency conversion. Historical cards refresh their financial data when currency or sharing permissions change; archiving a display currency no longer closes an authorized board.

Updating

Stop the hub and back up its data before replacing it. Keep its encryption key backed up separately. Upgrade the hub before the agents, then reload open dashboard tabs. The database upgrades automatically from layout 32 to 33; rollback requires the old image and the pre-upgrade backup.

Measurements, agent-work history, boards, settings and encrypted connections are preserved. Saved resource selections move from the layout into the common data filters. Hidden cards stay hidden without excluding their data. Chart legend choices, table columns, widget visibility and provided-data permissions remain independent.

Existing 0.8 agents remain compatible. To update each agent, run quotum update (or use its original installation method), then restart it with quotum stop and quotum start, or restart its service.

For the desktop app, choose Quit before installing the update. For the Windows portable package, replace the entire extracted folder; keep your existing profile and data. Desktop downloads remain available for Windows x64 and Linux x64. Updates are manual.

Quotum 0.8.0

Quotum 0.8.0 brings client activity, resource assignments and measurement devices into one board workflow.

What’s new

• Track coding clients independently of subscription collectors, including native OpenCode CLI sessions and installed client versions. A client can contribute work without a known subscription.
• Link client work to a subscription or budget for a chosen device and period. Review suggested links, correct historical assignments and inspect why a resource was selected. Original machine observations stay intact.
• Manage measurement participation and preferred devices from My connections. Disabling measurements keeps the device’s activity and history; unavailable preferred devices fall back to automatic selection.
• Arrange cards and analytics in one grid with one viewing period. Five-hour and weekly quota charts and tables have independent placements, shared filters and consistent settings.
• Explore session analytics with grouping, sorting, pagination, active time and average concurrency. Device-session sharing is independent of subscription sharing, with funding identities redacted when they are not provided.
• Retain observed agent work through delayed delivery, interruption and restart. The updated agent captures bounded intervals and retries them without reassigning their recorded account evidence.
• Improve hub request cancellation, compressed history delivery and shutdown behavior.

Updating

Stop the hub and back up its data before replacing it. Keep its encryption key backed up separately. Upgrade the hub before the agents, then reload open dashboard tabs. The database upgrades automatically from layout 20 to 32; rollback requires the old image and the pre-upgrade backup.

Existing measurements, work history, boards, settings and encrypted connections are preserved. Saved layouts move into one grid. Shared boards initially include sessions from members’ saved devices; review Board settings → Provided data to change your devices’ participation. Resource sharing and private connection credentials remain separate.

Update each agent with quotum update (or its original installation method), then restart it with quotum stop and quotum start, or restart its service. Updated agents are needed for device measurement controls and captured-interval delivery. Older agents can continue delivering measurements, subject to the hub’s device controls.

For the desktop app, choose Quit before installing the update. For the Windows portable package, replace the entire extracted folder; keep your existing profile and data.

Desktop downloads remain available for Windows x64 and Linux x64. Updates are manual. Native OpenCode project attribution is available on Linux; macOS and Windows report presence without a project. CPU-based working states and spending per active hour are estimates, rather than provider reports of individual requests.

Quotum 0.7.0

Quotum 0.7.0 brings more providers and clearer money views alongside subscription limits.

Highlights

• DeepSeek balances and z.ai personal quotas. Connect a dedicated key from My connections. DeepSeek shows the available balance; supported z.ai Coding Plan accounts show five-hour and weekly quotas with their own history.
• Purchased Codex credits. See extra funds beside free resets on subscription cards and in the compact panel, with a separate balance-history widget. The initial estimate is USD 0.04 per credit; personal rates can replace it. Native credits, unlimited and unavailable readings remain distinct. Extra funds on shared boards need separate permission.
• Currencies and personal rates. Choose a display currency, define personal units and keep dated rate versions. Original amounts and recorded estimates stay intact when preferences change.
• Separate analytics. Subscription limits, wallet budgets and subscription extra funds have their own widgets and selections, sharing the time range with agent activity.
• Simpler board setup. Add widgets directly from the board, connect a source as part of adding it, and manage your profile, connections and application settings separately from board controls.
• More accurate work attribution. Shared client runtimes no longer credit work to an idle client's project without supporting evidence.

Updating

Stop the hub and back up its data and separate encryption-key storage before updating. Start the new hub with the existing storage: it migrates the database and saved analytics layouts automatically. Update the hub before agents, restart background agents or services after updating, and reload open dashboard tabs. Existing measurements, agent-work history and encrypted connections are preserved. A rollback needs the previous image and pre-upgrade backups.

Codex balances become available after an updated agent's next measurement. Sharing subscription limits does not automatically share its extra funds; grant that separately on each shared board.

For the desktop app, choose Quit before replacing it. Install the new package over the old one; for the Windows portable edition, replace the whole extracted folder. Data stays in your user profile. Automatic desktop updates and a macOS desktop package are not available yet.

The release includes CLI downloads for Linux, macOS and Windows, desktop packages for Linux and Windows, checksums and build provenance. The hub image and all six npm packages use version 0.7.0.

Full comparison: v0.6.0...v0.7.0

Quotum 0.6.0

Quotum 0.6.0 adds OpenRouter balances and API-key limits, groups running agents by project, and makes chart navigation continuous with smaller history reads.

OpenRouter and connections

• Connect a dedicated OpenRouter management key in My connections, alongside your devices. The hub validates and encrypts it before saving; keys cannot be read back through the dashboard or API.
• Budget cards show the account balance and enabled API-key limit scales with their reset times. Card settings select keys and paginate larger inventories.
• Select USD in analytics for balances, spending and key limits. Top-ups remain separate from spending, and missing or uncertain history is kept distinct from zero.
• Expired or revoked access preserves the last measurements. Access details are private to their owner; board members see the shared measurements and a neutral unavailable state.
• The compact desktop panel displays budgets too. Percentage forecasts, tray quota colours and quota notifications continue to use subscription windows only.

Server hubs need a separate encryption key to enable trusted connections. Back it up separately from the database. The desktop app uses the system password store when available, with a protected-file fallback as described in SECURITY.md. The machine agent still asks installed coding clients for limits and never receives provider keys.

Dashboard

• The running-agents widget groups by project, machine or subscription, with working-agent counts, agent-hours and last activity. Open a group for its individual agents and machines.
• Horizontal touchpad scrolling, Shift-wheel and Shift-drag move both charts continuously through time. Plain dragging selects a time range; the arrow buttons retain half-period navigation.
• Panning keeps known chart data visible, reads missing history ahead within bounded limits, and updates totals when the range settles. Returning to cached periods reuses their history.
• Device and provider-account setup live together in My connections. Account settings hold profile and app preferences; display choices stay in each widget's settings.

Upgrading from 0.5

Stop the hub and back up its data directory before replacing it. Database migrations preserve subscription measurements, agent-work history, boards and settings. Older agents continue to deliver measurements; update the hub first, then run quotum update and restart background agents or their services. Reload open dashboard tabs.

Existing subscription measuring needs no new configuration. To connect OpenRouter on a server hub, configure QUOTUM_SECRET_KEY or QUOTUM_SECRET_KEY_FILE outside its data directory; see deploy/README.md. Preserve matching encryption keys separately when making or restoring backups. An older hub cannot open the upgraded database, so rollback needs the pre-upgrade backup.

For the desktop app, quit the old app before installing the new package. Windows portable users replace the whole extracted folder; data stays in the user profile. Updates remain manual, Windows packages are not code-signed yet, and macOS is supported by the CLI only.

See the README for installation, configuration and package verification.

Quotum 0.5.0

Quotum 0.5.0 adds limits and notifications to the desktop tray, gives boards a two-dimensional layout, and keeps analytics up to date with smaller history reads.

Desktop

• A tray icon coloured by the tightest visible limit, with a separate mark for stale or unavailable measurements.
• A compact panel of limits, reset times and working agents: click the tray icon on Windows, or choose Limits from the Linux tray menu.
• Configurable native notifications for low and critical quota, confirmed window resets and newly announced scheduled resets. Hidden limits are excluded; starting, waking and reconnecting do not replay missed events.
• More reliable compact-panel and main-window handoffs, close/reopen behaviour and a responsive loader while the browser starts.

Windows and Linux packages remain available in the same formats. Desktop updates are manual; Windows packages are not code-signed yet. macOS is supported by the CLI, with no desktop app yet.

Dashboard and measuring

• Place widgets on a six-column grid and resize their width and height. Charts grow with their widgets, and shorter agent lists open their complete list on demand.
• Refresh a card's limits or all visible cards on demand, within the device's measuring interval and error pauses.
• Choose Auto or a measuring frequency of 1, 2, 5 or 15 minutes per subscription, shared across its boards. A device's own interval remains its minimum.
• Weekly forecasts follow the hours and days when each subscription usually spends, with a marker for a recent burst. Spending and forecasts distinguish active time from agent-hours; four parallel agents over one hour make four agent-hours.
• Analytics keep the history already read, fetch only missing or changed cells and update agent activity when work is reported. Cached periods and frames can be revisited without rereading their whole history.
• Floating panels and tooltips stay inside the window. Codex updater and proxy processes no longer appear as coding-agent sessions.

Contributors can use isolated worktree development stands and the shared component check commands documented in CONTRIBUTING.md.

Upgrading from 0.4

Stop the hub and back up its data directory before replacing it. Database migrations preserve subscription measurements, agent-work history, boards and settings. Saved board layouts are converted to the widget grid when opened. An older hub cannot open the upgraded database; rollback needs the pre-upgrade backup.

Update the hub first, then run quotum update and restart background agents or their services. Older agents continue to deliver measurements. Reload open dashboard tabs so the page and hub use the same history contract.

For the desktop app, quit the old app before installing the new package. Windows portable users replace the whole extracted folder; data stays in the user profile. Notifications are on by default and can be changed in the app's settings.

See the README for installation, configuration and package verification.

Quotum 0.4.0

Quotum 0.4.0 brings the desktop app to Windows and Linux and adds a clearer picture of how coding agents spend your subscriptions.

Desktop app

Download a Windows installer or portable ZIP, or a Linux x64 deb, rpm or AppImage. The app runs the machine's agent and its own hub, shows the dashboard in a window, and keeps measuring from the tray when the window closes. No server or Quotum account is needed. It supports start at login and shares settings with the CLI.

Packages are built and smoke-tested on Windows and Linux, with SHA256SUMS and build provenance alongside the CLI downloads. Updates are manual; Windows packages are not code-signed yet. macOS is supported by the CLI, but has no desktop app yet.

Dashboard and measuring

• Agent-work history by subscription, project and machine, with project names you can correct in My machines.
• Activity charts, spending per hour of agent work, and forecasts of how many work hours remain.
• Forecasts based on each limit window's own pace, drawn beside the spending plan, with labels for limits projected to run out beyond the visible chart.
• Shared analytics periods from one hour to 30 days, zooming and navigation through history.
• Live dashboard updates from hub events, with long polling when a proxy holds back the stream; widgets update only when their data changes.
• The hub sets the measuring pace, and the card explains when the next measurement is due. Reset announcements and free resets live in the card's tray.
• Configurable reset-tracker endpoints, a reproducible demo board, and fixes to desktop window reopening and unauthenticated agent requests.

Upgrading from 0.3

Stop the hub and back up its data before replacing it. The database migrates automatically. Subscription measurements, boards and settings remain; the old totals of agent work are replaced by per-session history, so work analytics start at the upgrade. Earlier limit history stays on the chart. An older hub cannot open the upgraded database: a rollback needs the pre-upgrade backup.

Update the hub first, then run quotum update and restart background agents or their services. Older agents continue to deliver measurements to the new hub. For a desktop development build, quit the old app before installing the release; portable Windows users replace the whole extracted folder.

See the README for installation, configuration and package verification.

Quotum 0.3.0

Which coding agents are running on your machines, and which of them are working, on the
cards of the subscriptions they spend; a time range selected on the chart; and the agent
installed without Node.js.

Get it

• Hub: docker run -d -p 8080:8080 -v quotum:/data ghcr.io/padurets/quotum-hub:0.3.0
  (linux/amd64 and arm64), then docker logs for the setup code of the first account.
  deploy/compose.yaml
  runs it behind Caddy with HTTPS.
• Agent: curl -fsSL https://github.com/padurets/quotum/releases/latest/download/install.sh | sh
  on Linux and macOS, irm https://github.com/padurets/quotum/releases/latest/download/install.ps1 | iex
  on Windows, or npx quotum (Node.js 18+). The binaries below come with SHA256SUMS
  and build provenance (gh attestation verify <file> -R padurets/quotum).
• Connect a machine: quotum connect https://your-hub and quotum start.

Upgrading from 0.2

• Upgrade the hub first. It adds a table to its database on start; a 0.2 hub does not
  open that database again, so keep a copy of the volume if you may need to go back.
• Agents 0.2 keep working with a 0.3 hub; they just don't report running agents. A 0.3
  agent with a 0.2 hub measures as before and asks again every hour whether the hub
  takes its list of running agents, so nothing needs restarting after the hub's upgrade.
• quotum update replaces an installed agent with the latest release; one installed
  through npm is updated through npm.

What's in it

Which agents run, and which of them work. The agent looks at the machine's process
list every 15 seconds: which Claude Code, Codex and Antigravity clients run, since when,
in which project folder (its name only), in a terminal, an editor or a desktop app, and
whether they are working, judged by the CPU time of the client and what it started. No
client configuration, no hooks, no session files, no tokens, and a look costs a few
milliseconds.

• Each card shows how many agents work on its subscription, by machine, in a tray along
  its bottom; its panel names them.
• A table widget lists every running agent of the board, with the columns you choose.
  It is off until the board's owner turns it on.
• The hub keeps how long agents worked on each subscription, for the analytics to come.
• Board members see these agents, their project folders and the names of their
  machines, as they see the subscription's limits. sessions = false in the agent's
  settings turns the reports off, projects = false leaves out the folder names.

A time range on the chart. Drag across the chart (on a phone, hold, then drag) to
select from 15 minutes to a month: the chart zooms to it, and the table shows what each
window had at its start and end, what it spent and at what pace. The range lives in the
page's address, so a link to a burst of work can be shared, and Back undoes it.

Now and analytics. The cards, which are about now, come first; the chart and the
table below them share one set of filters: the kind of window and the period.

The agent without Node.js. Installers for curl … | sh and PowerShell check the
checksum and put quotum in ~/.local/bin; quotum update is one small request when
there is nothing new. Release archives are now named quotum-cli-<version>-<platform>.

The board.

• A card can have its own colour, and its spending plan can be switched off.
• A card's dot shows how fresh its numbers are; it turns amber only on trouble.
• The chart's tooltip reads the plan beside what is left, an announced reset is labelled
  on the chart, and a reset that happened is mentioned on the card for a day.
• The widgets menu groups the cards, the overviews and the analytics.
• A warmer look: softer colours, frosted cards, glass menus, dialogs and tooltips.

Written down. The spec
has a new section, Reporting running agents, and says in its Privacy section what
the reports carry. About 180 tests cover the rules, permissions, sharing, the clients'
answers and the process lists of Linux, macOS and Windows.