ZiyaZhang e72978ba98 fix(tool-goal): scope the wrap-up no-more-tools clause to the current run ...

The injected instruction persists as a durable user message, so an
unscoped 'Do not call any more tools.' stays in every later request's
history. Scope it: '...in this run; further work waits for the user's
next instruction.' A/B probes on deepseek-v4-pro show the scoped wording
is non-inferior in-turn (4/4 zero tool calls, closing quality unchanged)
and next-turn tool use is unaffected under both wordings; the scoped
form states the instruction's actual lifetime.

2026-08-02 07:29:18 -07:00

..

fixtures

fix(subagent): preserve published run failures

2026-08-02 12:51:09 +08:00

goal-snapshots

fix(tool-goal): scope the wrap-up no-more-tools clause to the current run

2026-08-02 07:29:18 -07:00

snapshots

test(snapshot): refresh Cordis steering API fixture

2026-08-02 17:53:07 +08:00

acp.e2e.ts

Merge remote-tracking branch 'origin/master' into codex/trim-redundant-comments

2026-07-25 13:36:21 +08:00

acp.snapshot.ts

feat(subagent): add explicit child reports

2026-08-02 12:51:10 +08:00

cleanup.e2e.ts

test: preserve ACP cleanup failures

2026-07-14 14:11:33 +08:00

cleanup.ts

test: preserve ACP cleanup failures

2026-07-14 14:11:33 +08:00

escalation.e2e.ts

refactor(acp): reduce bridge to automation protocol

2026-07-24 01:40:25 +08:00

fs-search.cordis.snapshot.yml

fix(fs-search): make glob sampling an explicit choice

2026-07-30 21:14:03 +08:00

fs-search.cordis.yml

fix(fs-search): make glob sampling an explicit choice

2026-07-30 21:14:03 +08:00

goal.snapshot.ts

fix(tool-goal): let the model deliver a wrap-up message after a goal-round complete/blocked

2026-08-02 05:58:45 -07:00

hooks.e2e.ts

Merge remote-tracking branch 'origin/master' into codex/trim-redundant-comments

2026-07-25 13:36:21 +08:00

lsp.cordis.snapshot.yml

fix(lsp): align operations and harden lifecycle

2026-07-21 13:29:40 +08:00

lsp.cordis.yml

fix(lsp): align operations and harden lifecycle

2026-07-21 13:29:40 +08:00