Charles retweeted
Introducing AIO Sandbox, All-in-One Sandbox Environment for AI Agents.
Unchecked AI autonomy is a ticking time bomb; it’s time to pull the plug on full system unfettered access. We can no longer afford to give AI agents the 'keys to the kingdom' without oversight. The 'wild west' of AI agents running with total system control is officially over.
AIO Sandbox is an open-source project designed to solve these problems. It is everything your agent needs, out of the box. No more juggling multiple services. AIO Sandbox ships a complete, pre-wired environment in a single Docker container.
The AIO (All-in-One) Sandbox is a containerized environment designed for both human developers and AI agents. Its architecture is built around a "Batteries-Included" philosophy, providing a full Linux desktop-like environment inside a single Docker container.
Unified Environment: One Docker container with shared filesystem. Files downloaded in the browser are instantly accessible in Terminal and VSCode.
Out of the Box: Built‑in VNC browser, VS Code, Jupyter, file manager, and terminal—accessible directly via API/SDK.
Agent-Ready: Pre-configured MCP Server with Browser, File, Terminal, Markdown, Ready-to-use for AI agents.
Developer Friendly: Cloud-based VSCode with persistent terminals, intelligent port forwarding, and instant frontend/backend previews.
Secure Execution: Isolated Python and Node.js sandboxes. Safe code execution without system risks.
Production Ready: Enterprise-grade Docker deployment. Lightweight, scalable.
Calling all AI agent developers! How are you securing your builds? Let’s try running your agent in AIO Sandbox and compare notes.
AIO Sandbox is open-sourced under the Apache License 2.0. Contributions welcome.
GitHub: github.com/agent-infra/sandb…
Official website: sandbox.agent-infra.com/
#OpenSource #AIAgent #Docker
7x24 用起来!
Replying to @OpenAIDevs
Selected maintainers get:
• API credits for maintainer workflows
• 6 months of ChatGPT Pro, which includes Codex
• Conditional access to Codex Security
Applications are reviewed on a rolling basis.
openai.com/form/codex-for-os…
组里开始招实习生了,有兴趣可以私信我简历或者直接投递!
- base:杭州/上海/北京
- job.toutiao.com/s/L5pVbp5xqF…
2
7
1,316
当前的 git worktree 拖慢了 AI Coding 多需求的研发效率!
预感今年 Git 会大改,以适应 Vibe Coding。以前当 PM 搭档程序员,他们给我讲 Git,压根就没提到 Worktree。
我在刚上手 Vibe Coding 时候遵循古法:要做新功能是吧?那新窗口开新分支。三个功能那就三个分支并行开发。
Codex 写着写着就给我警告说代码非本窗口改动,我一脸疑惑?我明明给每个窗口都开了单独的分支啊!
过往手敲代码的物理特性,Git 压根就没想过有一天我们可以在一台机器上开启任意数量的窗口并行开发,Worktree 这种为边缘场景设计的功能一跃成为开发标配,从无人问津到聚光灯下,它显然没适应好:
• 腐败和调试问题:Worktree 容易导致 Git 仓库、包依赖或构建过程腐败,调试这些问题往往抵消了并行开发的效率提升。例如,在并行处理时,环境不稳定会引发频繁的修复需求。
• 未跟踪文件不复制:Worktree 不会自动拉取未跟踪的文件(如 .env 或 node_modules),这会中断工作流程,需要手动处理,增加了认知负担和时间成本。如果不并行实现多个功能,这种痛点尤其不值得。
• UX 和管理复杂:Worktree 被视为低级 Hack,需要手动管理多个命名空间和目录,与 Git 的核心模型冲突。整体用户体验糟糕,容易出错,尤其在多会话时 AI Agent 会混淆任务,导致意外重置或切换。
• 隔离不足:对于需要端口监听或完整隔离的场景,Worktree 不够可靠。有些开发者建议用 Docker 容器替代,以避免端口冲突或环境污染。
• 合并和 AI 处理问题:AI Agent 有时无法正确在新的 Worktree 上启动工作,或处理诡异的合并冲突,导致整体体验糟糕。特别是在工具集成时(如 Windsurf),可能会默认回根目录,无法生成 Commit。
Vibe Coding 到现在,我对 Worktree 的评价就是:还能咋地,你只能用它了。
2
508



















