Skip to main content

StackJack 0.1.0.10070+672162e

StackJack 0.1.0.10070+672162e

This release adds "Split big jobs across parallel agents," a new automation setting that lets one run hand large tasks to several agents working at the same time. Run pages and the live view now show the parallel agents a run started and how its work is progressing.

New features

  • Split big jobs across parallel agents. A new setting in the automation builder's Guardrails section lets an automation split large tasks across several agents that work in parallel within a single run.
  • It requires your organization's own Anthropic key. It can't be combined with live approval or with Azure Foundry.
  • Each run gets a hard spending limit on your key, taken from the automation's Max credits / run value. A run that reaches the limit ends with a clear per-run-limit message.
  • Max runtime and the Stop button still stop every agent a run started.
  • If the setting is on and the automation can reach a tool that changes data, the builder shows a warning, because parallel agents could make the same change twice. The warning doesn't block saving.
  • If turning the setting on would make the automation's instructions too long, the save is refused with a plain explanation on the form. Previously, that could lead to a failed automation.
  • Chat builder and agent-driven building. The chat builder can turn the setting on or off and includes it in its summary. The automation-building tools available to AI agents can also set and read the setting, and return the same data-changing-tool warning.

UI & UX changes

  • Parallel agents panel on the run page. For automations that use the new setting, the run page lists every agent a run started, grouped by parallel job. This includes agents that have finished. You can open any one agent's own transcript.
  • Live view and transcripts show parallel work. A run's parallel jobs appear with their name, phases and progress. A run is no longer shown as "Run completed" while parallel work is still going. If you open the live view partway through a run, it first shows the parallel work already in progress, then continues live.
  • Builder preview. The builder's preview rail shows whether the setting is On or Off. Changing only this setting now triggers the unsaved-changes prompt.
  • Templates and staging copies. The setting isn't included in automation templates, so installing a template always leaves it off. Staging copies carry the setting, and deploying a staging copy that has it off turns it off in production.

Known issues

  • For an automation using parallel agents, pressing Stop can take up to about 2 minutes to fully stop all agents.
NewImprovedFeature