E2B
e2b-dev/E2B
Secure sandboxes for agent-generated code execution. GitHub: e2b-dev/E2B (~13k stars).
GitHub repository
Overview
E2B (e2b-dev/E2B) is listed in LimeDock Directories as an AI agent resource. Secure sandboxes for agent-generated code execution. Group: memory-infra. Community size: ~13k GitHub stars. Repo (copy/paste): https://github.com/e2b-dev/E2B This page is a plain-English guide so searches for the GitHub project can land on how teams actually use it.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Agents are a starting point. LimeDock turns the workflow into production automation your SaaS team owns — not another prompt library.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Open the GitHub repository, then follow the README for your stack.
Official GitHub repository: https://github.com/e2b-dev/E2B GitHub path: e2b-dev/E2B
How to open it: 1. Copy: https://github.com/e2b-dev/E2B 2. Clone or follow the README for your OS/stack. 3. Start with the smallest example before production use.
How to use it
**Simple example** Agents write code that must run somewhere safer than your laptop.
1. Create an E2B account/project. 2. Run a hello sandbox. 3. Point your coding agent’s execute step at E2B.
Example prompts
- “Run Python in an E2B sandbox from our agent.”
- “E2B vs Daytona?”
- “Network restrictions we should enable.”
Use cases and examples
- Evaluate e2b-dev/E2B as an AI agent building block
- Pilot E2B on one staging workflow
- Compare against agents you already pay for
- Document a team playbook after the pilot
Prerequisites
- API access
- Agent integration
Tips
- Default deny network if possible.
- Time-limit sandboxes.