Skip to main content

StackJack 0.1.0.14711+a90a315

StackJack 0.1.0.14711+a90a315

This release lets organizations remove their own Anthropic key from StackJack without contacting support. AI Governance drift checks now respect each connection's "Turn changes on" setting, and some Portal pages load faster.

New features

  • Remove your own Anthropic key. Organization owners and administrators can now remove their Anthropic key themselves. Before, this required contacting support.
  • Confirmation step:
    • If no run is using the key, the confirmation shows how many automations were set up on it.
    • If a run is still using the key, the confirmation lists the runs and the Remove button is disabled until they finish or you cancel them.
  • What happens to automations:
    • Automations set up while the key was on file do not start until you re-sync them or add a key again.
    • A staging copy set up on the removed key needs its own re-sync, a new staging copy, or a key on file.
    • An automation that is refused for this reason is not billed for AI usage.
  • Runs StackJack is still stopping: These hold the removal for up to about an hour, and the message asks you to try again in a few minutes. After that window, the removal goes ahead. Any session still open is then yours to stop from your Anthropic console.
  • What removal does and does not do:
    • StackJack deletes its stored copy of your key. The key stays valid at Anthropic until you revoke it there.
    • Memory stays in your Anthropic workspace. A re-sync does not carry it over.

Improvements

  • Drift checks respect "Turn changes on". When "Turn changes on" is off for a client's connection, drift checks now only report differences. The Drift page and the drift tool show the difference with a plain explanation that changes are off for that connection. StackJack creates no fix attempt. When you turn changes on, the next check requests the fix as usual.

Optimizations

  • Portal pages that check members' recent usage now load faster and more reliably for larger organizations. This includes the Connectors page and the Team page's last-use details.

Bug fixes

  • Drift enforcement no longer stops on its own. Repeated fix attempts on a connection with changes turned off could stop drift enforcement, and someone had to resume it manually. These refused attempts no longer count toward stopping enforcement. A stop caused only by them is now released automatically.
  • Waiting fixes are cancelled when changes are off. If a fix is waiting on a connection where changes are off, including one a person requested, it is cancelled at the next check. If it runs before that check, it ends with "Changes are not turned on." Turning changes back on before the check keeps the waiting fix in place.