veer adyani in #general: "Hey Archestra team, I’m working on this https://github.com/archestra-ai/archestra/issues/1446..." | Archestra Community

#general

Jan 25January 26, 2026Jan 27 Latest

Hello everyone, I have an update to share.

What was failing

During local startup, I kept hitting ERRCONNECT errors because the application couldn’t reach required services when I used tilt up.

I am on Windows.

How I debugged and fixed it

• I used kubectl port-forward to expose the services to localhost.

• I ran the backend and frontend separately.

Current workflow

• Terminal 1: Kubernetes (apply, verify, and port-forwards)

• Terminal 2: Backend dev server

• Terminal 3: Frontend dev server

Result: The backend connects cleanly (no ERRCONNECT), the frontend loads correctly, and I can now iterate locally while continuing to rely on Kubernetes for infrastructure.

🙌1

2 replies

Swain4:17 AMOpen in Slack

Hey all, how's everyone doing?

1 reply

raj Gg6:23 AMOpen in Slack

👋 Hi everyone!

1 reply

Debojyoti De Majumder6:29 AMOpen in Slack

Hi all

1 reply

Unknown6:34 AMOpen in Slack

6:35 AM

do we need to make our own mcp server for the wemakedevs hackathon or use mcp servers from archestra online catalog

2 replies

6:36 AM

anyone reply

6:36 AM

please

vision3910:58 AMOpen in Slack

Is there any hackathon going on?

Matvey Kukuy (archestra team)11:11 AMOpen in Slack

Yep!

https://www.wemakedevs.org/hackathons/2fast2mcp

Join Slack to see the image

❤️3🎉2

veer adyani12:48 PMOpen in Slack

Hey folks, quick heads up while working on this issue: https://github.com/archestra-ai/archestra/issues/2410

This is in the repo [https://github.com/archestra-ai/website](https://github.com/archestra-ai/website)

I ran into a Windows clone/checkout failure with error: invalid path because one of the files under app/app/mcp-catalog/data/mcp-evaluations/ had a ?tab=... in the filename, which Windows does not support.

As a temporary workaround, I renamed the file in my fork so I could clone the repo and continue working.

I also checked if this rename would impact anything in the codebase. I ran git grep "mobb-dev__bugsy" and the only matches are inside the JSON files themselves. Nothing else in the repo references these filenames, so renaming should be safe and should not break any code.

There are currently two related JSON files in that folder, and both are standalone entries, so the rename is just to make cloning work smoothly for Windows developers.

If you are okay with it, I can open a small PR to rename the file in the main repo as well. 😃

Thanks!

Join Slack to see the image

2 replies

Dhyaneesh DS1:30 PMOpen in Slack

Hey, found Archestra through the hackathon, crazy work.

Quick question, should hackathon projects focus on end-user apps or MCP middleware [https://gofastmcp.com/servers/middleware] ?

1 reply

Matvey Kukuy (archestra team)2:52 PMOpen in Slack

Welcome to all new community members! How is archestra working for you? We're actively looking for bugs to fix 🙂

🙌1

1 reply

veer adyani10:35 PMOpen in Slack

Hey Archestra team,

I’m working on this issue

The Terraform provider currently relies on the following fields and methods, which now cause compile errors because they’re missing from the latest OpenAPI spec and client:

• profileTool.AllowUsageWhenUntrustedDataIsPresent (field missing)

• profileTool.ToolResultTreatment (field missing)

• d.client.GetPromptWithResponse (method missing)

• d.client.GetPromptsWithResponse (method missing)

• d.client.GetPromptVersionsWithResponse (method missing)

• client.CreateChatApiKeyJSONRequestBody expects *string, but provider uses string

• IsOrganizationDefault (unknown field in request/response, now missing)

• r.client.SetChatApiKeyDefaultWithResponse (method missing)

These have been removed from the OpenAPI spec and backend, so the provider no longer compiles against the latest API. Do you think we should proceed with refactoring the Terraform repo to align with the new API shapes, or is there another plan? Let me know your thoughts.

Here is the backend PR link for this issue (Ready for review) : https://github.com/archestra-ai/archestra/pull/2396

1 reply

Read-only live mirror of Archestra.AI Slack

👋Join the discussion withAI enthusiasts!

Thread

veer adyani10:35 PMOpen in Slack

Hey Archestra team,

I’m working on this issue

The Terraform provider currently relies on the following fields and methods, which now cause compile errors because they’re missing from the latest OpenAPI spec and client:

• profileTool.AllowUsageWhenUntrustedDataIsPresent (field missing)

• profileTool.ToolResultTreatment (field missing)

• d.client.GetPromptWithResponse (method missing)

• d.client.GetPromptsWithResponse (method missing)

• d.client.GetPromptVersionsWithResponse (method missing)

• client.CreateChatApiKeyJSONRequestBody expects *string, but provider uses string

• IsOrganizationDefault (unknown field in request/response, now missing)

• r.client.SetChatApiKeyDefaultWithResponse (method missing)

Here is the backend PR link for this issue (Ready for review) : https://github.com/archestra-ai/archestra/pull/2396

1 reply

veer adyani2:15 PMOpen in Slack

I can definitely open an issue regarding this and the PR too (if the issue is real according to the team) , once that’s merged I can continue working on issue #1446