StackJack 0.1.0.9588+bbf262a

This release adds richer ticket comments for NinjaOne. It also makes expired invitations clearer, gives better guidance on the Anthropic credentials card, restores automations paused by a cancelled data deletion request, and fixes issues with NinjaOne connections and automation reasoning levels.

New features

• Richer NinjaOne ticket comments. The tool for adding a comment to a NinjaOne ticket now accepts three optional extras:
• an HTML-formatted body alongside the plain-text comment
• time tracked, in seconds
• up to five file attachments, each supplied inline or from a public HTTPS link, up to 25 MB in total

If any attachment can't be retrieved, nothing is posted. Existing comment calls that don't use these options work exactly as before.

Improvements

• Paused automations come back when you cancel a deletion request. If a data deletion request switched some of your automations off while it waited, cancelling that request now switches those automations back on and restores their schedules. The account owner receives an email when this happens.
• Region moves carry over recorded run data. Moving your organization to another region now also copies recorded automation run parts and scenario fixtures. After the move is verified, the copy in the original region is removed.

Bug fixes

• NinjaOne technician-only refusals no longer disturb the connection. Some NinjaOne requests require a technician-authorized connection. When NinjaOne refused one of these, StackJack used to force a token refresh and retry, which could use up a single-use refresh token without helping. That error is now returned straight away, and the connection is left as it was. All other authorization errors still refresh and retry as before.
• Re-sync corrects a stale reasoning level. In some cases an automation's reasoning level was reset to the model default in StackJack, but the remote agent kept running at the previous level. Running Re-sync on that automation now brings the remote agent back in line with the model default. If the provider rejects the default level that StackJack sends, the save now retries without a level instead of failing.
• Cancelling a data deletion request no longer fails when other activity is happening at the same time. The cancellation now goes through. Any deletions that had not yet been withdrawn finish as part of the original request.

UI & UX changes

• Clear notice for expired or withdrawn invitations. If you sign in with an invitation that expired or was withdrawn, you now see a notice saying so. It asks you to contact an owner or administrator of that organization for a new invitation. Previously you saw a generic no-access message telling you to sign in again.
• Expired invites are shown as Expired on the Team page. The Team page now labels an expired invite as Expired and explains why. The Resend button is disabled for it. If an invite expired, was revoked or was accepted after you loaded the page, clicking Resend is refused with a message instead of sending an email that wouldn't work.
• Anthropic credentials card now gives a next step. Accounts that can't add their own Anthropic key and don't have one previously saw an empty card.
• Owners are now told where to buy an Agent Runner plan, and to check out with the organization's sign-up email and company name so the purchase matches the organization.
• Members are told that the owner buys the plan and sets the key.
• If the Agent Runner plan has a payment problem, the card points to the Billing page instead.
• Clearer region-move checklist wording. The self-service region-move checklist uses plainer item names: "No automation removal is in progress" and "No automations are waiting to be switched back on".

StackJack 0.1.0.9489+6c68ee0

This release adds run transcript deletion. Owners and administrators can delete the transcript of a single run, several runs, or every run of an automation, and can set an automation to delete its transcripts automatically. Deleting an automation or your organization now also deletes the related transcripts.

New features

• Delete a run's transcript. On a finished run's page, owners and administrators see a Delete transcript button. A confirmation step explains what is removed and what stays. The transcript is deleted from StackJack and from our AI provider.
• Delete transcripts for several runs at once. On an automation's run list, owners and administrators can tick finished runs and choose Delete transcripts (n). A preview shows the counts first. To go ahead, you type a confirmation phrase.
• Delete all transcripts for an automation. A new transcript card on the automation page has a Delete all transcripts action. It uses the same preview and typed-confirmation flow.
• Automatic transcript deletion per automation. The same card has a switch that deletes each run's transcript automatically after the run finishes.
• Only owners and administrators can change it. Everyone else sees the current setting as read-only.
• The switch is also available in the advanced builder's "Guardrails and consent" card and in the chat builder.
• Changing only this setting does not create a new automation version.
• A staging copy inherits the setting. Deploying a staging copy over the live automation does not change the live setting.
• New platform tool for agents. stackjack_delete_run_transcripts lets an owner or administrator delete transcripts through an AI client.
• It previews first and runs only with the exact confirmation phrase it returns.
• It cannot be used from an automation's own connection or from a connection that does not act for a signed-in person.
• The builder tools (stackjack_draft_agent, stackjack_update_agent_draft, stackjack_set_agent_definition) accept an optional autoDeleteTranscripts setting, with the same owner and administrator rule.
• stackjack_inspect_agent has a new transcript_deletions view.

Improvements

• Deletion status on the run page. A run shows whether its transcript is scheduled for deletion, deleted, or partly deleted.
• Partly deleted means the copy in StackJack is gone but the delete at our AI provider did not finish. Owners and administrators get a Try again option in that case.
• Once a transcript is deleted, the run's summary and payload panes read "Deleted with the transcript," and no transcript events are shown.
• A scheduled transcript stays readable for now. A transcript scheduled for deletion can still be read until the run's billing is final.
• Agent tools report deleted transcripts.
• stackjack_get_run_transcript returns a clear transcript_deleted result with the deletion time.
• stackjack_get_agent_run includes the run's transcript deletion status. Its next-step guidance no longer points to a transcript that has been deleted.
• Runs with deleted transcripts cannot be re-run or reused. Re-running such a run is refused with a plain explanation that its input was deleted with the transcript. Saving it as an evaluation scenario is also refused.
• Organization deletion removes more data. It now deletes run transcripts, recorded test files and large tool results.
• Your automations are switched off while transcript deletion finishes, and the confirmation step tells you so.
• Delete confirmations explain transcript deletion. The confirmations for deleting an automation, discarding a staged automation, and the stackjack_delete_agent tool now state that the related transcripts are deleted.

Breaking changes

• Deleting an automation now deletes its runs' transcripts, both from StackJack and from our AI provider. Previously, transcripts were kept after an automation was deleted. If you need a transcript, review or export it before you delete the automation.

StackJack 0.1.0.9384+c47af81

This release fixes NinjaOne ticket comments and tightens NinjaOne ticket creation and updates. It adds Claude Sonnet 5.5 to the agent builder, checks reasoning effort against each model, and reports refused or budget-limited runs correctly. It also fixes sign-in from tabs left idle and intermittent errors on the Connectors page.

New features

• Claude Sonnet 5.5 is now available when building agents. It supports all five reasoning effort levels and defaults to high.

Improvements

• The agent builder and slot editor now show only the reasoning effort levels the selected model supports.
• If you pick an effort level that the selected model doesn't support, the save is refused with a message naming the model. Previously the save could succeed and the agent would fail later.
• If an agent carries over an unsupported effort level from an earlier configuration, template, or copy, that level is reset to the model's default instead of causing a failure.
• When a tool call is missing a required parameter, the error returned to the agent now includes that parameter's description. This helps the agent correct the call on its next attempt.
• Some NinjaOne actions, such as adding a ticket comment or creating a ticket, require a technician connection that uses Authorization Code sign-in. When these actions are attempted over a Client Credentials connection, the agent now gets clear guidance:
• It is told that a technician connection is needed.
• It is told that nothing was rejected.
• The attempt is no longer treated as a tool failure.
• The NinjaOne update-ticket tool is now marked as destructive, because it replaces the whole ticket. Its description also explains how to send a valid full ticket, including which fields are read-only.

Bug fixes

• Adding a comment to a NinjaOne ticket now works. Previously the request was rejected by NinjaOne.
• Agent runs that the model refuses, or that stop because they reached their budget, now end as Failed with a plain-language reason. Previously these runs were recorded as Completed and sent no failure email. The reason appears in the run's error message, in live chat, and in the saved transcript.
• Signing in from a tab left idle for a while now works on the first click.
• A tab whose session expired while unattended now shows a signed-out page instead of starting a sign-in that nobody completes.
• Fixed intermittent errors when loading or working on the Connectors page.

Breaking changes

• NinjaOne add-comment tool:
• You must now say explicitly whether a comment is public or private. There is no default.
• The comment type option is ignored.
• NinjaOne create-ticket tool:
• It now requires an organization, a ticket form, and an explicit public or private setting.
• The Critical priority value is no longer offered.