A lecture hall. The presenter, whose head is a vintage CRT monitor showing the Chord logo, points at a projector screen showing the Chord app.

chord / platform

Team invitations

SNYShare
plan.mdDocument · edit togetherv3

Team invitations

Let workspace owners invite their team with a link, and keep access clear from day one.

Approach
  • ✓ Create single-use invitation links
  • ✓ Choose a role before sending
  • ✓ Expire unused invitations after 7 daysSarah
  • ✓
1

Nate 12 min ago

Let’s check the role again when the invite is accepted, not only when it’s sent.

Claude Code Added to the approach. I’ll cover it in the invitation-flow lane.

Your agents work in parallel. Your team should too

Plan together, run coding agents side by side in separate Git worktrees, and review the result with the plan and the pull request in one place.

See it work

One work item. Everyone and every agent in it

Click a tab, a lane or the plan. This is the Chord window, recreated

In every lane, the controls an agent run needs

A lane is one agent on its own branch, in its own Git worktree. Each one comes with these.

  • Use each agent the way it works best

    Six agents, Claude Code and Codex among them, open as a chat with tool calls and diffs shown inline. Every other agent runs its own CLI inside Chord’s terminal, so nothing it can do is lost.

  • Try a second approach from any reply

    Open the menu on a reply and choose Fork to new tab, or Fork to new worktree so both attempts can change files without touching each other.

  • Undo an agent’s wrong turn

    Reset to here rewinds the conversation and the files to that message. Reset files to here keeps the chat and puts only the files back.

  • Keep the sessions you already started

    Chord finds the Claude Code and Codex sessions already on your machine. Import one and it carries on inside a work item with its full history.

  • Run every lane’s version of your app

    Set the setup and run scripts once for the repository. Each lane starts its own copy on its own port, so two versions of a feature can be open side by side.

  • Fixed ports or Docker Compose? Use Solo

    Some stacks can only run from your project folder. Switch the repository to Solo and one lane at a time runs there. Chord puts the folder back the way it was when that lane is done.

How a piece of work moves through Chord

01Plan

Agree on the plan before anyone writes code

The plan is a shared document inside the work item. Your team and the agent edit it together, so the build starts from something everyone has read.

  1. plan.md · edited together

    Team invitations

    Approach

    1. Create single-use invitation links.
    2. Choose a role before the invite is sent.Sarah
    3. Re-check the role when the invite is accepted.Claude Code
    4. Expire unused invitations after 7 days.

    Write it together

    Everyone’s cursor shows up live, the agent’s included. You can see Sarah typing in Approach while Claude Code adds a step under it.

  2. Approach

    2. Choose a role before the invite is sent.

    3. Re-check the role when the invite is accepted.

    4. Expire unused invitations after 7 days.

    NNateon line 3

    Check it again on accept, not only on send. Roles can change in between.

    SAgreed, added to step 3.

    Comment on the exact line

    A comment stays pinned to the line it is about, so the reply makes sense a week later.

  3. plan.md · v1

    Team invitations

    plan.md · v2

    Team invitations

    plan.md · v3

    Team invitations

    plan.md · v5

    Team invitations

    plan.md · v6 · now

    Team invitations

    plan.md · v4 · yesterday

    Team invitations

    Restore this version

    Go back to any version

    Every version is kept. Open an older version of the plan and restore it if the new direction was wrong.

02Build

Run several agents without them colliding

Each agent works in a lane: its own Git worktree on its own branch. They run at the same time and never write over each other’s files.

  1. Claude Codeinvitation-flow
    Writing invitations/accept.ts
    Codexpermission-tests
    Waiting for you
    Geminisearch-index
    Indexing search · 3 min

    3 lanes · 3 worktrees · 3 branches

    One lane per attempt

    Give Claude Code the invitation flow and Codex the permission tests. Each one has a separate copy of the repository.

  2. Permission request

    Codex wants to run

    npm test -- invitations

    Team invitations · lane permission-tests

    AllowDeny

    Answer requests where they appear

    When an agent asks to run a command, the request waits in the lane and in your home view until someone allows or denies it.

  3. Agent driving

    Editors can prompt this agent and answer its permission requests.

    NNate, from his Chord

    Add a test for an expired link before you open the PR.

    Adding expired-link.test.ts

    Let a teammate steer

    Switch on agent driving and an editor can prompt your agent or answer its requests from their own Chord.

03Review

Review the change next to the reason for it

The diff, the checks and the pull request sit beside the plan that produced them, so the reviewer can see what was asked for and what was done.

  1. Changes · invitation-flow · 3 files

    src/invitations/accept.ts +12 −3

      const invite = await findInvite(token)- if (!invite) return notFound()+ if (!invite || invite.usedAt) return expired()+ const role = await currentRole(invite.teamId)+ await addMember(invite.teamId, user, role)  await markUsed(invite)

    Read the diff in context

    Open Changes to see every file a lane touched, with the plan one tab away.

  2. api-notes.md · document

    Accepting an invitation

    Invitations expire after 7 days.

    src/invitations/invite-token.tschanged

    Out of date · 1 source file changed

    UpdateMark reviewed

    Catch documents that went stale

    A document linked to source files is marked Out of date when those files change. Ask the agent to update it, or mark it reviewed.

  3. Pull request #248

    Team invitations

    • Typecheck
    • Unit tests
    • Review · Nate approved
    Mergeinto main

    Merge when the checks pass

    Create the pull request, follow its checks and reviews, then merge it from the work item.

04Keep up

Know what needs you before anyone asks

The home view collects what is waiting on you and what is running. Team Pulse adds a short summary of what each teammate is working on.

  1. Home · Needs you · 3

    Permission request

    Codex wants to run npm test

    Team invitations

    Plan approval

    Claude Code finished a plan

    Search improvements

    Review requested

    Nate asked you to review #248

    3 of 3 checks passed

    Needs you

    Permission requests, plan approvals and review requests in one list, each with the work item it belongs to.

  2. Team Pulse · this morning

    SSarah

    Tightened the invitation plan and asked for a role check on accept. Now drafting the empty-state copy.

    NNate

    Reviewing pull request #248. Tests for expired and reused links are close to done.

    Team Pulse

    A few sentences per teammate on what they are doing now, written with your own OpenRouter key.

  3. An agent is blockedCodex is waiting in permission-tests
    An agent finishesClaude Code finished invitation-flow
    A pull request merges#248 merged into main
    You’re mentionedSarah mentioned you in plan.md

    Only the alerts you want

    Choose which events notify you: an agent is blocked or finishes, a review is requested, a pull request merges, someone mentions you.

Bring your agents. Keep your tools

Each agent keeps its own sign-in, models and permissions. Chord connects the services your team already uses to the work item, so the ticket, the code and the review stay in one place.

25 coding agents work in Chord today

  • Opens as a chat in Chord (6)
  • Runs its own CLI in Chord’s terminal
  • Codexchat
  • Claude Codechat
  • Devinterminal
  • Cursorterminal
  • Geminiterminal
  • Qwen Codechat
  • Droidterminal
  • Ampterminal
  • OpenCodechat
  • Hermes Agentterminal
  • GitHub Copilotchat
  • Charmterminal
  • Auggieterminal
  • Goosechat
  • Kimiterminal
  • Kilocodeterminal
  • Kiroterminal
  • Rovo Devterminal
  • Clineterminal
  • Continueterminal
  • Codebuffterminal
  • Mistral Vibeterminal
  • Piterminal
  • Autohand Codeterminal
  • Roo Codeterminal
  • Open, check and merge pull requests

    Create the PR from the work item, follow its checks and reviews, then merge without switching to the browser.

  • Start from the ticket you were given

    Link a Linear, Jira or GitHub issue to a work item, or start a new work item straight from an issue, a branch or a pull request.

  • Add an MCP server once

    Chord writes it into every agent’s own config file, in each agent’s format.

    • Figma
    • Sentry
    • Supabase
    • Notion
    • Slack
    • Stripe
    • Vercel
    • Playwright
    • Cloudflare
    • Linear
    • PostHog
    • Context7
  • Open any lane in your editor

    Jump from a lane to its folder in the editor or terminal you already use.

    • VS Code
    • Cursor
    • Zed
    • Xcode
    • IntelliJ IDEA
    • WebStorm
    • PyCharm
    • Windsurf
    • Ghostty
    • iTerm2
    • Warp
  • Skills from the public catalogs

    Browse and install skills from the Anthropic and OpenAI catalogs, or write your own.

  • Sessions you already have

    Import Claude Code and Codex sessions from your machine, with their history.

  • Confluence for the rest of the company

    Publish a document to Confluence when other teams read there.

Keyboard first

  • ⌘ K Command palette
  • ⌘ N New work item
  • ⌘ P Go to file
  • ⌘ ⇧ T New terminal
  • ⌘ ⇧ G Changes
  • ⌘ [ ] Previous / next work item

Pay for seats. Every feature comes with each one

Plans only differ in how many people can join your team. Start free with up to five, and add seats when more people need to be in the work.

  1. Free

    For a small team trying Chord on real work.

    $0for the team

    • Up to 5 seats
    • No card needed
  2. Custom

    For organizations with more than 50 people in Chord.

    Talk to us

    • A seat limit set for you
    • Set up directly with us
    Email us

On every plan

  • Parallel lanes, each in its own Git worktree
  • All 25 supported coding agents
  • Shared work items, documents and comments
  • Live presence and agent driving
  • Documents that flag when their code changes
  • Home view and Team Pulse
  • GitHub, Linear and Jira
  • MCP servers and skills for every agent

Your agents run on your own accounts and keys, so model usage stays on the bill you already get from each provider. Upgrade from Settings › Team › Upgrade to Pro inside the app.

Know where the work goes

Your code and your agents run on your machine. What syncs is what your team needs to see, and the providers you pick only get what their sessions need.

01

Stays on your machine

  • Your repositories, worktrees and files
  • Agent runtimes, signed in with your own accounts and keys
  • Agent session history
  • Credentials, kept in your operating system’s secure storage

02

Syncs to Chord when you sign in

  • Work items and their conversations
  • Documents, comments and versions
  • For work you share: git state, diffs, lanes and sessions
  • Plan and permission requests, so teammates can answer them

03

Goes to the providers you choose

  • Prompts and files, to the agent provider running that session
  • Team Pulse summaries, generated with your own OpenRouter key
  • GitHub, Linear, Jira and Confluence, when you connect them

Anonymous telemetry can be switched off in Settings.

Questions, answered plainly

The things teams ask before they bring their agents into a shared space.

Is Chord a coding agent?

No. Chord is the workspace around your coding agents. You bring the agents you already use, and Chord gives each piece of work a shared home for the plan, the sessions, the changes and the people involved.

Which agents does it support?

Chord works with more than twenty agent CLIs, including Claude Code, Codex, Cursor, Gemini, GitHub Copilot, OpenCode, Droid, Amp, Goose and Kiro. Some run as a native chat inside Chord; the rest run in its built-in terminal. Available features vary by provider.

Can I use it on my own?

Yes. Chord asks you to sign in once, then work items, lanes and agent sessions are yours alone until you invite someone. Your code and session history stay on your machine either way.

How does parallel work stay separate?

Each lane is its own Git worktree and branch, so agents working at the same time don’t overwrite each other’s files. You still review and resolve any merge conflicts when the work comes together.

What can my teammates do in my work item?

It depends on the access you give them. Viewers can follow along; editors can co-edit documents, comment and chat. Prompting your agent or answering its permission requests stays behind a separate agent-driving switch for each work item.

What is Team Pulse?

A short AI-written summary of what each teammate is working on, shown on the home view next to Needs you and Running now. Summaries are generated with your own OpenRouter key.

Which platforms does it run on?

Chord is a desktop app built for macOS on Apple silicon, Windows (x64) and Linux (x64).

What does it cost?

Free covers a team of up to five. Pro is priced per seat, billed monthly or yearly, for up to 50 people, and larger organizations can ask for a Custom plan. Every plan has every feature. Your agent providers keep billing you directly for model usage, as they do today.

The lecture hall after class. An empty seat with a laptop on its desk waits in the front row while the CRT-headed presenter waves.

There’s a seat
saved for you

Bring your team and the agents you already use. Free for up to five people, on macOS with Apple silicon, Windows and Linux.

Read the docs

Chord is almost ready for you.

The public download hasn’t been linked to this page yet. Chord is a desktop app built for these platforms:

macOS · Apple siliconWindows · x64Linux · x64
See how it works →