Why: the direct chat path needs one loop for deliverable checks, reminders, and truncated replies, while squad keeps today's behavior when the new fields stay unset.
Evidence: go test ./... passed.
Merge this before Backend and Agent-Squad.
Refs: feature/agent-harness-p1
Why: the direct chat path needs one loop for deliverable checks, reminders, and truncated replies, while squad keeps today's behavior when the new fields stay unset.
Evidence: go test ./... passed.
Merge this before Backend and Agent-Squad.
Refs: feature/agent-harness-p1
Why: the direct chat path needs one shared loop for deliverable checks, tool pairing, reminders, and truncated replies, while squad callers keep today's behavior when the new fields stay unset.
Evidence: go test ./... in agent-native passed, including Stop cap, BeforeTool pairing, reminders absent from the session, repeat-guard cap, length continuation, and zero-value loop tests.
Impact: runtime.Config and llm.Event grow optional fields; AgentSession.Prompt copies them through. Squad sessions that leave them zero are unchanged.
Refs: feature/agent-harness-p1
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the direct-path adapter accounts usage per turn, including runs that stop on a budget error before the final usage event.
Evidence: go test ./runtime/ ./runtime/llm/ after the field was added.
Impact: message_end and usage events carry TotalTokens. Callers that ignore the new field are unchanged.
Refs: feature/agent-harness-p1
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the direct chat path still executes model-emitted calls that are not in the profile allow-list, while squad keeps the unknown-tool error when the fallback is unset.
Evidence: go test ./runtime/ passed, including TestLoopUnknownToolFallsThrough and the existing unknown-tool cases.
Impact: Config.UnknownTool is optional. Nil preserves today's registry error.
Refs: feature/agent-harness-p1
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
merged commit 1a999c344d into main2026-10-01 13:41:33 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: the direct chat path needs one loop for deliverable checks, reminders, and truncated replies, while squad keeps today's behavior when the new fields stay unset.
Evidence: go test ./... passed.
Merge this before Backend and Agent-Squad.
Refs: feature/agent-harness-p1