First month free · then $19.99 a month · No VAT (§ 19 UStG) First month free · then $19.99 a month

See pricing
How to use Grace

Install once. Then work as usual.

Grace is a plugin for Claude Code on your Mac or Windows PC. You keep working the way you do: type your task, and Grace takes over new projects and changes to your code. There is no command to learn.

Installs into
Claude Code on a Mac or Windows PC, as grace@grace
You type
your task, as usual — no command
Your plugins and Claude’s tools
none switched off

Install once

One command in Terminal installs the Grace plugin for Claude Code and, if it is missing, Node.js. On Windows, use the command for PowerShell. Claude Code must already be installed. Before it installs anything, it checks your computer, signs it in with a device code and checks your subscription.

in Terminalin PowerShell

$ /bin/bash -c "$(curl -fsSL https://parsimic.com/install.sh)"
$ irm https://parsimic.com/install.ps1 | iex

It asks before each install, and it stops before downloading anything if the account has no active subscription or free month. Read the script firstRead the script first

Run the command in the Terminal app, not in the Claude chat. Restart Claude Code afterwards.Run the command in PowerShell, not in the Claude chat. Restart Claude Code afterwards.

If Node.js is already on your computer: usually under 2 minutes (our estimate). If the installer adds Node.js, that download comes on top. Updates: under 1 minute.

  1. Subscribe or try it free

    Grace is delivered only to accounts with an active subscription or a free month — your first month is free, without payment details.

    See the plans

  2. Run one command

    Paste the command above into the Terminal app (Applications → Utilities) — not into the Claude chat — and press Return.

  3. Confirm the code

    The installer shows a code and opens parsimic.com/geraet — confirm it with your Grace account. It then installs the plugin and, if it is missing, Node.js.

    parsimic.com/geraet

  4. Build something

    Restart Claude Code and run /grace:grace-einrichten once. Then just type your task — Grace builds new projects on its own.

    in Claude Code › <task>

Every step of the installer, and what to do if something stops

Type your task as usual

There is no command to start Grace. Open Claude Code in a project or in your projects folder and type what you want, the way you would without Grace. Grace works with your Claude sign-in and the model you chose in Claude Code.

  • Questions, explanations and reviews go to Claude as usual.
  • Messages that start with / are commands — Grace leaves them alone.
  • You stay in Claude Code the whole time; there is no separate app or window.

New projects, changes, and “without Grace”

Grace sees by itself what kind of task it is.

  1. new project

    Grace builds it in your projects folder — the one you named during installation, where your other projects are — as a project of its own, next to them. In an empty folder it builds right where you are. It says so in one sentence first. When it is done, you get a short report: what was built and, if the project has tests, whether they passed.

  2. existing project

    Open Claude Code in the project and describe the change. Claude works as usual, and Grace carries out the changes to your files — in Claude Code you usually see Grace’s tool grace_aendern instead of Edit.

  3. without Grace

    Write “without Grace” in your task, and Claude builds it alone, as if Grace were not installed.

Your projects folder

During installation, Grace asks where your Claude projects are. That is how it tells a new project from work on an existing one — and that is where new projects go, next to your other projects.

  • For each project there, Grace notes the name, a short description (from the README, package.json or pyproject.toml) and the language. It never reads .env files, keys or code for this.
  • The list stays on your computer. It is not sent to us.
  • Skipped it, moved your projects, or want another folder? Run /grace:grace-einrichten in Claude Code.

What you see

Grace keeps Claude Code as it is. Two small additions, in German — that is how Grace reports.

Grace aktiv
Grace is active. An optional status line under Claude Code’s input box — setup offers it, and it is only installed if you say yes. An existing status line stays and is shown above it.
Grace denkt … · 3 Min. (example)
Grace is building. A dim line under Grace’s entry in Claude Code, with what it is doing and the minutes so far. Claude Code’s own spinner stays as it is. The dotted edge marks an example value.

Before it changes your status line, setup keeps a copy of ~/.claude/settings.json as settings.json.vor-grace.

Your plugins, MCP servers and skills

Grace works alongside them and switches none of them off.

Your plugins, MCP servers and skills — and all of Claude Code’s own tools — keep working in your Claude Code session exactly as before. Grace does not uninstall or disable anything.

  • New projects Grace builds use your Claude sign-in and your project’s rules (CLAUDE.md, or else AGENTS.md). Your other plugins, MCP servers, skills and hooks are not used for that build.
  • Hooks on Edit and Write — formatters, security warnings and the like — do not run on changes Grace makes; run your project’s formatter after Grace’s changes. Your deny rules for Read, Edit and Write (permissions.deny in your, the project and the local settings) apply to Grace too: it does not read or change files they block. Grace itself also never touches .env files, keys and credentials, .git, .claude or Git hooks. /grace:grace-einrichten names the hooks and rules this affects.
  • Measured with plugins installed: our test compared Grace with Claude Code that already used two token-saving plugins, caveman and context-mode. A saving against that is a saving on top of what careful users already do.

From each project’s own documentation, checked 29 September 2026 — not measured by us unless stated.

Turn these off in projects where you use Grace

They bring their own file-editing tools and compete with Grace.

Morph
Fast Apply MCP, its own edit_file
Relace
apply MCP
Serena
symbol-editing tools
trueline-mcp
blocks Claude’s Edit and reroutes it
Hashline-style edit plugins
Desktop Commander
its own edit_block

Note: “headroom wrap claude” installs Serena along with Headroom.

Work alongside Grace, add little on top

caveman, context-mode
Measured together with Grace on a few tasks: allowed, little extra saving.
rtk (Rust Token Killer)
claude-mem
Claude Context (zilliz)
Headroom
without Serena

Everything else works normally

Skills, LSP servers, GitHub, Stripe or browser MCPs and the like.

Grace checks this for you: at setup and at every session start it scans installed plugins and MCP servers and tells you if one competes — it never uninstalls anything. Run /grace:grace-plugins any time.

What it does for your limit

From our test of October 2 – 3, 2026 on Claude Max 20x — the same 60 tasks, with Grace 0.3.8 and without:

≈ −49 % of the 5-hour limit for the same 60 tasks.

Read from the limit in whole percentage points, two measurements added up: 32 % with Grace 0.3.8, 63 % with Claude Code + caveman + context-mode · 60 tasks, Claude Max 20x on both sides · October 2 – 3, 2026: 30 tasks at the same time on two accounts, 30 with the comparison run measured separately on the same day · on the comparison account 54 s of readings are missing at a 5-hour reset, which can only make the saving look smaller

Measured against Claude Code with two token-saving plugins already installed: caveman and context-mode.

Quality on the 58 tasks both runs finished: 92.5 % with Grace vs 91.9 % Claude alone.

These are averages from our test, not a promise for every task: depending on the task, the saving and the quality come out higher or lower.

Every number, with the method and the raw data per task

What leaves your computer

  • To us: no code, no project content, no prompts. Grace’s only connection to parsimic.com is your subscription — sign-in with a device code at parsimic.com/geraet, then at most one check a day with a device token. After a successful check, Grace works offline for 7 days.
  • To Anthropic: Claude Code sends Claude what it needs for your task — also for tasks Grace takes over, through your own Claude sign-in, as it does without Grace.
  • One subscription covers up to 2 computers. Without an active subscription, Grace’s tools switch off and Claude works as normal.

Privacy policy

Requirements

Mac
Apple silicon, M1 or newer
Windows
Windows 10 (version 1809 or newer) or 11, 64-bit
Claude Code
with your own Claude Pro or Max plan — or the Claude API on the API plan
Node.js
22.13+, 23.4+ or 24+ — the installer adds it with Homebrew if it is missing; with nvm, Volta, fnm, asdf or mise it shows the command instead
Internet
for installing, signing in a computer, updates and the subscription check

At every session start Grace checks Node.js and your installed plugins, and tells you once if something needs attention.

Commands

There is no command to start Grace. These three are for setup:

/grace:grace-einrichtensetup
Checks the setup and installs what is missing after asking (Node.js), sets your projects folder, and offers the status line.
/grace:grace-anmeldensign-in
Connects this computer to your Grace account with a device code at parsimic.com/geraet. The installer does this for you.
/grace:grace-pluginscheck
Lists plugins that compete with Grace and names the command to turn each off — it never runs it itself. Also names hooks that do not run on Grace’s changes and the deny rules Grace follows.

Good to know

  • Mac with Apple silicon, or Windows 10 or 11 (64-bit). Windows support is new.
  • Grace speaks German: the status line and its reports.
  • Small tasks were not slower with Grace: in the test at the same time with Grace 0.3.8 (October 3, 2026), the 6 easy tasks took 10 min with Grace and 20 min without.
  • Quality: 92.5 % with Grace 0.3.8 vs 91.9 % Claude alone, over the 58 tasks both runs finished. Weakest on mixed tasks: 85 % vs 86 %.
  • Grace does not switch off Claude’s tools and does not uninstall plugins. When it builds a new project, it installs that project’s dependencies (npm or pip packages) inside the project folder; beyond that, it installs nothing without your consent.

Quality level by level, and the raw data per task, on the measurements page

Try 30 days free Just create an account · no payment details · ends on its own

Continue on your computer

Grace runs on your Mac or Windows PC. Copy the link and send it to yourself — by email, a note or a message — then open it there.