Sharing something that might help new contributors, I faced while setting up archestra👇

Large repos can get really slow (clone, fetch, etc.), especially as they grow over time (Well-Architected)

I wrote a guide on how to handle this better while contributing:

👉 https://medium.com/@oulkarshubhu/dont-let-large-git-repositories-slow-you-down-519ac1bc0fb2

Hope this helps someone getting started 🙌

New release! 🚀🚀🚀

Features

Bug Fixes

Miscellaneous Chores

New release! 🚀🚀🚀

Features

Bug Fixes

Hi everyone! I applied for the Software Engineer role and started going through the repo and I’d love to contribute. I noticed a lot of issues seem pre-scoped for candidates already in the pipeline – would you prefer I wait for a task through the process, or is it okay to pick something up independently?

Hi, I’m working on an issue approval flow for ChatOps, and I have a couple of questions:

1. When an approval request appears in a Slack thread, can only the user who initiated it approve or deny it, or can any user who has access to the bot do so?

2. If two users are talking to the bot in the same Slack thread and one of them receives an approval request, should a message from the second user interrupt the approval flow, or should it not?

Hi team! I'd like to discuss one idea, I don't know how much it is relevant for you now at all, but to me it looks like a pretty natural continuation of what you already have in guardrails.

It is about something like policy dry run / what-if for tool policies: so it would be possible to run tool call scenarios through current or proposed policies and see what would happen with them and for what reason.

I see two modes here:

1. synthetic scenarios - more for new clients, I don't know how your sales are organized, but potentially it could be useful there.

2. running on historical cases - for already existing clients, so before changing a policy they could see how it would affect their real scenarios.

It seems to me that in a light version this should fit pretty well into the current architecture.

If it's interesting, I'd be glad to discuss it more and take implementation on myself.

Hey, my name is Anmol-I'd love to work on issue https://github.com/archestra-ai/archestra/issues/3406 (Claude models failing through the Bedrock proxy with body/system/1 Invalid input). Mind if I pick it up?

New release! 🚀🚀🚀

Features

Bug Fixes

Miscellaneous Chores

Hey team!

I've had a few feature ideas that I think could really improve the experience for users. Wanted to check if they align with the current roadmap. If they look good, I'd be happy to open issues and take them on!

1. Agent Cloning (One-click duplication): Right now, if you want to fork an agent to test a new prompt or slightly different toolset, you have to recreate the whole config (tools, KBs, sub-agents, labels) from scratch. I’ve seen this in a few other products and it's a huge time-saver. It would be a pretty self-contained backend addition using the existing model associations.

2. Knowledge Base Search Feedback Loop: Right now, we can see sync stats and query volume, but we have no way to know if cited documents actually helped the user. Adding small 👍/👎 buttons to citations in chat would give us a direct signal on which docs are authoritative vs. which ones are just noise. This helps admins find content gaps (frequent 👎) and identify outdated docs without manually auditing thousands of files. In the long run, we can feed this data back into rrf.ts to automatically boost documents that users find consistently helpful. I think it adds a lot of value for anyone managing enterprise knowledge at scale.

What do you all think?

New release! 🚀🚀🚀

Features

Bug Fixes

Hey team 👋. I'm Sasha)

I’m interested in contributing to this issue: https://github.com/archestra-ai/archestra/issues/3838

Before I jump in, I wanted to ask - is there already a defined vision or some expectations for how this should be approached? Or is this more of an open-ended task where contributors are encouraged to propose their own direction/implementation?

Happy to align with any existing ideas, or draft a proposal if it’s still exploratory.

Can't we attempt the the issue with the tag Reserved for SE Interview?