#general

May 24May 25, 2026May 26Latest
H
Hi @user I noticed you self-assigned #4429. Just wanted to let you know that I already implemented the automatic pod restart fix with full Vitest coverage. I've just synced it with the latest main branch and all 586 tests are passing green. Would you like me to submit the Pull Request for your review?
5 replies
EF
Elina Fedosova8:59 AMOpen in Slack
Hi team, my name is Elina, and I’m currently going through stage 3 of the interview process. Happy to meet you all! 🙂
I’m planning to work on issue #3859, hopefully it gets assigned to me soon. In a meantime, I’d like to brainstorm a bit about the overall approach and possible designs.
I reviewed all the existing PRs and comments under the issue, and from what I understand, the main idea is not exactly to add JSON support specifically for the Arguments field, but rather to allow describing the entire server configuration as JSON, similar to how many MCP catalogs handle it. For example:
  "mcpServers": {
    "playwright": {
      "type": "stdio",
      "command": "npx",
      "timeout": 30,
      "args": [
        "-y",
        "@playwright/mcp@latest"
      ],
      "disabled": false
    }
  }
}```
So I’m not planning to change anything inside the existing Arguments field itself, but instead add a separate tab for editing/viewing the JSON configuration.

I also asked Claude to generate a rough design mockup. Does this align with the desired behavior or am I missing something? Thank you!

<@U0975SLALTT> <@U0975QYCNRF>
3 replies
AA
Archestra App1:00 PMOpen in Slack
Community call is tomorrow! See you!
Propose your agenda in 🧵
7 replies
PM
Peaceful mind8:42 AMOpen in Slack
Hey, I've prepared a fix for #5033 (embedding error details on Knowledge/Connectors file upload) — I see it's assigned to @BeInLife and @user. Is this issue still available or is someone already working on it?
4 replies
EK
Hey, regarding the same issue as above:
What do you think about adding an alert if "[Embedder] No embedding API key configured, skipping" is met? This way we'll clearly describe why all the docs in "Pending" state ?
7 replies
SZ
Serge Zakharov4:52 PMOpen in Slack
Hi @user I was sketching over the evening Archestra as a thin policy lens over public chats, not only Slack/Teams, then found https://github.com/archestra-ai/archestra/issues/4146 - would like to pick it up if it's still relevant
Shipped a pretty similar Telegram bot stack in my project over the past few months - webhook + secret token + callback_data routing + state-in-cache for multi-step flows along with py-telegram-bot. I could share the adapted spec for this task before implementation if needed

Read-only live mirror of Archestra.AI Slack

👋Join the discussion withAI enthusiasts!