Req2CodeExplore Workbench

TROUBLESHOOTING

Fix common
problems.

Find the message you’re seeing below. If it doesn’t help, contact support with the details listed at the end.

AI TOOLS

Connecting
an AI tool.

“Install … to connect your account.”
Workbench can’t find that provider’s CLI. Install it using the provider’s instructions, then click Try again in the sign-in window or Refresh session in the conversation. You don’t need to restart Workbench.
“Connect your … account to continue.”
The CLI is installed but signed out. Click Sign in to … in the conversation and follow the tool’s instructions; a browser may open. If the sign-in window can’t start, open Manual instructions, copy the command, run it in a terminal, then click Try again.
Claude is using a different account or billing method
Workbench accepts the authentication reported by Claude Code, including subscription, API-key, token and cloud-provider configurations. An environment variable or Claude Code setting may take precedence over the login you just completed. Read the method shown in Workbench and its guidance before continuing. To use another account, update the relevant configuration, sign in again if needed, then click Try again.
Does Workbench use credentials from my shell?
Yes. Workbench passes the shell environment to Claude Code. Variables such as ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN and CLAUDE_CODE_OAUTH_TOKEN, along with Claude Code settings, can affect authentication and billing. Check the active method in Workbench. For a subscription login, use claude auth login; for an Anthropic Console login, use claude auth login --console. Existing configuration may still take precedence.
Grok won’t connect
Grok uses its own CLI sign-in. Run grok login in a terminal, or use Sign in to Grok in the conversation, then click Try again.
Which CLI versions are supported?
See the qualified CLI versions for Workbench 0.1.2 build 714. Other versions may work but are unverified; compatibility issues may require reproduction on a qualified version. Include your CLI version when reporting a problem.
Updating an AI tool’s CLI
Workbench checks for newer CLI versions and shows Update beside the provider when one is available. Open Settings → Providers to see each CLI’s version, click Check Now, or turn Check automatically on or off. Workbench uses the same installer you used (Homebrew, npm or the provider’s own installer) and waits until that provider is idle. If it can’t identify how a CLI was installed, update it with the tool you installed it with. Refresh open conversations afterwards to use the new version.

NETWORK

Waiting
for network.

A conversation shows “Waiting for network” or “Offline”
Workbench has detected a connection problem. Check your network, then review the last response and any running work before continuing. Automatic recovery is not guaranteed. If the conversation stays stuck after connectivity returns, open Session → Refresh session in the conversation toolbar. This reconnects to the same provider conversation without replaying messages. Local history and drafts are preserved; check queued messages before resuming.

LICENCE

Activating
Pro.

Licence controls are in Workbench → Settings → Licence. Your projects and documents stay accessible whatever happens to your licence.

“The license or this Mac’s activation is no longer valid.”
Check that you pasted the whole key, with no extra spaces. Use Manage Purchases / Find License Key… or the Polar customer portal ↗ to copy the key again and confirm the licence is active.
“This license has reached its device limit.”
Pro works on up to 3 Macs. Free a slot by opening Workbench on a Mac you no longer use and choosing Deactivate This Mac…, or remove a device in the Polar customer portal ↗. Then activate again.
Status shows “Offline grace”
Workbench couldn’t reach the licensing service. Pro keeps working offline for up to 7 days, and Settings shows when offline access ends. Reconnect and click Check License. If the grace period ends, Workbench falls back to Free without deleting anything, and Pro returns once your licence is verified.
“Workbench could not access the license in Keychain.”
Your licence is stored in your Mac’s Keychain. Unlock Keychain or allow access when macOS asks, then click Retry Keychain Access.
“Activation needs recovery”
An activation was interrupted. First check the Polar customer portal ↗ and remove any device allocation left behind for this Mac. Then click Clear Incomplete Activation… and activate again. Clearing doesn’t release an allocation that still exists in Polar.
“Check the Mac’s date and time”
Your Mac’s clock changed. Make sure the date and time are set correctly, then click Check License while online.

APP UPDATES

Updates
not arriving?

Check manually
Workbench checks for updates automatically and asks before installing. To check now, choose Workbench → Check for Updates…, or open Settings → Updates, which also shows your version and build. Updates are signed and verified on your Mac before they install.
Nothing found or the check fails
Make sure your Mac is online and that a firewall or VPN isn’t blocking the connection, then try again. Release notes for every version are on the releases page.
An agent is still working
Installing an update relaunches Workbench. If an agent is still working, Workbench asks before quitting, because quitting interrupts its current work. Choose Cancel to let it finish first.

FIRST LAUNCH

macOS won’t
open Workbench?

macOS asks whether to open an app from the internet
This is expected the first time. Workbench is signed by Req2Code and notarized by Apple; choose Open.
macOS says Workbench can’t be opened or verified
Delete the copy and download it again from the download page, then compare the SHA-256 checksum shown there. Drag Workbench into Applications before opening it, rather than running it from the disk image. If the warning persists, don’t bypass it; contact support.
Workbench won’t start on my Mac
Workbench requires macOS 27 or later on a Mac with Apple Silicon. Intel Macs aren’t supported.

CONTACT SUPPORT

Still stuck?
Email us.

Use Help → Contact Support…
It opens an email to support@req2code.com with your Workbench version and build in the subject.
Include these details
  • Your Workbench version and build (Settings → Updates)
  • Your macOS version
  • The AI tool involved and its CLI version (Settings → Providers)
  • The exact message you see, and the steps that lead to it
Please don’t send passwords, API keys, licence keys, tokens or private source code. If Workbench crashes, you can attach the crash report after reviewing it for sensitive information.