#general
Sep 29September 30, 2026
Hi everyone, we love Archestra. We've been looking for centralizing our company's (https://indahash.com) AI usage in one tool and Archestra has been perfect for it. We're just starting out and already found it useful for user support queries by using knowledge base with Asana connector. Honestly, Archestra looks like a tool we've been looking for more than a year now. It looks so good. We appreciate all the hard work you've done.
However, one of the things that didnt work was an A2A API call with team's token (not personal). We are building an automation for the legal team, the trigger is outside archestra and the goal for it is to make an A2A call to Archestra with team token, because that's most suitable. Such call fails with
MCP tools unavailable: could not connect to MCP Gateway . Agent is shared with the team, MCPs are shared with the team with added service accounts shared with this team. So the setup appears to be correct.I've gone through this with Claude, here are the findings:
This same bug pattern was already fixed elsewhere in the codebase, just never ported over to this path: launch-spec.ts's resolveGatewayToken() branches on actor.kind explicitly — for a "team" actor it calls TeamTokenModel.findTeamToken(teamId) directly, looking the token up by team ID with no userId/membership indirection at all. The plain SendMessage path in a2a-manager.ts has no equivalent branch — it always resolves tokens through a userId, so once a team actor is collapsed to "system" there's no way back to its own token.```
Claude has fixed it apparently (working on tag `platform-v1.4.0-rc.27`), I am attaching a patch here. Please let me know how would you like to proceed with this:
1. You can take this patch and proceed with it in your own pace or implement the fix on your own
2. I can submit a PR
3. Correct me because all the findings are wrong and the problem is in me not being able to use the tool properly :sweat_smile:
Whichever you prefer, I just want to make the life easy for you and us :heart:👀1
3 repliesRead-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!Hi everyone, we love Archestra. We've been looking for centralizing our company's (https://indahash.com) AI usage in one tool and Archestra has been perfect for it. We're just starting out and already found it useful for user support queries by using knowledge base with Asana connector. Honestly, Archestra looks like a tool we've been looking for more than a year now. It looks so good. We appreciate all the hard work you've done.
However, one of the things that didnt work was an A2A API call with team's token (not personal). We are building an automation for the legal team, the trigger is outside archestra and the goal for it is to make an A2A call to Archestra with team token, because that's most suitable. Such call fails with
MCP tools unavailable: could not connect to MCP Gateway . Agent is shared with the team, MCPs are shared with the team with added service accounts shared with this team. So the setup appears to be correct.I've gone through this with Claude, here are the findings:
This same bug pattern was already fixed elsewhere in the codebase, just never ported over to this path: launch-spec.ts's resolveGatewayToken() branches on actor.kind explicitly — for a "team" actor it calls TeamTokenModel.findTeamToken(teamId) directly, looking the token up by team ID with no userId/membership indirection at all. The plain SendMessage path in a2a-manager.ts has no equivalent branch — it always resolves tokens through a userId, so once a team actor is collapsed to "system" there's no way back to its own token.```
Claude has fixed it apparently (working on tag `platform-v1.4.0-rc.27`), I am attaching a patch here. Please let me know how would you like to proceed with this:
1. You can take this patch and proceed with it in your own pace or implement the fix on your own
2. I can submit a PR
3. Correct me because all the findings are wrong and the problem is in me not being able to use the tool properly :sweat_smile:
Whichever you prefer, I just want to make the life easy for you and us :heart:👀1
3 replies
Hey there!, thanks for raising this!
I'll take a look at it and see whats up and keep you posted.
❤️1
Hey there.
Just to keep you posted, this should be fixed in the next 1.4.0rc28 release of archestra, as well the next patch for 1.3.
Thanks again!
This is amazing, thank you @user!