Tigran Kostandyan in #general: "Hi everyone! Quick one for #2160 — MCP server args now support $VAR / ${VAR} refs from the env config. No more sh -c wrapping just to interpolate a v..." | Archestra Community

#general

Apr 28April 29, 2026

Hey I'm Apoorva 😀— I recently started getting into open source contributions and Archestra caught my eye, especially the MCP gateway angle. Really cool project.

Tried to open a PR for #3491 (the model selector chip thing) but got blocked by the contributor restriction, so figured I'd say hi here first.

Bit about me:

• Software Engineer at Oracle (MySQL / HeatWave release eng — Concourse, Jenkins, Terraform). Before that built a multi-agent platform at a Shopify Plus agency (LangChain, autonomous Dev + QA agents, RAG over Slack/email/meeting data)

• Mostly Python + TS day to day, CSAI background.

Took a look at #3491 and have a fix on a branch — tests pass, type-check clean.

Couple of things:

1. What's the move to get unblocked on PRs as a new contributor here?

2. Found a tiny chip flicker on reset I'd want to follow up on separately — bundle or split?

1 reply

Ayush Singh6:52 AMOpen in Slack

👋 Hi everyone!

1 reply

Harsh Panwar10:29 AMOpen in Slack

Hi everyone, I’ve seen several issues labeled ‘Reserved for SE interview.’ Are you currently hiring? Is this only for Archestra contributors, or can I also participate?

1 reply

10:31 AM

I’m also an OSS contributor. my GitHub

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

Good day, everyone!

👋1

1 reply

Tigran Kostandyan12:51 PMOpen in Slack

Hi everyone!

Quick one for #2160 — MCP server args now support $VAR / ${VAR} refs from the env config. No more sh -c wrapping just to interpolate a value. Works for both default and custom YAML deploys. PR up if anyone wants to take a look 👀

https://github.com/archestra-ai/archestra/pull/4202

Subhasmita Swain3:24 PMOpen in Slack

Hey folks! I've been working on Responses API support for the OpenAI provider

(this PR #4143), and I just noticed #4190 is tackling this related portion as well. Rather than let these evolve in parallel, I thought it'd be good to sync up.

Quick summary of what my implementation covers:

Request/Response/Stream adapters following the existing proxy pattern
Guardrail integration via toolCalls population for trusted-data evaluation
unit and e2e test coverage (12 tests + WireMock scenarios)
extends the current LLM proxy architecture

PR #4190 appears to introduce a broader Model Router architecture that

includes Responses API as one component across multiple providers.

I'm curious in understanding how these pieces could work together or inform each other

@user @user I'm happy to adapt this work based on what makes sense for the architecture, and I'd value your perspective on the best path forward.

Justin Green3:36 PMOpen in Slack

Hi all, I'm Justin I have a background in Computer Science with 8 years of experience, some at Amazon Web services, and some as a contractor .

Read-only live mirror of Archestra.AI Slack

👋Join the discussion withAI enthusiasts!