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

Protected personality files and secret redaction in logs

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
backend, security

调研方向

Start with how skill changes already become pending diffs, then check whether the same approval path can cover writes from sentient/memory/workspace.py and the memory and files tools. Separately, find the logging setup in sentient/app.py and the keychain access in sentient/secrets.py to see where a redaction filter would attach. Done means an agent write to a protected file asks first, a known secret value never appears in logs or tool errors, and tests cover both. The issue leaves the approval mechanism unspecified, so confirm the design with a maintainer before coding.

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

描述

area: engine area: memory enhancement help wanted priority: P2 size: S

An injected instruction that rewrites SOUL.md or a skill persists forever. Secrets that leak into tool errors and logs end up in bug reports. Hermes v0.21.0 shipped protection for both.

Idea:

  • agent writes to SOUL.md, USER.md, MEMORY.md, skills and config always require approval
  • secrets (keychain values, tokens, keys) are redacted from tool errors, logs and checkpoints

Status in Sentient today: Partial. Skill changes already land as pending diffs, and secrets live in the keychain (sentient/secrets.py). Workspace file writes and log redaction are not covered.

Where: sentient/memory/workspace.py, sentient/tools/builtin/memory_tool.py, sentient/tools/builtin/files_tool.py, a logging filter set up in sentient/app.py, and sentient/secrets.py.

Done when:

  • an agent write to a protected file asks first
  • a known secret value never appears in logs or tool errors
  • tests cover both

Sources:

Roadmap ID: SAFE-16 · Priority: P2 · Size: S

主要语言
Python
星标
702
派生
113
平均合并
5 小时 8 分钟
30 天内合并 PR
171

环境准备

从这里开始

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

existence-master/Sentient 的其他 Issue

查看 existence-master/Sentient 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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