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.

Hello everyone

The project submission link is live on the website

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.

{

"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"

}

}

New release! 🚀🚀🚀

Bug Fixes

⚠️ 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!

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

Hi

i am getting this error while running the quickstart command

Deleted nodes: ["archestra-mcp-control-plane"]

ERROR: failed to create cluster: failed to init node with kubeadm: command "docker exec --privileged archestra-mcp-control-plane kubeadm init --config=/kind/kubeadm.conf --skip-token-print --v=6" failed with error: exit status 1

Command Output: I0213 03:29:53.144936 247 initconfiguration.go:260] loading configuration from "/kind/kubeadm.conf"

W0213 03:29:53.145640 247 common.go:100] your configuration file uses a deprecated API spec: "kubeadm.k8s.io/v1beta3" (kind: "ClusterConfiguration"). Please use 'kubeadm config migrate --old-config old-config-file --new-config new-config-file', which will write the new, similar spec using a newer API version.

W0213 03:29:53.146518 247 common.go:100] your configuration file uses a deprecated API spec: "kubeadm.k8s.io/v1beta3" (kind: "InitConfiguration"). Please use 'kubeadm config migrate --old-config old-config-file --new-config new-config-file', which will write the new, similar spec using a newer API version.

W0213 03:29:53.147052 247 common.go:100] your configuration file uses a deprecated API spec: "kubeadm.k8s.io/v1beta3" (kind: "JoinConfiguration"). Please use 'kubeadm config migrate --old-config old-config-file --new-config new-config-file', which will write the new, similar spec using a newer API version.

W0213 03:29:53.147439 247 initconfiguration.go:361] [config] WARNING: Ignored configuration document with GroupVersionKind kubeadm.k8s.io/v1beta3, Kind=JoinConfiguration

[init] Using Kubernetes version: v1.35.0

[certs] Using certificateDir folder "/etc/kubernetes/pki"

I0213 03:29:53.149466 247 certs.go:111] creating a new certificate authority for ca

[certs] Generating "ca" certificate and key

I0213 03:29:53.186784 247 certs.go:472] validating certificate period for ca certificate

[certs] Generating "apiserver" certificate and key

[certs] apiserver serving cert is signed for DNS names [archestra-mcp-control-plane kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [10.96.0.1 172.20.0.2 127.0.0.1]

[certs] Generating "apiserver-kubelet-client" certificate and key

I0213 03:29:53.392276 247 certs.go:111] creating a new certificate authority for front-proxy-ca

[certs] Generating "front-proxy-ca" certificate and key

I0213 03:29:53.448463 247 certs.go:472] validating certificate period for front-proxy-ca certificate

[certs] Generating "front-proxy-client" certificate and key

I0213 03:29:53.496347 247 certs.go:111] creating a new certificate authority for etcd-ca

[certs] Generating "etcd/ca" certificate and key

I0213 03:29:53.620613 247 certs.go:472] validating certificate period for etcd/ca certificate

[certs] Generating "etcd/server" certificate and key

[certs] etcd/server serving cert is signed for DNS names [archestra-mcp-control-plane localhost] and IPs [172.20.0.2 127.0.0.1 ::1]

[certs] Generating "etcd/peer" certificate and key

[certs] etcd/peer serving cert is signed for DNS names [archestra-mcp-control-plane localhost] and IPs [172.20.0.2 127.0.0.1 ::1]

[certs] Generating "etcd/healthcheck-client" certificate and key

[certs] Generating "apiserver-etcd-client" certificate and key

I0213 03:29:54.030291 247 certs.go:77] creating new public/private key files for signing service account users

[certs] Generating "sa" key and public key

[kubeconfig] Using kubeconfig folder "/etc/kubernetes"

I0213 03:29:54.251275 247 kubeconfig.go:111] creating kubeconfig file for admin.conf

[kubeconfig] Writing "admin.conf" kubeconfig file

I0213 03:29:54.376731 247 kubeconfig.go:111] creating kubeconfig file for super-admin.conf

[kubeconfig] Writing "super-admin.conf" kubeconfig file

I0213 03:29:54.455445 247 kubeconfig.go:111] creating kubeconfig file for kubelet.conf

[kubeconfig] Writing "kubelet.conf" kubeconfig file

I0213 03:29:54.496423 247 kubeconfig.go:111] creating kubeconfig file for controller-manager.conf

[kubeconfig] Writing "controller-manager.conf" kubeconfig file

I0213 03:29:54.541698 247 kubeconfig.go:111] creating kubeconfig file for scheduler.conf

[kubeconfig] Writing "scheduler.conf" kubeconfig file

[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"

I0213 03:29:54.254741 247 local.go:67] [etcd] wrote Static Pod manifest for a local etcd member to "/etc/kubernetes/manifests/etcd.yaml"

I0213 03:29:54.254814 247 manifests.go:125] [control-plane] getting StaticPodSpecs

[control-plane] Using manifest folder "/etc/kubernetes/manifests"

[control-plane] Creating static Pod manifest for "kube-apiserver"

I0213 03:29:54.256137 247 certs.go:472] validating certificate period for CA certificate

I0213 03:29:54.256296 247 manifests.go:151] [control-plane] adding volume "ca-certs" for component "kube-apiserver"

I0213 03:29:54.257162 247 manifests.go:151] [control-plane] adding volume "etc-ca-certificates" for component "kube-apiserver"

I0213 03:29:54.257171 247 manifests.go:151] [control-plane] adding volume "k8s-certs" for component "kube-apiserver"

I0213 03:29:54.257174 247 manifests.go:151] [control-plane] adding volume "usr-local-share-ca-certificates" for component "kube-apiserver"

I0213 03:29:54.257178 247 manifests.go:151] [control-plane] adding volume "usr-share-ca-certificates" for component "kube-apiserver"

I0213 03:29:54.258932 247 manifests.go:178] [control-plane] wrote static Pod manifest for component "kube-apiserver" to "/etc/kubernetes/manifests/kube-apiserver.yaml"

I0213 03:29:54.258971 247 manifests.go:125] [control-plane] getting StaticPodSpecs

[control-plane] Creating static Pod manifest for "kube-controller-manager"

I0213 03:29:54.259673 247 manifests.go:151] [control-plane] adding volume "ca-certs" for component "kube-controller-manager"

I0213 03:29:54.259707 247 manifests.go:151] [control-plane] adding volume "etc-ca-certificates" for component "kube-controller-manager"

I0213 03:29:54.259712 247 manifests.go:151] [control-plane] adding volume "flexvolume-dir" for component "kube-controller-manager"

I0213 03:29:54.259715 247 manifests.go:151] [control-plane] adding volume "k8s-certs" for component "kube-controller-manager"

I0213 03:29:54.259718 247 manifests.go:151] [control-plane] adding volume "kubeconfig" for component "kube-controller-manager"

I0213 03:29:54.259720 247 manifests.go:151] [control-plane] adding volume "usr-local-share-ca-certificates" for component "kube-controller-manager"

I0213 03:29:54.259723 247 manifests.go:151] [control-plane] adding volume "usr-share-ca-certificates" for component "kube-controller-manager"

I0213 03:29:54.264736 247 manifests.go:178] [control-plane] wrote static Pod manifest for component "kube-controller-manager" to "/etc/kubernetes/manifests/kube-controller-manager.yaml"

I0213 03:29:54.264781 247 manifests.go:125] [control-plane] getting StaticPodSpecs

[control-plane] Creating static Pod manifest for "kube-scheduler"

I0213 03:29:54.265009 247 manifests.go:151] [control-plane] adding volume "kubeconfig" for component "kube-scheduler"

I0213 03:29:54.266366 247 manifests.go:178] [control-plane] wrote static Pod manifest for component "kube-scheduler" to "/etc/kubernetes/manifests/kube-scheduler.yaml"

I0213 03:29:54.266403 247 kubelet.go:69] Stopping the kubelet

[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"

[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/instance-config.yaml"

[patches] Applied patch of type "application/strategic-merge-patch+json" to target "kubeletconfiguration"

[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"

[kubelet-start] Starting the kubelet

I0213 03:29:53.300675 247 loader.go:405] Config loaded from file: /etc/kubernetes/admin.conf

I0213 03:29:53.301533 247 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=true

I0213 03:29:53.301598 247 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false

I0213 03:29:53.301607 247 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false

I0213 03:29:53.301613 247 envvar.go:172] "Feature gate default state" feature="InOrderInformers" enabled=true

I0213 03:29:53.301617 247 envvar.go:172] "Feature gate default state" feature="InOrderInformersBatchProcess" enabled=true

I0213 03:29:53.301622 247 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=true

[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests"

[kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s

[kubelet-check] The kubelet is not healthy after 4m0.001654422s

Unfortunately, an error has occurred, likely caused by:

- The kubelet is not running

- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:

- 'systemctl status kubelet'

- 'journalctl -xeu kubelet'

error: error execution phase wait-control-plane: failed while waiting for the kubelet to start: The HTTP call equal to 'curl -sSL http://127.0.0.1:10248/healthz' returned error: Get "http://127.0.0.1:10248/healthz": context deadline exceeded

k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:262

k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:450

k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:234

k8s.io/kubernetes/cmd/kubeadm/app/cmd/init.go:135

github.com/spf13/cobra@v1.10.0/command.go:1015

github.com/spf13/cobra@v1.10.0/command.go:1148

github.com/spf13/cobra@v1.10.0/command.go:1071

k8s.io/kubernetes/cmd/kubeadm/app/kubeadm.go:48

main.main

k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25

runtime.main

runtime/proc.go:285

runtime.goexit

runtime/asm_amd64.s:1693

ERROR: Failed to create KinD cluster

can anyone please help me with this?

<!everyone> :rotating_light: Project Submissions for 2 FAST 2 MCP hackathon are now OPEN! ⚡

Built something blazing fast with MCP? Now’s the time to ship it 🚀

✅ Submit your project

✅ Share your demo & repo

✅ Share a short demo video about the project

:alarm_clock: Don’t wait till the deadline rush. Submit early so you can iterate, polish, and make your project stand out.

🔗 Submit your project here: https://forms.gle/23VfngcFUy1JGEjE8

will all entry get participation certificate?

How do we add members in the archestra.ai site for the hackathon , when i have tried to share the invitation link to my team members , they were getting an invalid link message

New release! 🚀🚀🚀

Features

Bug Fixes

iadded the api key but not shown

Hey..I have a Master Orchestration Agent connected to multiple sub-agents and a self-hosted MCP server, and orchestration works correctly when triggered from the Archestra UI chat. However, when my external frontend tries to trigger orchestration via the /api/chat endpoint, Archestra returns errors like Unauthenticated, and falls back to frontend-side mock orchestration. As a result, no agent runs or MCP tool calls appear in Archestra logs. My goal is to trigger the Master Orchestration Agent programmatically from an external frontend and receive the real orchestration response. What is the correct way to initiate a new agent orchestration session via API so it runs fully inside Archestra so that i can have an orchestration first system rather than a chat based ui first system

1. Failed to connect to MCP server atlassian__remote-mcp: Streamable HTTP error: Error POSTing to endpoint: Missing sessionId parameter

Hey my MCP tools are registered and work when invoked manually, but A2A-triggered messages don’t result in tool execution or resolution.

Is there a required config (agent mode, tool trust policy, or run trigger setting) to ensure message/send actually starts autonomous execution?

Looking for the correct way to programmatically trigger a fully autonomous agent run from an external frontend?

Hey team 👋 Here’s my hackathon submission: PitCrew Incidents (Archestra + MCP) : https://www.youtube.com/watch?v=OLO5L_fgJeY

Getting issues with the quickstart guide, can anyone help, please?

I’ve created multiple agents, along with a parent agent that orchestrates them. When I send a request to the parent agent, it correctly delegates the task to a child agent. However, the request fails with an error stating that the LLM API key is not set for the individual agent.

I’m confused because I’ve already configured the LLM API key globally. Despite this, the system seems to require the API key to be set separately for each agent.

Is it actually necessary to configure an LLM API key for every individual agent, or should a single global key be sufficient?

i tried the gateway mode of archestra on first day it worked archestragatewaymode !! i think its allowed .. can i get a confirmation?

hello organisers!

sorry i had a busy week and now that the weekend is here im planning to hack something with Archestra for the 2 fast 2 mcp hackthon

joining late wont disqualify me right?

and just to double check I can make my submission till 15th Fe 11:59pm (GMT+5:30) right?

Hello! Had fun working on this.

And AI said, Let there be Light. (a light read, not ai-gen : D )

Cheers.