Yichen Jiang fdf9bddbf8 feat(agent-loop): make the parallel tool-call cap a user setting ...

The section is a strict subset of the plugin config: `agents` is consumed
once when the service starts, so a stored change there could only look like
it had an effect. The cap resolves through a getter over the settings source,
which the scheduler destructures at the start of each tool group, so a
committed change bounds the next group without disturbing the one in flight.
`resolveMaxParallelToolCalls` becomes the section validator, refusing a value
at the write instead of at that group.

The deferred-resume effect-shape assertion now allows the one plugin effect
the optional settings wiring adds at the fiber's own level; a resumed agent
joining it there is still the regression it pins.

2026-08-10 18:00:03 +08:00

..

agent.ts

refactor(agent-loop): tighten wake-latch comments

2026-08-08 19:42:42 +08:00

constants.ts

docs: tighten parallel tool-call prose

2026-07-18 14:59:26 +08:00

index.ts

feat(agent-loop): make the parallel tool-call cap a user setting

2026-08-10 18:00:03 +08:00

invariant.ts

refactor(session): route construction through Session.create

2026-08-05 11:56:14 +08:00

runtime-context.ts

Merge remote-tracking branch 'origin/worktree/context-source-cards' into worktree/context-forms-remaining

2026-08-06 11:49:03 +08:00

tool-calls.ts

docs: replace vague provenance prose with recorded facts

2026-08-09 15:35:02 +08:00