Never get rate
limited again.

When Claude Code, Codex or Cursor stops on a usage limit, Harlay moves the task to another agent, or to your other account, with everything it needs to pick up on the same line.

Why Harlay

Or with npm

macOS desktop app, Apple silicon and Intel. Run the same command again to update. npm builds it on your Mac and adds the harlay CLI (Node 22 or newer).

Works withClaude CodeCodexCursorGemini CLIclaude.aiChatGPTGemini

Claude won’t hand your work to Cursor. Cursor won’t hand it to Codex. Harlay will.

They compete for your subscription, so none of them will build the way out. Harlay sits above all of them, on your Mac, and turns every limit into a handoff.

Without Harlay
1h 48m

Waiting for the 6:00 PM reset, or twenty minutes pasting logs into another tool and explaining the task again.

With Harlay
Seconds

The same task, open in the next tool, starting on the line where the last one stopped.

Your logs stay on your Mac.

Only the handoff moves, and only to where you send it.

Reads, never uploads

Session logs and git are read on your Mac, and a web chat only while it’s in front. There’s no Harlay server.

You send it

The prompt is typed in, not sent. Read it, then press Enter. Or turn on auto-continue.

Your accounts

Targets open in the apps and sites you’re signed in to. Harlay never reads your sign-ins or API keys.

Long-running agents can call it too.

Harlay ships an MCP server for Claude Code, Codex and Cursor. An agent checks how much of its limit is left and, before it runs out, hands itself off with its own note on what’s next.

harlay mcp install
  • harlay_status

    How much of its limit is used, whether the chat is going in circles, and what to do next.

  • harlay_targets

    Every agent and account it can move to, and which ones still have room.

  • harlay_handoff

    Writes the handoff with the agent’s own note. It opens the next agent only if you’ve allowed agents to.

Stop waiting for the reset.

Or with npm