See what people built during the Apps HackathonExplore the gallery

#general

May 12May 13, 2026May 14Latest
A
New release! ๐Ÿš€๐Ÿš€๐Ÿš€
1.2.40 (2026-05-12)
Miscellaneous Chores
---
This PR was generated with Release Please. See documentation.
MJ
M Junaid Shaukat6:36 AMOpen in Slack
Just found a small bug that when we add the api key of llm, we have to write name of key, even though the field itself shows optional.
it can be good first issue
cc: @user
5 replies
A
New release! ๐Ÿš€๐Ÿš€๐Ÿš€
1.2.41 (2026-05-12)
Features
A
New release! ๐Ÿš€๐Ÿš€๐Ÿš€
1.2.42 (2026-05-12)
Bug Fixes
  • *dev:* stop vault-k8s release from claiming e2e-tests NodePorts (#4571) (953a696)
Miscellaneous Chores
JS
Joshua Silverstone3:50 PMOpen in Slack
Hi team โ€” working on bounty #4468 (Anthropic Workload Identity Federation). CLA is signed and my PR is ready, but my contributor-onboard PR archestra-ai/archestra#4590 got a merge conflict on EXTERNAL_CONTRIBUTORS.md right after it opened. The merge-external-contributors workflow only triggers on PR open, so it's stuck. Could a maintainer rebase or reopen it so I get added to the allowlist? Then I can submit the WIF PR (already committed and tested locally). Thanks!
3 replies
A
New release! ๐Ÿš€๐Ÿš€๐Ÿš€
1.2.43 (2026-05-12)
Bug Fixes
Miscellaneous Chores
  • add separate --check mode for the vault migrate script (#4588) (04323e0)
  • reduce shell noncritical startup requests (#4585) (fae7a67)
DA
Diego Aguirre4:33 PMOpen in Slack
Hi community, Diego Aguirre here, Nice to meet you all. Looking forward to connect with others interested in AI and contribute with the community. ๐Ÿ‘‹
6 replies
A
New release! ๐Ÿš€๐Ÿš€๐Ÿš€
1.2.44 (2026-05-12)
Bug Fixes
  • relax probe timeouts and make them configurable (#4595) (58568bc)
---
This PR was generated with Release Please. See documentation.
A
New release! ๐Ÿš€๐Ÿš€๐Ÿš€
1.2.45 (2026-05-12)
Bug Fixes
Performance Improvements
  • *logging:* async stdout in prod, gate pino-pretty to dev (#4602) (46b1756)
Miscellaneous Chores
PN
Phฦฐฦกng Nguyแป…n3:43 AMOpen in Slack
Hi Archestra community! ๐Ÿ‘‹
I'm Phuong, a developer interested in contributing to Archestra bounty issues. My GitHub username is @akamabu.
I tried to comment /attempt on a few bounty issues but got a validation error โ€” looks like my account needs to be allowed first.
I'm interested in starting with:
  • #4461 โ€” Cleanup interval / org-wide default user limits
  • #3012 โ€” Chat reload causing lost/duplicate messages
  • #4468 โ€” Anthropic Workload Identity Federation
Could someone from the team allow my GitHub account to interact with the repo?
Thanks!
1 reply
SU
Shafiq ur rehman4:18 AMOpen in Slack
Hi Archestra community,
I'm Shafiq Ur Rehman. Nice to meet you all. Iโ€™m a developer interested in contributing to Archestra bounty issues and collaborating with others working on AI-related projects.
My GitHub username is @im-shafiqurrehman.
I tried using the /attempt command on a few bounty issues but got a validation error, suggesting my account may need to be approved first.
Could someone from the team please grant me access so I can start contributing?
I'm interested in starting with:
  • #4468 โ€” Anthropic Workload Identity Federation
Thanks!
3 replies
MG
Myroslav Galavai8:01 AMOpen in Slack
Hey folks! I'm honestly stunned by the way you're figthing ai-slop! I'd love this to become an industry standard!
1 reply
AE
Hey, my name is Amr, and I would love to work on issue #4030 (Approval flow broken in Web UI). I'm a Full-Stack Engineer and I've already identified the state persistence issue on page refresh. Excited to contribute!
AE
Hi team, I'm Amr. I just put an /attempt on #3218 (Auto Sync Permissions). I'm planning to work on the ACL synchronization logic for Jira/Confluence. If there are existing design docs or internal context for the Baseconnector refactor, I'd love to take a look!"
1 reply
A
New release! ๐Ÿš€๐Ÿš€๐Ÿš€
1.2.46 (2026-05-13)
Bug Fixes
Performance Improvements
Miscellaneous Chores
A
New release! ๐Ÿš€๐Ÿš€๐Ÿš€
1.2.47 (2026-05-14)
Features
Bug Fixes
V
Hi everyone! ๐Ÿ‘‹
I left a proposal on #3796 about handling connector_sync cancellation before considering a broader pg-boss migration.
My read is that connector deletion needs DB-visible cancellation either way, because running sync handlers still need cooperative checkpoints before ingesting more data, enqueueing embeddings/continuations, or marking success.
Would appreciate a quick sanity check on whether this direction matches what you had in mind before I start implementing.
A
New release! ๐Ÿš€๐Ÿš€๐Ÿš€
1.2.48 (2026-05-14)
Features
  • *frontend:* enable version skew protection via deploymentId (#4629) (f6c00ad)
Bug Fixes
  • *auth:* don't downgrade existing member role via SSO default-role โ€ฆ (#4580) (3b02507)
  • *helm:* bound the postgres-wait init container loops (#4657) (03c9d88)
A
New release! ๐Ÿš€๐Ÿš€๐Ÿš€
1.2.49 (2026-05-14)
Bug Fixes
---
This PR was generated with Release Please. See documentation.
?
Hi Team! I just finished the bounty for issue #4468 (Anthropic WIF support).
I've implemented everything including tests and docs, but I'm locked out from opening a PR or commenting on
GitHub because I'm a new contributor.You can see my work here: https://github.com/akmalputraseptian-stack/archestra/tree/bounty-anthropic-wif
Can someone help me get this submitted? My GitHub username is akmalputraseptian-stack. Thanks

Read-only live mirror of Archestra.AI Slack

๐Ÿ‘‹Join the discussion withAI enthusiasts!