Start
Install and sign in
Install Chord for your system, sign in, and finish the short setup checklist.
Chord is a desktop app for macOS on Apple silicon, Windows (x64) and Linux (x64). Download the installer for your system and install it as you would any desktop app.
Chord runs the coding agents you already use, so it helps to have at least one agent CLI installed, such as Claude Code or Codex. If you have none yet, Chord can install supported agents for you from Settings › Agents & models.
Sign in
- Open Chord and click Sign in.
- Your browser opens the Chord sign-in page (run by WorkOS AuthKit). Sign in there.
- Chord picks up the sign-in and opens Set up Chord, a short checklist that saves as you go.
Chord asks you to sign in before first use. Your account is what lets teammates find and open the work you share.
Set up Chord
- Name your workspace, or confirm the workspace you joined from an invite.
- Default agent: Chord scans your machine for agent CLIs and preselects one. New work items start with this agent.
- Connect GitHub for pull requests, checks and reviews. Linear and Jira are optional at this step.
- Add a repository: choose a project folder that is already a Git repository.
- Invite your team by email. This step is optional.
Click Open Chord when you are done. Anything you skip can be finished later from Settings.
Start
Your first work item
Create a work item from scratch, from an issue, from a branch or from a pull request.
A work item is one piece of work, such as a feature or a bug fix. It ties a Git branch to the agent sessions, documents, linked tickets and pull request that belong to it. Anyone who opens it later finds all of that in one place.
- Click New work item in the sidebar, or press
Cmd+N (Ctrl+N on Windows and Linux). - Pick the Repo.
- In Name, type a name for the work. You can also paste a ticket key, a ticket URL or a pull request URL, and Chord works out which one it is.
- Check the Agent and write the first instruction in Prompt.
- Click Create, or press
Cmd+Enter.
Before you create it, the dialog shows what Chord is about to make: a new branch, or a checkout of a branch that already exists.
Start from an issue, a branch or a pull request
Click Create from… next to Name. It has three tabs:
- Issues: pick a GitHub, Linear or Jira issue. The work item is named from the issue key and title, and the ticket is linked for you.
- Pull requests: check out a pull request branch to keep working on it or to review it.
- Branches: pick up a branch that already exists in the repository.
If that branch is already checked out somewhere else, Chord offers Branch off to start a new lane from it instead.
Open Advanced to set a Base branch. Leave it empty and Chord branches from the remote default branch, fetched first.
Start
Lanes and worktrees
Each agent session can work in its own copy of the repo on its own branch, so parallel work stays apart.
A lane is one agent session working in its own copy of the repository, called a Git worktree, on its own branch. Agents in different lanes edit different folders, so two agents running at once do not overwrite each other’s files.
A work item starts with one lane. To add another, open the + menu in the work item’s tab bar, choose New chat in new worktree…, pick an agent and give the lane a title. Chord shows the branch name it will create before it makes it.
Lanes keep files apart while agents work. When the branches come together, you still review the changes and resolve any merge conflicts.
Where lanes live
- New checkouts go into a folder per repository. Change the location in Settings › Git & worktrees › Worktree folder.
- Git does not put ignored files in a new checkout, so Chord copies
.env* and .envrc from your main checkout into each new lane. Edit that list under Files to copy in the repository’s settings. - The right sidebar’s Work item panel lists every lane under Worktrees, with the sessions in each.
Archive a lane
When a lane is finished, use Archive on its row in the sidebar. Chord asks first, and offers Also delete the branch when that is safe to do.
Start
Chat and terminal agents
Six agents run as a native chat inside Chord, the rest run their own CLI in its built-in terminal, and all of them share your MCP servers and skills.
Chord works with more than twenty coding agent CLIs. Each agent signs in with your own account or API key, as it does today, and the provider bills you directly.
Agents that run as chat
- Codex
- Claude Code
- Qwen Code
- OpenCode
- GitHub Copilot
- Goose
A chat opens inside the work item with the agent’s tools, permission requests and documents shown as part of the conversation.
Agents that run in the terminal
Every other agent, such as Cursor, Gemini, Droid, Amp or Kiro, runs its own CLI in a terminal tab inside the work item, in the lane’s folder. You use it the same way you would in your own terminal.
To open chat agents in their CLI as well, set Settings › Agents & models › Open agents in to Terminal.
Features vary by agent. For example, Reset to here rewinds the conversation for Claude Code and Codex only; other agents get Reset files to here.
Settings › Agents & models › CLI agents shows which agents Chord detected. Use Install next to an agent that has an installer, and Check for updates to look for newer versions.
MCP servers
MCP servers give agents extra tools, such as access to a database or an internal API. Add a server once and Chord writes it into each agent’s own config.
- Open Settings › MCP Servers.
- Pick a server under Recommended, or click Custom MCP.
- For a custom server, fill in Server Name and Transport:
stdio with a Command and Arguments, or http with a URL. - Under Sync to agents, choose which installed agents get the server.
Agents that do not support HTTP servers are greyed out when the transport is http.
Skills
A skill is a set of instructions an agent loads when a task calls for it. Settings › Skills lists skills from the OpenAI and Anthropic catalogs. Install one to make it available to all your coding agents, or click New Skill to write your own. Skills follow the open Agent Skills standard.
Work
Fork, reset and import sessions
Branch a conversation from any turn, roll back files or the whole conversation, and bring in sessions you started outside Chord.
Hover a finished turn in a chat to see its actions. Only the owner of the work item sees them.
Fork a turn
Open the turn’s … menu (More for this turn) and choose one of these:
- Fork to new tab: a new chat with the same agent, starting from this turn, on the same lane.
- Fork to new worktree: the same, on a new lane made from the files as they were at this turn. Use it to try another approach and keep the original lane as it is.
Reset to a turn
- Reset to here: files go back to how they were after this turn, and the agent forgets the turns after it. Available for Claude Code and Codex.
- Reset files to here: files go back and the agent keeps its memory of later turns. Chord offers this for agents whose conversation it cannot rewind.
Before a reset, Chord saves your current files as a checkpoint. Commits made since that turn stay on the branch.
Import an existing session
A Claude Code or Codex session you started in a lane’s folder outside Chord appears in the right sidebar’s Work item panel, under that lane in Worktrees. Click Import to bring it in with its history.
Chord looks for new sessions about every 30 seconds while the panel is open. Installed agents that cannot list their sessions are named under the list.
Work
Run your app in each lane
Give a repository setup, run, test and teardown scripts, then run every lane on its own ports or one lane at a time with Solo.
Run scripts let Chord start your app from any lane. Open Settings › Repository, open the settings for your repository and find Run & test. If a repository has no scripts yet, the right sidebar’s Run panel offers Set up Run & test.
- Setup runs in each new lane’s checkout after the files are copied, for example
npm install. Agents wait for it unless you change Agent start to Start immediately. - Run is one command, or several named commands such as
web and worker. - Test runs when you press Run tests in the Run panel. Its exit code is the result.
- Teardown runs in a lane’s checkout when the lane is removed.
Each script has two save buttons. Save for me keeps it on your machine. Save to team file writes it to .chord.json in the main checkout, which you commit so the whole team gets it.
{
"scripts": {
"setup": "npm install",
"run": { "web": "npm run dev", "worker": "npm run worker" },
"test": "npm test"
},
"runMode": "perWorktree"
}
Per lane or Solo
Run mode decides how lanes share your machine:
- Per lane (
perWorktree): each lane runs its own copy in its own checkout, on its own ports. Chord gives every lane a block of ports and sets CHORD_PORT to the first one, so point your dev server at that variable. - Solo (
solo): one lane at a time runs in the repository’s own folder, so fixed ports and Docker Compose stacks keep working. Click Solo this branch in the Run panel. Other lanes can Queue behind it. Use Sync from lane to bring in the lane’s latest files and Release when you are done.
Run mode belongs to the codebase, so it is saved only in the team file. In Solo mode, a run script that starts Docker Compose should use docker compose up --remove-orphans.
Every process Chord starts for a lane also gets CHORD_LANE_ID, CHORD_ROOT_PATH (the lane’s checkout), CHORD_SOURCE_PATH (the main checkout) and CHORD_DEFAULT_BRANCH.
Scripts from the team file ask before they run in a lane: Run scripts from this repository? Tick Always trust scripts from this repository to stop the question, and turn it off later under Trust in the repository’s settings. Scripts you saved for yourself run without asking.
Work
Review changes and pull requests
Commit, push and open a GitHub pull request from the right sidebar, then follow checks and reviews inside the work item.
The right sidebar shows the lane you are focused on. Its top row offers the next Git step for that lane, such as Commit, Publish, Push, Create PR or Merge. Below it are the panels:
- Changes (
Cmd+Shift+G): the files this lane changed, as a tree, and its recent commits. - Files (
Cmd+Shift+E): the lane’s checkout. - Checks: the pull request’s checks, reviewers and comments.
Open a pull request
- Click Commit, write a message or click Generate to draft one, and commit.
- Click Publish to push the branch for the first time. Use Push for later commits.
- Click Create PR. Check the Title and Description (Generate can draft them), tick Create as draft if it is not ready, and click Create pull request.
Generate runs the agent you pick in Settings › Git & worktrees › AI once, with no tools, in an empty temporary folder. It saves no session to that agent’s history.
Follow checks and reviews
- Fix with AI on a failing check sends the failure to the lane’s agent and asks it to fix the cause in that worktree.
- Add to chat puts review feedback into the conversation. Fix with AI on a review asks the agent to address each point.
- Mark ready takes a draft pull request out of draft and notifies reviewers.
- Merge offers Merge commit, Squash and merge and Rebase and merge. GitHub decides whether the pull request can merge yet.
Review requests from GitHub also appear in Needs you on the home view.
Pull requests need a repository with a GitHub remote and a connected GitHub account.
Work
Link Linear, Jira and GitHub Issues
Connect your issue tracker, then link tickets to work items or start work items from them.
Connect a tracker
Open Settings › Integrations and click Connect next to the service.
- Linear: paste a Linear API key. In Linear, create one under Settings › Security & access › Personal API keys.
- Jira: enter your site URL (such as
https://your-domain.atlassian.net), your email and an API token from id.atlassian.com/manage-profile/security/api-tokens. - GitHub Issues: available once GitHub is connected, for repositories with a GitHub remote.
Link a ticket to a work item
- Open the right sidebar’s Work item panel.
- Next to Tickets, click + Link.
- In Link Issue, choose GitHub, Linear or Jira, search, and pick the issue.
To start new work from a ticket, use Create from… › Issues in the Create work item dialog, or paste the ticket key or URL into Name.
Work
Documents, comments, versions and drift
Plans and docs live beside the code, update live for everyone, and warn you when the files they describe change.
Documents (the app calls them artifacts) are the plans, specs and notes that belong to a work item. An agent can write one while it works, and you can add an existing file with + Add under Artifacts in the Work item panel.
People with edit access type into the same document at once and see each other’s cursors, including the agent’s.
Comments
- Select text and click Comment to pin a comment to that passage.
- Click Comments in the document’s top bar to see Open and Resolved threads. Reply, Resolve and Re-open are on each thread.
- Mention a teammate in a comment and it shows up in their Needs you.
- Select text and click Ask agent to have the agent Improve, Fix grammar, Summarize or Explain it.
Versions
Click Versions in the top bar to see the history, grouped by day, with who made each version and why. Pick an older version to view it, then click Restore to save it as the newest version, or Back to latest to return. To mark a point yourself, use Save version in the More actions menu.
Drift
When an agent writes a document from files in the repo, it lists those files as the document’s sources. If a source file changes or is deleted, the document is marked Out of date with the number of files that changed.
- Update asks the agent to bring the document up to date.
- Mark reviewed clears the warning when the document is still right.
Drift only follows the source files the agent listed. A document without sources is never marked out of date.
To publish a document to Confluence, connect Confluence in Settings › Integrations, then open Share, pick the document and switch to the Publish tab.
Team
Sharing and roles
Share a whole work item or one document, choose who can open it, and set each person to view or edit.
- Click Share in the work item’s header.
- Choose what to share: Whole work item, or one of its documents.
- Invite people by email and pick Can view or Can edit for each of them.
- Under Who has access, choose Only people invited or Everyone in your team, and the role the team gets.
Copy link copies a link that opens the work item or document in Chord for anyone who has access.
Roles
- Can view: follow the chat, the documents and the changes.
- Can edit: also co-edit documents, comment and chat.
- Author: the person who created the work item. Only the author manages sharing and runs Git actions such as commit, push and merge.
Public links for documents
To show one document to people outside Chord, open Share, pick the document and switch to the Publish tab. Turn on Public link and anyone with the link can view it in a browser without signing in. You can also let people signed in to Chord comment on it.
Public links are view-only, and a team can switch them off for everyone. A whole work item cannot be made public.
Avatars in the work item show who is looking at it right now and which document they have open.
For work you share, Chord syncs its git state, diffs, lanes and sessions so teammates can follow along. Teammates never get a checkout of your files, so the Files panel is yours alone.
Team
Agent driving and permission requests
Answer your agent’s permission requests and plans, and let teammates prompt it and answer them from their own Chord.
A chat agent asks before it runs certain tools. The request appears as a card in the chat that names the tool, with Allow once, Deny, and an always-allow option when the agent offers one.
When an agent proposes a plan, click Approve or Reject, or type what should change and send it back to the agent.
Waiting requests show on the work item in the sidebar as Needs permission or Plan to approve, and in Needs you on the home view.
Let teammates drive your agent
- Open Share with Whole work item selected.
- Turn on Let editors drive the agent.
People with Can edit can then prompt the agent, interrupt it and approve its tool requests from their own Chord. Their answer reaches your machine and the agent the same way your own click would. The agent itself keeps running on your machine.
While the switch is off, only you can prompt the agent and approve its tool requests. Only the author of the work item sees the switch.
Team
Home view and Team Pulse
See what needs you, what is running and what your team is working on, with summaries billed to your own OpenRouter key.
Click Dashboard at the top of the sidebar to open the home view. It shows each work item once, in the first section that fits:
- Needs you: work waiting on you, such as permission requests, plans to approve, review requests from GitHub and mentions.
- Running now: work items with an agent working.
- Pick back up: recent work you can resume.
In the sidebar itself, switch from Repos to Status to group work items as Needs input, Working, Ready to review and Idle.
Team Pulse
Team Pulse is a short AI-written summary of what each teammate is working on, shown on the home view. Chord generates it with your own OpenRouter API key and never proxies these calls, so the usage is billed to your OpenRouter account.
- Create an API key in your OpenRouter account.
- In Chord, open Settings › Integrations and find Team Pulse.
- Click Connect OpenRouter (the + next to OpenRouter API key), paste the key, which starts with
sk-or-, and click Save. - Optionally, change the Model.
- Back on the home view, click Generate Pulse.
Summaries run only when you press Generate Pulse, at roughly 300 tokens per teammate.
Notifications at the top of the sidebar collects updates such as work shared with you, mentions, new comments, review requests, a blocked or finished agent and a merged pull request. Choose which kinds you get in Settings › Interface › Notification types.
Reference
Keyboard shortcuts
The default shortcuts, and where to change them.
On Windows and Linux, press Ctrl wherever this list says Cmd. On a Mac, Alt is the Option key.
Cmd+K: open the command palette.Cmd+N: new work item.Cmd+Shift+N: new repository (pick a folder, and Chord makes it a Git repository and adds it).Cmd+P: go to a file in the current work item.Cmd+Shift+T: new terminal in the current work item.Cmd+L: move focus to the chat box.Cmd+Alt+E: step the chat’s reasoning effort to the next level.Cmd+Shift+G: open Changes in the right sidebar.Cmd+Shift+E: open Files in the right sidebar.Cmd+[ and Cmd+]: previous and next work item.Cmd+Alt+Left and Cmd+Alt+Right: previous and next tab.Cmd+W: close the active tab.Cmd+B: show or hide the left sidebar.Cmd+.: show or hide the right sidebar.Cmd+O: open the project in your default editor.Cmd+,: open Settings.Cmd+T: switch theme.Cmd+Enter: confirm the current dialog.
To change a shortcut, open Settings › Interface › Keyboard shortcuts. Chord tells you if the new shortcut clashes with one you already use.
Reference
Data and privacy
What stays on your machine, what syncs to Chord, and what goes to the providers you choose.
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.
Syncs to Chord
- 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.
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.
Usage data
Chord sends anonymous usage data (through PostHog) to help improve the app. To stop it, turn off Anonymous usage data in Settings › General › Privacy.
Reference
Plans and seats
Every plan has every feature; plans differ only in how many seats your team gets.
- Free: up to 5 seats.
- Pro: self-serve, paid per seat, monthly or annually, for up to 50 seats.
- Custom: for teams larger than that, set up with the Chord team.
Upgrade to Pro
- Open Settings › Team. The billing card shows your plan and how many seats are used.
- Click Upgrade to Pro. Only workspace owners and admins see this button.
- Choose the number of seats and Monthly or Annual, then click Continue to checkout.
- Finish the checkout in your browser. Your plan updates in Chord on its own.
Owners and admins open the billing portal with Manage billing to change payment details.
Your agent providers and OpenRouter bill you directly, as they do today.