#general
👋 Hi everyone! Just got here, willing to set some elbow grease on the issues and hit the ground running! Thank you for this opportunity and glad to be part of this 🙂
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?
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>
Read-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!