Skip to help content

Homer support

Homer Help

Choose what you are trying to do. Start with the guided setup, understand a Homer result, or work through the most common fixes without needing to decode internal system language.

Continue guided setup Email Homer support

Get Homer installed

The guided setup is the quickest route. Open it on the same Windows or macOS machine where Cursor, Claude Code, or Codex runs. Setup ends with a controlled 60-second guided activation review, not an ordinary first check.

  1. Create your account and verify your email.
  2. Copy and run the install command for your computer.
  3. Close and restart your coding agent after the command finishes, then start a new agent task.
  4. Copy the guided activation prompt from setup into that new task. The first Homer result is expected to pause and name one checklist improvement.
  5. Let the agent make that edit, then retry Homer in the same agent task with the retry_scope_id from the first result. A different task cannot complete the review.
  6. Wait for setup to show Homer as activated.

Timing and usage: the guided review expires 24 hours after its install command is created. If it expires, return to setup and create a new install command. Guided-review calls are activation checks, so they do not appear as ordinary usage on the Account page.

Review the hook for your agent

Codex

After restarting Codex, open /hooks. Find the Homer PreToolUse hook, inspect its current command and definition, and approve that exact definition if Codex prompts you. Codex records trust for the definition's current hash; if the definition changes, Codex can require another review.

hook context not observed means only that Homer's Codex PreToolUse hook did not run for that check. It does not prove the hook is unapproved. The hook may be disabled, its definition may have changed, or the task may predate the current install. Review /hooks, then start a new task and retry. If the Homer hook is absent, rerun the installer first.

Cursor

Restart or reload Cursor. If Cursor asks to review Homer hooks, inspect and trust the Homer PreToolUse hook; it attaches the current Cursor transcript path to Homer checks. If Homer still cannot see the full Cursor session, confirm Cursor transcripts are enabled, restart or reload, and retry in the same workspace.

Claude Code

Restart Claude Code. If it asks to review Homer hooks, inspect and trust the Homer PreToolUse hook; it attaches the current Claude transcript path, session ID, and working directory to Homer checks. Start the guided review in the restarted session.

Start guided setup Open advanced setup
Back to topics

Understand a Homer result

Homer checks whether the work and visible evidence support what your agent is about to claim. CL is completion confidence for that specific claim. It is not a code-quality score, a bug-free guarantee, or an improvement percentage.

Cleared

Homer check: cleared completion (CL=0.97).
How to read it

Homer has high confidence that the evidence supports the stated completion claim. It does not rate the underlying code 95/100.

What to do

The agent can finish with this receipt, while keeping its claims no broader than the evidence.

Another pass needed

Homer paused completion (CL=0.57).
How to read it

The current work or evidence is not strong enough to support “done.” The reason and blocker identify the gap.

What to do

Address that gap, gather direct evidence, and retry in the same task with the returned retry_scope_id.

Retry limit reached

Homer check: retry cap reached; not confidently cleared (CL=0.40).
How to read it

The allowed retry count has ended. Reaching the retry cap is not a successful clearance.

What to do

The agent must disclose what remains unresolved and must not describe the work as Homer-cleared.

Show the technical receipt fields
  • CL is Homer's confidence that the current completion claim is supported by the available work and evidence.
  • decision=block, should_continue=true, or may_finish=false all mean the agent should keep working.
  • Advice, planning, review, brainstorming, and status-only answers do not normally need a Homer check.
Back to topics

Homer didn't run

Start with the symptom that matches what you can see. The first recovery path solves most missing-receipt cases.

I finished a task but saw no Homer result
  1. Return to guided setup and check the activation status. Do not use ordinary Account usage to diagnose the guided review; demo calls are intentionally excluded there.
  2. If more than 24 hours have passed since the install command was created, create a new install command.
  3. Restart your coding agent, follow the agent-specific hook review above, and open a new task.
  4. Paste the guided activation prompt. After the expected pause, keep working in that same task and retry with the returned retry_scope_id.
My agent says Homer is unavailable

Some Codex sessions defer tools until they are searched for. Ask Codex to search for or discover homer_check before deciding that Homer is unavailable. For Cursor or Claude Code, restart the agent and confirm the install command completed without an error.

Homer keeps asking for another pass

Read the reason in the Homer result, do the missing work, and collect direct evidence such as a test result, file check, browser check, or deployment response. Repeating the same request without new work will not make the evidence stronger.

The installer or update failed
  1. Run the command on the same computer as your coding agent.
  2. Open a fresh PowerShell or Terminal window and try the command once more.
  3. If it still fails, copy the complete error and send it to support with your operating system and agent name.

Still stuck?

Email hello@homer.tech with the error text, your operating system, and whether you use Cursor, Claude Code, or Codex. We reply fast.

Back to topics

Change Homer's settings

The Done page offers copyable prompts for changing Homer. If you prefer to edit the local configuration directly, use ~/.homer.env.

Recommended configuration 
HOMER_ENABLED=1
HOMER_THRESHOLD=0.97
HOMER_MAX_RETRIES=3
HOMER_AUTO_UPDATE=1
  • Turn Homer on or off: set HOMER_ENABLED to 1 or 0.
  • Change strictness: a higher HOMER_THRESHOLD asks for stronger evidence before clearing.
  • Limit follow-up passes: HOMER_MAX_RETRIES controls how many attempts the agent can make.
  • Control updates: set HOMER_AUTO_UPDATE=0 only if you need to update Homer manually.
Open my configuration prompts
Back to topics

Credits and charges

You do not need a card to start. Completing the guided activation review unlocks the $10 starter credit. The guided-review calls are free activation checks and do not appear as ordinary usage; creating an install command or checking the installer key does not unlock credit.

  • Your balance and recent usage are shown on the Account page.
  • Homer warns you when your balance is getting low.
  • You can add credit or find your referral link from Account.
Open balance and usage
Back to topics

Update Homer

Recent Homer clients update automatically when a new version is available. The new version takes effect after you restart the agent or open a new agent session.

I installed Homer before automatic updates existed

Older clients may need one manual reinstall before automatic updates become available. Open your install page, copy the current reinstall command, run it, and restart your agent.

Turn automatic updates off

Set HOMER_AUTO_UPDATE=0 in ~/.homer.env. You will then be responsible for installing future client fixes yourself.

Get my reinstall command
Back to topics

Reinstall or remove Homer

Reinstall Homer

Your reinstall command contains your account-specific install details. Open the install page on the computer you want to update, then copy its Reinstall command.

Get my reinstall command

Remove Homer from this computer

Choose your operating system and copy the command. Homer backs up any configuration it changes under ~/.homer-uninstall-backups.

Windows PowerShell 
powershell -NoProfile -ExecutionPolicy Bypass -Command "irm 'https://app.homer.tech/uninstall.ps1?run=1' | iex"
macOS Terminal 
curl -fsSL 'https://app.homer.tech/uninstall.sh?run=1' | sh

Add purge=1 to the script URL only if you also want to delete Homer's downloaded client and local state under ~/.homer.

Back to topics

Privacy and data

For a check, Homer sends the current task, recent transcript, and evidence needed to judge whether the completion claim is supported. Homer does not need your editor password or your model-provider API keys.

  • Check content uses zero data retention.
  • Account, balance, usage, referral, and email-preference metadata are kept so billing and account screens can work.
  • The local installer writes Homer settings and agent integration files on your machine.
Back to topics

Need the shortest path? Start with guided setup. If the answer is not here, email hello@homer.tech.