Troubleshooting

“Runner returned no result”

The app started its runner with your system node, but Node exited before it could answer. This shows up on Sync all and other Local sync actions.

• On the Linux AppImage, this was a bug in versions before 0.1.5: the AppImage’s own libraries leaked into Node and crashed it. Update to 0.1.5 or newer. You can also install the .deb or .rpm instead.
• Elsewhere, check that Node works on its own: run node --version in a terminal. If that fails, or prints a version older than 18, install a current Node.js and reopen ACRE.

“Install Node.js and reopen ACRE”

The app couldn’t start node. Install Node.js 18 or newer (22 LTS recommended) so node is on the system PATH, then reopen ACRE. On macOS, Node installed only through a shell version manager may be invisible to apps. See Compatibility.

“Install claude first” / “Install codex first”

The CLI isn’t on PATH. Install Claude Code or Codex, check that claude --version or codex --version works in a terminal, then reopen ACRE.

“Select subscription login in your native client first”

Your CLI is signed in with an API key, not a subscription. ACRE only runs agents on your own plan:

• Claude Code: claude auth login and choose your Claude account.
• Codex: codex login and sign in with ChatGPT.

“Sign in to a saved ACRE account first”

You’re using a guest account. Save it, or sign in with GitHub. See Signing in.

The app won’t open the first time

The builds aren’t notarized or code-signed yet. See First launch.

Sign-in didn’t come back to the app

The browser hands you back with an acre:// link, and its code works once within five minutes. If you waited longer or clicked twice, start sign-in again from the app.