Skip to content

v0.13.0: per-tool time limit

Choose a tag to compare

View all tags
@eadwinCode eadwinCode released this 03 Nov 15:45
· 13 commits to main since this release
v0.13.0
eab15e1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A time limit per tool, in both runtimes: one slow tool can get more time while StepTimeout stays short for every other step. Go module github.com/eadwinCode/agentic-kit/packages/go-agentenkit@v0.13.0, npm agentenkit@0.13.0 and use-agentenkit@0.13.0.

No breaking changes.

New: a tool's own time limit (#42)

Go: Tool.Timeout, or agentenkit.WithToolTimeout(t, 30*time.Minute). TS: withToolTimeout(tool, ms), which returns a copy of the tool.

  • While a call runs, its step has at least that long, even when StepTimeout (TS: stepTimeoutMs) is shorter. Once the call returns, the step is back to StepTimeout, counted from then.
  • A call past its own limit ends the step like a step past StepTimeout: the same step N ran longer than … error, naming the limit that ran out, and the same retry.
  • Other tools keep the step limit. A tool in the same step as a slow one shares its longer time.
  • The tool must stop when its ctx is done (TS: when its abortSignal fires), as with the step limit.
  • It does not lift SegmentTimeout, or a queue's own job limit, such as Flow's step time. Keep those longer than your slowest tool.

New: a subagent's own time limit (#42)

Go: SubagentsConfig.Timeout. TS: subagents.timeoutMs. A child's whole run happens inside one spawnSubagent call, so inside one step of the parent. This gives that call its own limit, so a child, and a slow tool inside it, can outlast the parent's StepTimeout.

Changed

  • Go: a step whose tools include a timed tool now has a context with no Deadline(), because a deadline cannot be moved later. When time runs out, ctx.Err() is Canceled and context.Cause says DeadlineExceeded. The timed call itself gets a real deadline. Steps with no timed tool are as before.
  • Go: a timed-out step keeps the provider's own error text, for example context deadline exceeded (stream read: context canceled). TS keeps it as the error's cause.
  • TS: a step whose time runs out just as the model finishes now fails and retries, as in Go.

See Tools that need more time and Subagents: Limits.

Assets 2
Loading