Skip to content

0.55.0

Choose a tag to compare

@b10x-bot b10x-bot released this 02 Nov 18:26
· 119 commits to main since this release
00dc7fe

A spec runs one turn on a given task text and exits, a Command resource can run on a schedule with its task text declared in the resource, and a write Connectors refuses is never counted as sent.

Breaking

No breaking changes.

Changed

  • b10x-loom agent run --spec <FILE> --state <DIR> --input <FILE> runs one turn of a loom.agent/1 spec on the input's text, records it as agent serve records an item, performs at most the sends writes admits and exits: 0 answered, 4 no answer, 3 refused, 1 input refused.
  • LoomAgent spec.schedule (cron, timeZone, suspend, startingDeadlineSeconds) runs a Command resource as a batch/v1 CronJob, Forbid; a scheduled resource's name is at most 52 characters.
  • status.lastRun and the condition LastRunSucceeded report a scheduled resource's newest finished run; it stays Running.
  • spec.schedule.input (text or configMapKeyRef) makes each scheduled run b10x-loom agent run --input <file>.
  • loom.resource command ObserveScheduledRun, event LoomAgentLastRunObserved, view member last_run.
  • The chart's Role grants cronjobs (create, update, patch, get, list, watch, delete).
  • b10x-loom agent resume of a write Connectors classifies refused or not_attempted exits 5 with the refusal and counts no send, where it reported success.

Full entry: https://github.com/beyond10x/loom/blob/0.55.0/CHANGELOG.md#0550---2026-11-02