Softcap
EN+9
ENEnglishEnglish RUРусскийRussian ESEspañolSpanish FRFrançaisFrench ARالعربيةArabic BNবাংলাBengali HIहिन्दीHindi IDBahasa IndonesiaIndonesian PTPortuguês (Brasil)Portuguese (Brazil) ZH中文(简体)Chinese (Simplified)
Appearance
Overview/Support

Support

One person writes Softcap; the same person answers.

How to reach me

Write to lapster.me@gmail.com, or open an issue at github.com/milushov/softcap/issues.

Mail is read within a day or two; a fix depends on what broke. An issue with the failing account's provider, the app version and what you expected to happen is the fastest kind to act on.

What it requires

macOS 14 or later. The iPhone app needs iOS 17 or later. One provider account — Claude or Codex — signed in through the browser, or a CLI already signed in locally.

Opening the app the first time

Current builds are signed ad-hoc rather than with an Apple Developer ID, so macOS refuses the first launch. Right-click the app, choose Open, and confirm once — that is the whole ritual.

The terminal way, if you prefer it: xattr -dr com.apple.quarantine /Applications/Softcap.app

When something looks wrong

It asked for keychain permission when I pressed Refresh

Reading the CLI's own keychain item needs macOS's permission, and Softcap only asks while you are watching — when you press the button, never from a timer. Allow Always and it will not ask again; decline and the app keeps working from its own copies.

A Codex account shows a reading from hours ago

A local Codex account is read from the session files the CLI writes, so the number is as fresh as the CLI's last run — that is why every surface shows the snapshot's age. Sign that account in through Softcap's browser flow to see current usage independently of the CLI.

Notifications did not arrive

Check three things: macOS notification permission for Softcap, the thresholds in Settings (80% and 95% out of the box), and quiet hours — nothing arrives while they are on, and nothing is delivered late to make up for it.

Removing an account, and what it leaves behind

Remove the account in Settings: its credentials leave your keychain at that moment. The CLI it came from stays signed in — Softcap held its own copy, not the CLI's.

Turning off error reports and the update check

Both switches are in Settings. With them off, the only traffic the app makes is the usage requests to your own providers.

More

Product questions live on the FAQ page; the legal pages are short and honest. FAQ · Privacy · Terms

Overview FAQ What's new Claude limits Codex limits Support Privacy Terms

Softcap runs all day on the machine it was written on — and now on yours too. Release notes.

Not affiliated with Anthropic or OpenAI.

EN+9
ENEnglishEnglish RUРусскийRussian ESEspañolSpanish FRFrançaisFrench ARالعربيةArabic BNবাংলাBengali HIहिन्दीHindi IDBahasa IndonesiaIndonesian PTPortuguês (Brasil)Portuguese (Brazil) ZH中文(简体)Chinese (Simplified)