MiniMax-AI / MiniMax-AI/minimax-code
[Bug]: 压缩上下文后的日志位置不正确
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 141
- Avg merge
- 2h 45m
- Merged PRs (30d)
- 46
Description
Version / 版本号
3.0.42-inside.10.10
Platform / 平台
macOS
OS version / 系统版本
macOS 26.5.1
Issue area / 问题类型
Model output quality
Upload ID / 日志上传 ID
409056127828394
What happened? / 问题描述
正常对话的输出，最下方是文件改动的位置，也就是那些文件发生了改动。此时，如果我选择手动压缩上下文，使用命令“总结”。就会进行上下文压缩。但是压缩之后，本来应该在日志的最下方拉一条横线，显示上下文压缩。但是这个横线却拉在了文件改动的上方。变成了。
-----压缩上下文----
文件改动
这会看起来是压缩上下文后又进行了文件改动，实际上文件改动是压缩上下文之前的。
Steps to reproduce / 复现步骤
- 修改文件
- 压缩上下文
Expected behavior / 预期行为
压缩上下文显示在最下方
Actual behavior / 实际行为
压缩上下文显示在文件改动上方。
Logs or crash report / 日志或崩溃信息
Screenshots / 截图
No response
Before submitting / 提交前确认
- I have searched existing issues.
- I am using the latest version available to me.
- I have removed sensitive information from logs/screenshots.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is identified in the report. Reproduce the sequence in the terminal coding agent by modifying a file, then manually compressing context with “总结”; trace the log rendering and context-compression entry points to determine why the compression marker appears above the file-change entry. Done means the marker consistently appears below earlier file changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100