AlpacaX
Blog

Product

Product update: the judgment behind every approval

See the reasoning behind each approval request, without bringing agent runs to a halt.

Taeyeong Baek
Taeyeong BaekGTM Associate · 11 August 2026

See the reasoning behind each approval request, without bringing agent runs to a halt.

Approvers need context, not just a command and an approve button. Approval requests now show the runtime engine's assessment of each privileged command. Agent runs wait for a human decision instead of failing, and users can manage account security from a single page.

Approvals now include the reasoning behind them

When a privileged command requires approval, the request includes the runtime engine's risk assessment for that command and the Work Session it belongs to.

If an approver narrows the scope or shortens the approval window, those changes are reflected in the request across email, Slack, and the terminal.

The engine also evaluates commands run through wrappers such as docker exec and psql, keeping routine work out of the approval queue. It provides the context; a human still makes the final call on commands routed for approval.

The approval request now carries the engine's assessment and the Work Session behind it.

Keep governance on without stalling automation

Give an agent a task and approve any request when it arrives. The run will continue from where it paused.

Previously, an agent that reached an approval gate failed immediately. Even if the request was approved later, the entire run had to restart. The agent now pauses at the gate and resumes as soon as it receives a decision.

The same flow works over MCP and the Alpacon CLI. MCP setup is simpler as well: the approval flow is built into the server, read-only checks do not require execution permissions, and you can register only the tools an agent needs.

AWS instances register themselves, and approvals reach Slack

Connect an AWS account once, and new instances can register with Alpacon automatically instead of being configured one by one.

Connect Slack from the same Integrations page to receive approval requests where your team already works. Lightweight requests can be approved in Slack; anything that needs a stronger identity check hands off to the Alpacon console.

AWS and Slack are each connected once, from Integrations.

See who is signed in, and cut off what you do not recognize

The account security page lists every device and browser currently signed in to your account, with the IP it connected from and when. If a session is not yours, revoke it directly.

Every device signed in to your account, and a way to cut off the ones that should not be.

Also shipped

  • Search session records, cancel a pending request, and set how long a run waits for approval from the Alpacon CLI.
  • Command output streams as it runs, with sensitive values masked.
  • A command palette lets you navigate the console from the keyboard.
  • Editor sessions reconnect after a network interruption.
  • Session recordings support full-screen playback.
  • Seat counts update correctly when invitations are accepted or users are removed.
  • Security improvements landed. Self-hosted deployments should update.
Tags:
  • Product update
  • Approvals
  • AI agents
  • MCP
  • Slack
  • Account security
Taeyeong Baek
About the authorTaeyeong BaekGTM Associate

Taeyeong Baek works on go-to-market at AlpacaX, covering Alpacon, an AI-native PAM platform with runtime execution control for AI agents. He works where the product meets its users—supporting proof-of-concept deployments and building the demo videos and onboarding emails that teams see first—and writes the product updates from there: what changed, and what it makes easier for teams running AI agents in production.


Product update: the judgment behind every approval | AlpacaX