Argoforgebeta
Argoforgebeta
Argus notices when a session keeps going wrong: the same action refused again, many tool errors, one command failing over and over, you correcting Claude, very heavy or compressed sessions. Your own Claude explains what happened and proposes a rule. You decide on Mnemosyne's page.
Step by step
Your Mac counts, your Claude explains, the server collects.
It reads the last 8 prompts of the session record on disk and counts five kinds of trouble. Only numbers and hashes leave, never text.
If the score reaches 3 and the limits allow, the server sends a one-time task. Your correction counts double: “no”, “not that”, “still broken”, “revert” at the start of a reply, in Russian or English. A long session counts 2 for a turn over 120,000 fresh tokens (cache re-reads not counted) and 2 for a compacted context, each at most once per session a day; a long session alone starts an analysis only when both happened, and at most once a day.
With no tools, it reads the task and a cleaned excerpt of the same last 8 prompts, headed by the signals that fired, then proposes a rule — or none if the signals were harmless.
Claude's short account of what happened, and any fact about you it noticed, are encrypted with your key from the Keychain. The excerpt itself never leaves.
A finding with the same calls or a similar rule absorbs it. ×N is the number of sessions it was seen in: the same session never adds to it. If its rule was accepted, it is marked “recurred”; if postponed, it opens again. Your corrections, very long sessions and many tool errors are signed by the project only, so they join a finding with the same rule title, never just by project.
Your data
Your own Claude, on your Mac: no tools, a 2-minute limit and a $0.20 budget per analysis. The server picks the model (Sonnet by default). Argus runs no model on the server.
Rules
At most 3 analyses a day per Mac and 10 per account — the server enforces both, by your Mac's day — one at a time. A long session alone gets 1 of them a day. An analysis your Claude could not run gives its place back; after three such failures in a day, analyses wait until tomorrow.
Once you accept a rule, the same trouble (the same calls) is not analysed again for 7 days; the calls of a finding you rejected are not analysed again. If they come back, the finding records the session without a new analysis — an accepted one is marked “recurred”. Corrections, long sessions and tool errors are signed by the whole project, so a rejection there mutes them for 30 days, not for good, and their return does not mark a rule “recurred”.
A refusal or error counts only when the same call repeats. Tool errors count when over 25% of at least 12 calls fail.
Once per turn, Claude's answer goes back if it cites a file and line the disk does not confirm (or a name that is not on that line), says a check passed when none ran or quotes a number no check printed, or says “not found” after one look. The check runs on your Mac; the server gets only which kinds fired, as counts.
Clearing findings shows the exact list and waits for your confirmation. Only open findings are cleared: postponed and rejected ones and accepted rules stay.
How to use
Argus finds problems; on Mnemosyne's page you accept, postpone or reject them.
Read the evidence and fix the rule.
To read it on another Mac, export the encryption key in Settings.