Skip to content

fix(recall): relax mandatory trigger to recommended with skip conditions#158

Merged
jeff-r2026 merged 1 commit into
Tencent:mainfrom
m0Nst3r873:worktree-recall-trigger-relax
Jul 7, 2026
Merged

fix(recall): relax mandatory trigger to recommended with skip conditions#158
jeff-r2026 merged 1 commit into
Tencent:mainfrom
m0Nst3r873:worktree-recall-trigger-relax

Conversation

@m0Nst3r873

@m0Nst3r873 m0Nst3r873 commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Change recall rule from MUST to SHOULD with explicit skip conditions
  • Add 3 skip scenarios: user already provided context, local files have the answer, trivial/local changes
  • Soften TodoWrite hint from "confirm you have already invoked" to "consider invoking if applicable"
  • Update teamai-recall agent description to match the new guidance

Motivation

The unconditional MUST language caused unnecessary teamai-recall invocations even when:

  1. The user explicitly says "the answer is in this file" or provides full context
  2. The task is a simple bug fix in the current file (no team knowledge needed)
  3. The change is trivial (typo, parameter tweak)

This wasted tokens and slowed down responses without adding value.

Test plan

  • npx tsc --noEmit passes
  • All 1672 unit tests pass (npx vitest run)
  • npm run build succeeds
  • After teamai pull, verify .claude/rules/teamai-recall.md contains "SHOULD" and skip conditions

🤖 Generated with Claude Code

The recall rule and TodoWrite hint used MUST/强制 language that forced
knowledge base search even when the user already provided context, the
answer was in local files, or the change was trivial — wasting tokens.

Change to SHOULD with three explicit skip conditions so the AI can
exercise judgment on when recall adds value.
@m0Nst3r873 m0Nst3r873 force-pushed the worktree-recall-trigger-relax branch from e2888f5 to 5aa1aa5 Compare July 7, 2026 03:04
@jeff-r2026 jeff-r2026 merged commit f1a9d89 into Tencent:main Jul 7, 2026
7 checks passed
@jeff-r2026 jeff-r2026 mentioned this pull request Jul 7, 2026
2 tasks
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.

2 participants