Hey everyone! 👋

My name is Abdellah Bouarguan. I've been diving into Archestra recently and find the project and what you're building incredibly interesting!

I would love to work on the UI state desync and concurrency vulnerability (Issue #4030).

---

About me

---

Proposed approach

I’m looking to tackle this issue not just for the bounty, but as a practical architecture assignment for my engineering program.

My current plan to fix the double-execution race condition is:

- Using an "ON CONFLICT" write-lock

- Located in "chat-mcp-client.ts"

- Flip abandoned "approval-requested" states → "output-denied"

- Before DB persistence

---

Since the contributing docs highly recommend syncing with the core team first, I wanted to drop in and say hi!

Do you have any specific guides, architectural design choices, or feedback on this approach before I officially post my "/attempt" claim and spin up a PR?

Thanks!

Good Monday, everyone! 👋

Guys, do you have logo in .svg? I'd like to check a possibility of fix the size.

Hey everyone! Just joined and set up Archestra locally — really impressive project.

I've been going through the open issues and noticed the swap_agent bug in Slack/MS Teams (#4011). That caught my eye because I recently built a multi-channel AI bot with RAG and chatops integrations (Telegram + Discord), so I'm comfortable in that space.

Are there areas especially around agent triggers or chatops where the community could use more testing or bug reports? Happy to explore in and contribute properly.

Community call is tomorrow! See you!

Propose your agenda in 🧵

Hey! I noticed that when a tool result policy is blocked, the agent can confuse result blocking with call blocking. I could not find this mentioned in GH, looks like bug

New release! 🚀🚀🚀

Bug Fixes

---

This PR was generated with Release Please. See documentation.

New release! 🚀🚀🚀

Bug Fixes

---

This PR was generated with Release Please. See documentation.

Good morning! I've noticed that knip does not check for dead code in backend properly. Created a fix here

New release! 🚀🚀🚀

Bug Fixes

---

This PR was generated with Release Please. See documentation.

Good morning 👋 @user I'd love to get your feedback on the proposed design for document pruning task here 🙂

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?

👋 Hi everyone!

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?

Good day, everyone!

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 👀

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:

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.

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 .

Hey peeps :fox_wave:, i have been looking into proper context compaction. Have some steps to think through and perhaps make multiple PRs as a step by step implementation to get going with context compaction in clear delivery steps.

Hey team!

While working on #4021, I realized we might need a way to move agent configurations between completely different instances (like from dev to prod or sharing with the community).

The basic idea is to export/import portable JSON configs.

I've created a GitHub issue outlining the basic idea - #4201. Let me know what you think!

New release! 🚀🚀🚀

Features

Bug Fixes

Hello archestra team ,sry to disturb I just wanted to check if there are any issues tagged with a bounty available for contribution