Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Sandboxing

未关闭
#330 12 条评论 4 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
clojure, docker, shell
领域
devtools, security

调研方向

No files, tests, or entry points are named. Start by reading the discussion and related issue #324; done would require a clear decision on whether ECA should support sandboxing and what approach to recommend.

由索引模型根据 Issue 内容生成。

描述

To upvote this issue, give it a thumbs up. See this list for the most upvoted issues.

Thinking more about #324, especially for shell commands, I think preventing all unreasonable commands isn't really possible without manual review. Sandboxing would be much better. Claude has /sandbox, and it looks like people are using all sorts of different ways for sandboxing opencode and other harnesses (using incus, bubblewrap, docker, etc.). Most of them seem significantly more painful to setup than something builtin.

I don't know that it actually makes sense to have something directly part of eca, though I am wondering if anyone has any recommended method to use with eca. Is anyone here doing some sort of sandboxing with eca?

主要语言
Clojure
星标
1k
派生
82
平均合并
1 天 14 小时
30 天内合并 PR
16

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

editor-code-assistant/eca 的其他 Issue

查看 editor-code-assistant/eca 的全部 Issue

相似的 Issue

更多 Clojure Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。