Skip to content

fix(core-agent): keep near-duplicate detection warn-only - #28

Open
CloudTianTian wants to merge 1 commit into
Orkas-AI:mainfrom
CloudTianTian:fix/near-duplicate-warn-only
Open

fix(core-agent): keep near-duplicate detection warn-only#28
CloudTianTian wants to merge 1 commit into
Orkas-AI:mainfrom
CloudTianTian:fix/near-duplicate-warn-only

Conversation

@CloudTianTian

Copy link
Copy Markdown
Contributor

Summary

  • keep normalized near-duplicate tool-call detection as a one-time warning
  • avoid terminating valid work solely because volatile request ids or timestamps were ignored by the fuzzy signature
  • retain hard stops for byte-identical repeats, the independent no-progress governor, and the configured tool-round limit

Testing

  • node scripts/run-tests.mjs run src/core-agent/test/agent-runner.test.ts src/core-agent/test/near-dup-loop.test.ts — 113 passed
  • node scripts/run-tests.mjs run src/core-agent/test — 32 files / 678 tests passed
  • npm run typecheck — passed
  • git diff --check and removed-symbol residue check — passed

The repository-wide npm test baseline is not clean in this environment: unmodified origin/main reproduces an EACCES failure for /Users/userWorkSpace in the video script fixture and a local OfficeCLI binary hash mismatch. Neither path is touched here.

Normalized tool-call matching drops volatile tracking fields and can therefore produce false positives. Keep its one-time progress nudge, but reserve hard stops for byte-identical repeats and the independent no-progress and tool-round limits.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant