v0.1.1 - End-to-End Batch Tracking, Ollama Fixes, and Agent Capability Updates #6
Badoot
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Added
batch_idcorrelation is now surfaced end-to-end — onCommandExecutionResult, approval metadata, and conversation message metadata — so agents and the dashboard can tie per-operator events and follow-up actions back to a single batched approval.Changed
command_validation.max_batch_concurrencyis now bounded (1–64) at the model layer, preventing misconfigurations that could fan out to an unbounded number of operators.target_operator) and batch (target_operators) targeting options.g8eddocs updated to describe parallel batch fan-out with bounded concurrency and sharedbatch_idcorrelation.Fixed
num_ctxconfiguration, error handling, and thinking parameter handling. Improved context window handling from Ollama responses.This discussion was created from the release v0.1.1 - End-to-End Batch Tracking, Ollama Fixes, and Agent Capability Updates.
Beta Was this translation helpful? Give feedback.
All reactions