Repository navigation
[Agent Backend] E2B connection Missing worpskace-isolation sandbox configuration in UI #41723
Closed as not planned
Description
Self Checks
- I have read the Contributing Guide and Language Policy.
- I have searched for existing issues search for existing issues, including closed ones.
- I confirm that I am using English to submit this report, otherwise it will be closed.
- Please do not modify this template :) and fill in all the required fields.
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Currently E2B Configuration can only setup globally by environment at system start up. This can no serve the case where each workpace should its individual
agent-backend. Neither it does not cover the case ApiKey is used to auth template access.
2. Additional context or comments
Support E2B connection Configuration within WebUI, same as LLM-Provider.
Mainly E2B_API_KEY, E2B_API_URL, E2B_DOMAIN. TemplateId should be opt-in，since apply build-draft always create new snapshot.
3. Can you help us with this feature?
- I am interested in contributing to this feature.
Activity
modelpath-dev commentedon Sep 4, 2026
I'll work on this. Could you assign it to me?
I'll look at the current code, add a focused test, and send a small PR.
modelpath-dev commentedon Sep 6, 2026
I'll start by reviewing the existing configuration setup. Then I'll work on adding the E2B connection configuration to the WebUI. I'll keep you updated on my progress.
modelpath-dev commentedon Sep 8, 2026
I've started reviewing the current configuration setup. I'll begin implementing the E2B connection configuration in the WebUI soon. I'll update you as I make progress.
github-actions commentedon Oct 13, 2026
Closed due to inactivity. If you have any questions, you can reopen it.