How Argoforge works

The right rule at the right moment

Instead of one long instructions file, each message gets only the rules that apply to it — fewer tokens, fewer forgotten instructions.

A clear task before the work

Before editing, Claude Code says what it thinks of the request and sizes the task. A medium or large one gets a card — the goal, the items with how to tell each is done — and a plan; a large one first gets three options to choose from, and a plan you approve.

A team picked for your project

Argoforge looks at your project’s stack and suggests agents, skills and MCP servers from public catalogs — rated, and checked for risky commands before install.

How the pick works →

Learns from mistakes

When a session goes wrong — refused permissions, repeated errors, a lost context — Argoforge suggests a rule. It applies only after you accept it — or, if you switch Mnemosyne to auto, after your own Claude decides on your Mac. Any decision can be undone.

Faster and cheaper over time

Ways to save tokens and time are tested on real work and measured; one that turns out harmful is stopped automatically, and only what proves useful is switched on for everyone.

Your setup stays yours

Your CLAUDE.md, rules, agents and skills are never edited. Argoforge only adds hints next to your message.

Stays on your Mac

• Your code and project files
• Project names and folder paths
• Session history with Claude Code
• The project description, its notes (START.md, the map) and the reasons for the picked team
• Your account key
• The text of Metis's options and which one you chose

Reaches the server

• The message text, cleaned — for one answer only, not stored
• A random project number instead of its name
• Numbers about the work: tokens, time, errors, the model's name — no text
• Dependency names as hashes — private names stay unreadable
• Findings and the picked team; evidence, facts about you and the pick's reasons are encrypted with a key only your app has
• For the check at the end of a turn — the cleaned beginning and end of the answer, not stored

The model runs on your side

Claude Code runs on your Mac under your subscription. The server never runs your requests.

Nothing about your project is kept

No message text, project names, paths or files on the server’s disk.

You decide

Suggested rules wait for your review unless you switch Mnemosyne to auto; every decision is listed and can be undone.

Statistics are anonymous

Shared numbers are shown only for groups of at least 5 users and with a little noise, so no one can be singled out.

Everything is visible

The app has a screen “What was sent to the server” with every request.

Off and out in one click

The switch in the menu turns Argoforge off from the next message. “Remove Argoforge…” takes away everything it installed.

Hints stay in your history

The text Argoforge adds to a message becomes part of your Claude Code session, like any other context.

Installed agents are ordinary files

Agents and skills go into your project’s .claude folder; most of them come from public repositories.