Update Grace instructions

To refresh the Grace instructions in your project, ask your agent:

Update Grace.

This request authorizes an update of the Grace kit: its procedures, instruction block and official review profiles. The agent checks the proposed version, backs up affected files, then applies the update without asking for a second confirmation in the conversation. This operation changes neither the project’s talents nor your connection to Grace.

Does your older grace-update skill still require manual application or refuse the update because of a missing native capability? Follow Migrate an older installation.

Understand the check at the start of a conversationCopy Anchor Link

At the start of each new conversation, the agent retrieves the official list of kit files, called the manifest, through grace_check_installation. It then reads the grace-update procedure contained in that manifest, even if an older version already exists locally. It compares files locally without sending their content to Grace.

This check follows the agent’s instructions: no background service, hook or program triggers it. An older conversation may need the explicit request described below.

If files differ or are missing, the agent shows the differences and offers:

• Update: apply the current version, after backups, for this operation.
• Later: continue working without changes or another automatic reminder in this conversation.

You can subsequently ask Update Grace to check and apply again, including after Later. If everything is current, the agent reports that without rewriting files. No automatic-update activation is needed or created. An old activation setting stays intact and is no longer used. The Auto review level is independent.

Find the kit before choosingCopy Anchor Link

The agent first inspects compatible destinations individually: instructions, each of the four skills, then native profiles separately. An older file remains present, needs an update; a procedure absent from the menu may still exist on disk. Client loading conditions and actual invocation require separate checks.

An unambiguous existing location is kept. For missing items or divergent copies, the agent shows paths before requesting a choice for that item only. Identical copies are all updated after update approval, within the backed-up local plan. It creates no compatibility file, symlink or permanent preference and moves no other files. Antigravity’s .agent/skills remains compatible alongside .agents/skills; Codex’s .codex/agents profiles do not replace .agents/skills.

Connect a project documents compatible choices and script options. The web guide presents choices without claiming to have inspected your disk. A frozen pentest campaign remains excluded from this check.

What the agent checks before replacing filesCopy Anchor Link

The agent checks destinations and their parent directories, links and Grace block boundaries. It backs up every file to be changed in full before the first replacement, including text outside the block. It rereads those backups, then each file immediately before and after editing it.

Installed content must match the official version exactly, without altering its line endings or characters. The agent checks the size and fingerprint of every kit file and the Grace block. These checks detect concurrent changes; they do not guarantee that another tool cannot intervene between two checks.

Ordinary reading, editing and terminal tools are sufficient within your client’s permissions. Its write denials and approval requests still apply. In Plan or read-only mode, the agent can compare but changes nothing, including backups. A known ongoing review defers application; the agent does not search other sessions. A frozen pentest campaign keeps its instructions without remote checks or downloads.

Verify the resultCopy Anchor Link

The agent reports a verified update only after rereading the complete kit and comparing it with the manifest. It identifies changed files and backup locations, then rereads the new instructions before continuing. A partial write remains an interruption even if some files are already current.

Files being present, discovered in your AI client’s menu and a skill being invoked are three separate checks. Refresh the menu or start a new conversation if your client requires it, then verify that grace-update and grace-effort appear. Codex uses $grace-effort; a client supporting slash commands may offer /grace-effort. In T3, use the selector or the active provider’s syntax. Updating the kit does not prove that invocation succeeded.

Migrate an older installationCopy Anchor Link

An older installation may keep reading its outdated local procedure. Explicitly ask the agent to fetch the current manifest and read its procedure before acting:

Update Grace. Call grace_check_installation for my agent and the English language, then read the entire grace-update skill from the returned manifest, even if it already exists locally. Apply that procedure after fully backing up the files to replace.

If the MCP connection or this tool is unavailable, use this bootstrap request for Codex:

Update Grace from the official public manifest for Codex. Retrieve and validate that manifest, then read its entire grace-update skill. Follow that procedure to back up and replace the local kit. This request authorizes application, including customized or unrecognized kit content.

For another agent, replace harness=codex in the link with harness=claude, harness=cursor, harness=vscode, harness=copilot, harness=copilot-cli, harness=windsurf, harness=mistral, harness=gemini or harness=agents, depending on your tool. In T3, choose the active provider. The agent uses this public address without passwords, cookies or API keys. If the manifest is unreachable, invalid or still provides the old procedure, it explains the limitation; it does not report a successful migration.

Recover from a problemCopy Anchor Link

To change your review preference, see Choose the review level.

Troubleshooting: older manual scriptsCopy Anchor Link

harness=codex
kit_dir=$(mktemp -d)
kit_script=''
if curl --fail --silent --show-error 'https://grace.hoppr.tech/setup.sh?locale=en' -o "$kit_dir/setup.sh" && grep -Fq -- '--update-kit' "$kit_dir/setup.sh"; then
  kit_script="$kit_dir/setup.sh"
  printf 'Script ready.\n'
else
  printf 'Check unavailable. Stop here; do not run ordinary setup.\n'
fi

sh "$kit_script" --update-kit --harness "$harness" --check
sh "$kit_script" --update-kit --harness "$harness" --dry-run

printf 'planDigest of the accepted preview: '
IFS= read -r plan_digest
sh "$kit_script" --update-kit --harness "$harness" --apply --expect-plan "$plan_digest"
sh "$kit_script" --update-kit --harness "$harness" --check

$Harness = 'codex'
$KitScript = $null
$KitDirectory = Join-Path ([IO.Path]::GetTempPath()) ('grace-kit-' + [Guid]::NewGuid().ToString('N'))
New-Item -ItemType Directory -Path $KitDirectory | Out-Null
$DownloadedScript = Join-Path $KitDirectory 'setup.ps1'
Invoke-WebRequest -UseBasicParsing 'https://grace.hoppr.tech/setup.ps1?locale=en' -OutFile $DownloadedScript -ErrorAction Stop
if (-not ([IO.File]::ReadAllText($DownloadedScript)).Contains('-UpdateKit')) {
  throw 'Check unavailable. Stop here; do not run ordinary setup.'
}
$KitScript = $DownloadedScript
& $KitScript -UpdateKit -Harness $Harness -Check
& $KitScript -UpdateKit -Harness $Harness -DryRun

$PlanDigest = Read-Host "planDigest of the accepted preview"
& $KitScript -UpdateKit -Harness $Harness -Apply -ExpectPlan $PlanDigest
& $KitScript -UpdateKit -Harness $Harness -Check

printf 'Transaction identifier: '
IFS= read -r transaction
sh "$kit_script" --update-kit --harness "$harness" --recover "$transaction"

printf 'planDigest of the accepted recovery: '
IFS= read -r plan_digest
sh "$kit_script" --update-kit --harness "$harness" --recover "$transaction" --apply --expect-plan "$plan_digest"
sh "$kit_script" --update-kit --harness "$harness" --check

$Transaction = Read-Host "Transaction identifier"
& $KitScript -UpdateKit -Harness $Harness -Recover $Transaction

$PlanDigest = Read-Host "planDigest of the accepted recovery"
& $KitScript -UpdateKit -Harness $Harness -Recover $Transaction -Apply -ExpectPlan $PlanDigest
& $KitScript -UpdateKit -Harness $Harness -Check

Local review and paged readsCopy Anchor Link

See the local review workflow for prerequisites, complete reads, retries and evidence limits.