DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to watch agent authority decisions in Docker Desktop with Docker

Use the Docker Desktop extension to see PROCEED, HOLD, and BLOCK outcomes and pending approvals.

Who it is forSecurity or engineering lead who wants live visibility into what AI agents are attempting in local or team Docker environments.

The problemWithout a view of decisions, teams cannot see which agent actions were held, blocked, or overridden.

The outcomeA live view of authority decisions, reason codes, pending Presence approvals, and policy drift or overrides.

What you need first

  • A Docker environment, such as Docker Desktop, where you can run the Decionis components
  • An AI agent or MCP client that can send proposed actions to Decionis before running a tool
  • A written policy for which actions need PROCEED, HOLD, or BLOCK, since Decionis evaluates against versioned policy
  • Awareness that the README says components are released incrementally, so some listed features may not be available yet

Steps

  1. Install the Decionis Desktop Extension in Docker Desktop once it is available for your version.
  2. Connect the extension to your running Decionis components.
  3. Open the live decisions view and filter for HOLD outcomes.
  4. Review the policy and reason codes for any held or blocked action.
  5. Check the policy drift and override section for changes that need follow-up.

Prompt for your agent

Using the decionis/docker repository, open the Docker Desktop extension and list the most recent PROCEED, HOLD, and BLOCK decisions with their policy names. Expected output: a table of decisions with verdict, policy, and reason codes. Verify that each HOLD has a matching pending Presence approval or a recorded resolution.

Caveat. The README says the extension is designed to surface these views, so confirm which views ship in your release before relying on them.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page