Repository navigation
Concord for Goose: shared task context and file claims across coding agents #13439
alexechoi
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm building Concord, an open-source MCP server for shared coding-agent work-state. Goose can use its workflow tools alongside other clients working on the same project.
The part I'd love people to try is shared ownership and context: Goose claims a module, another agent sees that claim, and both can read the task's decisions and handoff evidence instead of relying on a person to copy context between chats.
Separate Goose sessions can share claims and task context through Concord as well. For example, one session can record implementation decisions for another to pick up later. The inbox limitation below still applies.
npm install -g @concord-ai/concord-mcp cd your-repo concord setupWhen Goose is detected, setup adds the Concord extension to its config. Restart Goose afterwards. Setup rewrites the YAML configuration, so existing YAML comments may not survive.
There is an important boundary: Goose inbox messaging isn't supported yet. We don't have a verified Goose session endpoint for live delivery. This is an invitation to try shared work-state, not a claim that Goose can already receive peer messages.
Goose integration guide.
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.
Does this fit how you run Goose with other agents? Reports on setup and shared claims would help; pointers to a supported session-delivery API would also be welcome.
All reactions