Archestra Apps HackathonJoin now

#general

Apr 19April 20, 2026Apr 21Latest
OG
Omkar Geedh8:38 AMOpen in Slack
hello guys I am setting up the project in local
when I run command pnpm install in terminal it works
but in Tilt it doesnt
2 replies
SO
Shubham Oulkar7:07 AMOpen in Slack
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:
Hope this helps someone getting started 🙌
🙌3
A
New release! 🚀🚀🚀
1.2.19 (2026-04-20)
Features
Bug Fixes
  • *chat:* add copy button to code blocks in conversation artifacts (#3868) (41c1612)
  • enforce SSO allowed email domains (#3976) (22d2743)
  • preserve native Slack markdown replies (#3936) (80010ae)
  • *sharepoint:* recursive subfolder traversal via folder-traversal utility (#3960) (081d0b2)
Miscellaneous Chores
  • switch to pnpm in docker image for mcp base image (#3657) (2ef39dd)
A
New release! 🚀🚀🚀
1.2.20 (2026-04-20)
Features
  • *openapi:* name UserConfigField + UserConfigFieldDefault schemas (#3969) (759f667)
Bug Fixes
TK
Tigran Kostandyan9:04 PMOpen in Slack
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?
11 replies
IK
Ilya Korovin10:19 PMOpen in Slack
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?
5 replies
VL
Vadim Larin2:57 PMOpen in Slack
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.
9 replies

Read-only live mirror of Archestra.AI Slack

👋Join the discussion withAI enthusiasts!