Technology

agent permissions

6 synchronized stories carry this tag.

Antigravity App 2.26 docks permission prompts and configures MCP plugins

Google's Antigravity App 2.26.0 keeps question and permission prompts docked above the composer, adds conversation filters and notification controls, and lets users configure declared MCP plugin variables without reinstalling. The release also repairs ADC credential switching, plugin header substitution, sleep and Wi-Fi reconnects, failed undo handling and Windows diff paths.

Why it matters: The app can keep accepting queued follow-ups while an approval is open and can change MCP connection variables in place. That makes prompt ordering, effective connector configuration and recovery state part of the permission boundary rather than a purely…

Read storyOriginal source · antigravity.google

Antigravity 2.23 puts permissions beside the prompt

Google Antigravity 2.23 adds a permissions-preset picker to the message box, ZIP and folder attachments, full-screen media review, MCP restart and agent-assisted repair, plus clearer subagent approval and error states.

Why it matters: Moving permission selection into the prompt surface can make authority easier to inspect per task, while archive ingestion and agent-assisted MCP repair create new extraction, dependency and execution boundaries that need explicit tests.

Read storyOriginal source · antigravity.google

GitHub Copilot Assisted Permissions reaches GA across CLI, app and VS Code

GitHub promoted Assisted Permissions to general availability across Copilot CLI, the Copilot app and Visual Studio Code. A model classifies command, filesystem and URL requests as clearly safe or approval-required, while enterprise settings can disable Assisted, block Allow All and set a default mode.

Why it matters: The rollout moves model-mediated permission decisions from a CLI-only release line into three production surfaces. It reduces approval friction but makes the classifier part of the authority boundary, so administrators need observable defaults, denials and…

Read storyOriginal source · github.com

LiteLLM 1.105 reaches RC1 with fail-closed startup and guardrail paths

LiteLLM promoted 1.105 to signed release candidate 1. The candidate retains the earlier agent-permission, delegated-identity, credential-isolation and tracing work while adding a Microsoft 365 Graph MCP catalog entry, non-canonical activity-date rejection, forced exit after database setup failure, fail-closed Straiker v3 handling when a verdict is missing, and storage, guardrail and migration fixes.

Why it matters: The release candidate is a more testable checkpoint for the gateway's agent identity and policy work, and several additions move error handling from ambiguous continuation toward explicit failure. It remains a preview with a broad change surface, so…

Read storyOriginal source · github.com

Claude Managed Agents adds server-evaluated permissions and live approval

Anthropic added an `auto` permission mode for Claude Managed Agents that lets the server allow, deny or pause each agent or MCP tool call for approval. New evaluation fields expose the decision in tool events, while `ant beta:sessions connect` lets an operator watch a running session and approve or deny waiting calls from a terminal or local web viewer.

Why it matters: The release turns permission policy and human intervention into observable runtime controls instead of relying only on prompt instructions or an opaque approval surface.

Read storyOriginal source · platform.claude.com

GitHub adds enterprise-managed permissions for Copilot agents

GitHub made centrally managed permissions generally available for Copilot agent operations. Administrators can set shell commands, file reads and edits, and network domains to blocked, require approval or proceed, with team-specific policies across the Copilot app, Copilot CLI and VS Code sessions using Agent Host.

Why it matters: Organization policy can now override local settings, auto-approval and saved approvals, reducing the chance that an individual convenience setting silently weakens an enterprise agent boundary.

Read storyOriginal source · github.blog