StackJack 0.1.0.7678+12b8896

This release adds Avanan SmartAPI as a second sign-in method and gives owners and administrators control over members' personal sign-ins. It also makes the automation builder assistant more reliable, stops capped automation runs immediately, and fixes several connector-configuration and team-invite problems.

New features

• Avanan SmartAPI sign-in. When you configure an Avanan connection, you can now choose between Infinity Portal and Avanan SmartAPI. SmartAPI mode has its own region selection and credential fields. StackJack checks the SmartAPI credentials when you save and does not store them if the check fails.
• SmartAPI sign-in for agent credentials. The agent credential form offers the same Avanan sign-in methods, regions, and SmartAPI fields as the connector card. Both apply the same rules when saving.
• Avanan MSP tools use SmartAPI credentials. The Avanan MSP tools now authenticate with SmartAPI credentials, whichever sign-in mode the connection uses. The setup guide lists the six supported SmartAPI regions.
• Remove a member's personal sign-in. Owners and administrators can remove a member's personal sign-in from the Team page.

Improvements

• Clearer Avanan errors. When a SmartAPI sign-in is refused, the error now gives SmartAPI-specific guidance instead of pointing you to the Infinity Portal key.
• Avanan outages are no longer reported as bad credentials. Rate limiting and Avanan service outages are now treated as temporary. They no longer count toward disabling the connection.
• Automation caps stop runs immediately. When a run reaches its credit cap or maximum runtime, it now stops at once and its session is shut down. Previously, the agent was asked to wrap up and summarize first.
• More reliable automation builder assistant:
• Each turn has much more room to respond, so its proposed configuration is less likely to be cut off.
• Slow turns can run for up to ten minutes instead of timing out after two.
• If a turn's details can't be read, the assistant now tells you that none of them were applied.
• Safer builder tool tests. If the builder assistant proposes a tool test with unreadable arguments, nothing runs and no test budget is used. The assistant is asked to correct the arguments and try again.
• Better AI-assist system prompt suggestions. Suggestions now describe the automation's role and goal, audience and tone, constraints with their reasons, and what a finished run looks like. They no longer produce long lists of prohibitions.
• Clearer tool descriptions for agents. Four UniFi and UISP read tools now explain how their responses should be used before the matching update or service action. For example, they note that some updates replace the whole object.
• Reworded built-in automation templates. The templates' closing instructions are simpler. Updated templates appear as a new template version, and their steps are unchanged.

Optimizations

• The tool pickers in the automation builder no longer rebuild the full tool catalog on every screen update. Typing and editing in the builder should feel faster, especially for tenants with many connectors.

Bug fixes

• Fixed an issue where cancelling a connector configuration or opening another connector while a save was in progress could apply the save to the wrong connector. The form's Cancel button is now disabled until the save finishes.
• Fixed an issue where an Avanan connection that signed in successfully could still be disabled automatically after a later authorization error.
• Fixed an issue where the "All Tools" selection in the builder's tool slot editor could reset while you were editing.
• Fixed team invitations failing when the invited email address differed only in capitalization from an existing account.
• The dashboard button for personal-only connections now opens the personal section directly.

UI & UX changes

• An old personal sign-in now appears on its own card. If the sign-in is disabled, the member can remove it there. An active old sign-in points to the Team page instead.
• On the Team page, members without a display name are shown as "this person."
• The Huntress API key hint, setup guide, and authorization error now point to the current location of API credentials in Huntress. They also recommend using a dedicated least-privilege user.

Breaking changes

• Avanan MSP tools no longer use a second set of Infinity Portal credentials. If you entered one for the MSP tools, it is now ignored. Enter Avanan SmartAPI credentials on the connection to keep using the MSP tools.