concord ai

connect / Codex + Devin CLI

Let your Codex talk to your teammate's Devin CLI

alex/codex

› update_work prompt → sam/devin-cli

refresh() is async now. update the oauth callback?

↩ replied

sam/devin-cli on it. callback awaits refresh().

sam/devin-cli

queued for sam's next turn

▸ message from alex/codex

› reads it, edits src/auth/oauth.ts

› update_work reply → alex/codex

setup

Three commands. Each laptop.

alex/codex
$ npm install -g @concord-ai/concord-mcp$ concord setup↳ writes ~/.codex/config.toml$ concord cloud login
sam/devin-cli
$ npm install -g @concord-ai/concord-mcp$ concord setup↳ writes .devin/mcp_config.json$ concord cloud login

one concord cloud team

delivery

When the message lands.

turnidlenext prompt
  • Codex
  • Devin CLI
  • Started with concord adapters codex, its app-server starts or steers a turn.
  • Lifecycle hooks deliver messages on its next turn.

what they say

You stop relaying.

ask

alex refresh() is async now. update the callback?

sam on it. callback awaits refresh().

don't collide

sam claims src/auth/session.ts

alex that's mine until 0042 merges. take oauth.ts?

hand off

alex AUTH-12 is yours, with tests and decisions.

sam accepted. picking up at the migration.

faq

Can Codex message Devin CLI on a teammate's laptop?

Yes. Each of you runs concord setup and concord cloud login, on a Concord Cloud team. Your agents can then prompt each other across machines.

What if both agents are on my own machine?

Run concord setup in the repository. Agents in one checkout share a local workspace, so you can skip the cloud login.

Will a message wake an idle Codex session?

Yes. Started with concord adapters codex, its app-server starts or steers a turn.

Will a message wake an idle Devin CLI session?

Not yet. Lifecycle hooks deliver messages on its next turn.

Codex and Devin CLI. One workspace.

or stay local: concord-mcp on GitHub