Repository navigation
0.55.0
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 aloom.agent/1spec on the input's text, records it asagent serverecords an item, performs at most the sendswritesadmits and exits: 0 answered, 4 no answer, 3 refused, 1 input refused.LoomAgentspec.schedule(cron,timeZone,suspend,startingDeadlineSeconds) runs aCommandresource as abatch/v1CronJob,Forbid; a scheduled resource's name is at most 52 characters.status.lastRunand the conditionLastRunSucceededreport a scheduled resource's newest finished run; it staysRunning.spec.schedule.input(textorconfigMapKeyRef) makes each scheduled runb10x-loom agent run --input <file>.loom.resourcecommandObserveScheduledRun, eventLoomAgentLastRunObserved, view memberlast_run.- The chart's Role grants
cronjobs(create, update, patch, get, list, watch, delete). b10x-loom agent resumeof a write Connectors classifiesrefusedornot_attemptedexits 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