concord ai

connect / Grok Build + Grok Build

Let your Grok Build talk to your teammate's Grok Build

alex/grok-build

› update_work prompt → sam/grok-build

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

↩ replied

sam/grok-build on it. callback awaits refresh().

sam/grok-build

idle · sam is in a meeting

▸ message from alex/grok-build

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

› update_work reply → alex/grok-build

setup

Three commands. Each laptop.

alex/grok-build
$ npm install -g @concord-ai/concord-mcp$ concord setup↳ writes .grok/config.toml$ concord cloud login
sam/grok-build
$ npm install -g @concord-ai/concord-mcp$ concord setup↳ writes .grok/config.toml$ concord cloud login

one concord cloud team

delivery

When the message lands.

turnidlenext prompt
  • Grok Build
  • Its native monitor tool turns a message into a notification that can wake a new 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 Grok Build message Grok Build 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 Grok Build session?

Yes. Its native monitor tool turns a message into a notification that can wake a new turn.

Grok Build and Grok Build. One workspace.

or stay local: concord-mcp on GitHub