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

How to compare answers from Codex and Claude Code in one thread with Endo

Ask one question, switch agents mid-thread, and dig into the answer that fits best.

Who it is forA developer who has both Codex and Claude Code subscriptions and wants a second opinion without juggling two apps.

The problemEach agent CLI keeps its own history, so comparing answers means copying context between tools by hand.

The outcomeOne chat thread where each agent sees the full history, plus a focused Dig In on the strongest answer.

What you need first

  • A Mac with Apple Silicon for the signed download, or Node.js 24, Bun 1.4.2 and Just for running from source
  • An existing codex, claude, Antigravity or grok login, or a provider set up in Settings → Models
  • A workspace folder where workflow files can live

Steps

  1. Install Endo from the Quick start link, or clone the repo with git clone https://github.com/longsurf-ai/endo.git.
  2. Sign in with your existing codex and claude logins, or set providers in Settings → Models.
  3. Ask your question in a new thread, then switch the model to the other agent mid-thread.
  4. Select the part of an answer you want to examine and choose Dig In to open a focused side conversation.

Prompt for your agent

Using the longsurf-ai/endo repo, set up a chat where <my question> is answered first by Codex, then by Claude Code in the same thread. Expected output: two answers in one thread, with the second agent referring to the first. Verify that the Claude Code answer reflects the earlier history.

Caveat. The README says Endo drives each provider through its own CLI, so you need working codex and claude logins on the same machine before the comparison runs.

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