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.