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

fix(context): refresh workspace state after tool-driven file changes

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
ai, tooling

调研方向

Trace how MiniAgent constructs WorkspaceContext and the generated prompt prefix, then follow the write_file, patch_file, and run_shell operations that can mutate the workspace. Check how later model turns obtain git status, branch state, commits, documentation, and repository instructions. Done means a mutation is visible on the next model turn, static prompt content is not needlessly rebuilt, and regression tests cover the sequence.

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

描述

Problem

"WorkspaceContext" and the generated prompt prefix are constructed once when "MiniAgent" starts. However, tools such as "write_file", "patch_file", and "run_shell" can mutate the workspace during the same session.

As a result, subsequent model turns can receive stale information about:

  • "git status"
  • current branch state
  • recent commits
  • project documentation
  • repository-level instructions

For example, the initial workspace may be clean, but after "write_file" creates a file, the prompt can still report the original clean status.

Expected behavior

After workspace-mutating operations, the agent should either:

  1. refresh the affected workspace context, or
  2. explicitly separate immutable context from dynamically refreshed state.

The refresh should avoid rebuilding unnecessary static prompt content on every turn.

Acceptance criteria

  • "git status" reflects changes made during the current session.
  • Changes made through "write_file", "patch_file", and shell commands are visible to later model turns.
  • Project documentation changes are reflected when appropriate.
  • Existing prompt/cache behavior is preserved as much as possible.
  • Add regression tests covering a workspace mutation followed by another model turn.
主要语言
Python
星标
1.2k
派生
218
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

rasbt/mini-coding-agent 的其他 Issue

查看 rasbt/mini-coding-agent 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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