#general
Hi is any other way to deploy the application just the chat bot or agents part not deploying the whole application
Hi team, I've been stuck on this for a while. Here's my issue.
I've an agent called "head" that assigns work to other subagents each responsible for certain MCP tooling. There subagents are working perfectly and I have no qualms with their chats or their MCP tooling.
Now, when I try to go to "head" and send a message to try and use the subagents, it throws an error.
{"code":"unknown","message":"An unexpected error occurred. Please try again.","isRetryable":false,"originalError":{"provider":"cerebras","message":"Error: LLM Provider API key not configured. Please configure it in Chat Settings.","type":"Error","raw":{}}}
For additional context, keys are already configured in the following places -> the main settings, each agent setting also has the API key selected (including "head" itself).
Remediation tried -> docker restart, change API keys, clear out the cache, check env, do the whole thing again from scratch.
Am I using subagents wrong? As per my general understanding of subagents this is how it's supposed to be. There is nothing to say otherwise in the docs as well.
Of course, I can get my project to work by putting all the tools in a single chat (and it does) but that doesn't fully calm my curiosity. Appreciate what you guys do, cheers.
Have a look
Hi Archestra team — I’m running archestra/platform:latest via Docker and hitting an error when trying to create a Personal Token and call an A2A agent endpoint.
Issue: Personal token creation fails and A2A auth doesn’t work.
Error returned:
{
"jsonrpc": "2.0",
"id": 1,
"error": {
"code": -32603,
"message": "Failed query: insert into \"usertoken\" (\"id\", \"organizationid\", \"userid\", \"name\", \"secretid\", \"tokenstart\", \"createdat\", \"lastusedat\") values (default, $1, $2, $3, $4, $5, default, default) returning \"id\", \"organizationid\", \"userid\", \"name\", \"secretid\", \"tokenstart\", \"createdat\", \"lastusedat\"\nparams: default-org,system,Personal Token,7aff233b-0062-4f29-9464-74d09078023a,archestra81fa"
}
}
⚠️ Quick Announcement ⚠️ Update to version 1.0.43 if you had issues with calling subagents from the parent agent.
We’ve fixed the issue when calling subagent from parent agent resulted in
LLM Provider API key not configured. Please configure it in Chat Settings error.Thanks everyone for reporting this bug!
🚀4❤️1🙌1
Hi team — I'm testing an A2A *sub-agent* locally and getting an empty response from message/send.The request succeeds and returns a messageId, but parts.text is empty in the result.
Endpoint:
<http://localhost:9000/v1/a2a/333c740d-7abe-4c8e-b624-17f7dc4beb46>I’m attaching a screenshot of the request/response.
Is there any additional config or step required for sub-agents to return text output?
Response:
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"messageId": "msg-1770910322166-4ok4ag8",
"role": "agent",
"parts": [
{
"kind": "text",
"text": ""
}
]
}
}
We are trying to configure archestra with ollama llm but we are getting an error, any idea how to resolve this
Getting this error when trying to add any mcp in the mcp registry
Read-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!Hi is any other way to deploy the application just the chat bot or agents part not deploying the whole application
2 replies
It's possible to deploy without attaching k8s cluster:
-e DATABASE_URL=postgres://... \
-v archestra-app-data:/app/data \
archestra/platform```
which makes mcp orchestration inside archestra unavailable, but still should allow you to run agents and use chat
team