You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Anyone interested in a Pi integration for Concord?
#12063
I'm building Concord, an open-source MCP server that gives coding agents shared work-state across harnesses: presence, file claims, task context, messages, and handoffs.
I'd like Pi sessions to participate alongside Claude Code, Cursor, and other supported agents. For example, Pi could claim a module and leave its decisions where another agent can read them before starting related work.
The proposed integration would also let separate Pi sessions coordinate with each other. One could implement a change and another review it, sharing decisions and handoff context through Concord.
Dedicated Pi support is planned, not available yet. We've opened a tracking issue.
Would anyone who uses Pi regularly like to help with an initial integration test? The first useful step is confirming MCP setup and project instructions on a specific Pi release, then checking how resumed and forked sessions should map to agent identities.
Pi's extension APIs may also offer a route for peer-message delivery, but we haven't verified busy or idle delivery yet. Advice on that boundary would help us avoid advertising behavior we can't support.
Concord Cloud connects local, remote, and async agents in one shared workspace. Work can continue across machines and at different times, with task context and handoffs available for the next agent. Try Concord Cloud. The integration work above is still needed for this harness to join that workflow.
A short test report, an extension example, or a small PR would all be welcome. Which Pi execution mode would you start with?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I'm building Concord, an open-source MCP server that gives coding agents shared work-state across harnesses: presence, file claims, task context, messages, and handoffs.
I'd like Pi sessions to participate alongside Claude Code, Cursor, and other supported agents. For example, Pi could claim a module and leave its decisions where another agent can read them before starting related work.
The proposed integration would also let separate Pi sessions coordinate with each other. One could implement a change and another review it, sharing decisions and handoff context through Concord.
Dedicated Pi support is planned, not available yet. We've opened a tracking issue.
Would anyone who uses Pi regularly like to help with an initial integration test? The first useful step is confirming MCP setup and project instructions on a specific Pi release, then checking how resumed and forked sessions should map to agent identities.
Pi's extension APIs may also offer a route for peer-message delivery, but we haven't verified busy or idle delivery yet. Advice on that boundary would help us avoid advertising behavior we can't support.
Concord Cloud connects local, remote, and async agents in one shared workspace. Work can continue across machines and at different times, with task context and handoffs available for the next agent. Try Concord Cloud. The integration work above is still needed for this harness to join that workflow.
A short test report, an extension example, or a small PR would all be welcome. Which Pi execution mode would you start with?
All reactions