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.