DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to hand off a half-finished task from Claude Code to Codex with AI Memory

Quit one coding agent mid-task and resume in another in the same directory with the open questions intact.

Remote script. The install command pipes a script from GitHub directly into sh, so review it first if you do not trust the source.

Who it is forA developer partway through a feature in Claude Code who needs to continue in OpenAI Codex, for example after hitting a usage limit or wanting a second agent's view.

The problemEach agent starts cold, so the architecture, failed approaches, and open questions must be re-explained by hand.

The outcomeCodex starts in the same directory with a handoff that states where the work stopped, what failed, and what is still open.

What you need first

  • A Linux or macOS machine (native Windows is experimental; WSL2 is supported)
  • At least one supported coding agent CLI installed, such as Claude Code or Codex
  • A terminal with curl and sh available

Steps

  1. Run curl -fsSL https://github.com/akitaonrails/ai-memory/releases/latest/download/install.sh | sh
  2. Run ai-memory setup
  3. Quit Claude Code in the project directory
  4. Run ai-memory run codex from the same directory

Prompt for your agent

Using the ai-memory repo (github.com/akitaonrails/ai-memory), set up the tool, then start <target-agent> in the project at <project-path> through `ai-memory run`. Expected output: the new agent begins with a brief that lists the last session's status, failed approaches, and open questions. Verify the brief mentions the open questions from the previous session before continuing.

Caveat. The README says AI Memory run gives Codex a private local projection of Claude's visible native history, so check what each agent can see before relying on it for sensitive work.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page