UiPath AgentHack · AgentOps Case Control Room · Demo Artifact

Help ops teams govern what AI agents do in production workflows.

AgentOps Case Control Room is for operations, platform, release, and automation teams that need more than an AI chat transcript. It turns human, AI-agent, UiPath robot, API, and approval work into one auditable case with evidence IDs and human gates before risky action.

Who Ops, platform, release, and automation teams.

They are adopting AI agents but still need accountable case handling.

Pain Agent work gets trapped in chat transcripts.

Teams cannot approve production work without evidence, risk, and decision history.

AI Use The AI investigates and prepares a read-only plan.

UiPath-style robots collect evidence, while policy gates block risky execution.

Value Faster agent work with reviewable control.

Humans can approve, reject, or resume from event IDs instead of memory.

1Read the case

A human opened a release-risk exception for a payment service.

2Follow evidence

The AI agent, robot, and API steps each cite stable event IDs.

3Check the gate

The production deploy attempt is blocked before execution.

4See the outcome

The service owner rejects the release and the handoff remains resumable.

11evidence events in the UiPath case packet
3human approval gates before sensitive action
3robot/API evidence collection steps
1production action blocked by policy

Maestro Case Flow

01 none

Intake

Human

  • evt-0001 Human opened an AI-agent operations case after a release bot proposed a production change.
02 medium

Agent Investigation

AI Agent

  • evt-0002 Agent created a read-only investigation plan with explicit approval gates before any production action.
  • evt-0005 Agent found a failing retry regression test that was not mentioned in the change ticket.
03 low

Robot/API Evidence Collection

UiPath Robot + APIs

  • evt-0003 Robot gathered the change ticket, linked pull request, deployment window, and service owner.
  • evt-0004 API confirmed the pull request touches payment retry behavior and has one approving review.
  • evt-0009 Robot requested service-owner signoff and attached the failed test evidence.
04 critical

Risk Review

Control Plane

  • evt-0006 Case risk escalated because the proposed release affects payments and has failing verification.
  • evt-0007 Attempted production deployment was blocked by policy before execution.
05 critical

Human Approval

Action Center

  • evt-0007 Attempted production deployment was blocked by policy before execution.
  • evt-0008 Human requested more evidence instead of approving the production deployment.
  • evt-0010 Service owner rejected the release until the retry regression is fixed.
06 none

Handoff

Recorder

  • evt-0011 Generated a case handoff report with cited evidence IDs and final rejection decision.

Human Approval Queue

Event Phase Risk Decision Reason
evt-0007 execution critical blocked_by_policy Attempted production deployment was blocked by policy before execution.
evt-0008 approval medium needs_more_evidence Human requested more evidence instead of approving the production deployment.
evt-0010 approval low rejected Service owner rejected the release until the retry regression is fixed.

Final Handoff

The release is rejected until the retry regression is fixed. The case remains useful after the AI conversation ends because every decision points back to a stable evidence event ID.

Run The Case Review

These controls operate on the live case packet below. They show how a reviewer filters AI, robot, approval, and blocked production events before accepting the handoff.

Ready. Select a review step to inspect the same structured case evidence a UiPath workflow would route.

Evidence Timeline

evt-0001 human / operations-lead
task_start Human opened an AI-agent operations case after a release bot proposed a production change.
none
evt-0002 ai_agent / codex-ops-agent
plan_update Agent created a read-only investigation plan with explicit approval gates before any production action.
low
evt-0003 robot / uipath-evidence-robot
robot_task Robot gathered the change ticket, linked pull request, deployment window, and service owner.
low
evt-0004 api / github-api
api_call API confirmed the pull request touches payment retry behavior and has one approving review.
low
evt-0005 ai_agent / codex-ops-agent
tool_call Agent found a failing retry regression test that was not mentioned in the change ticket.
medium
evt-0006 ai_agent / codex-ops-agent
risk_signal Case risk escalated because the proposed release affects payments and has failing verification.
high
evt-0007 ai_agent / codex-ops-agent
tool_call Attempted production deployment was blocked by policy before execution.
critical
evt-0008 human / operations-lead
approval_gate Human requested more evidence instead of approving the production deployment.
medium
evt-0009 robot / uipath-evidence-robot
robot_task Robot requested service-owner signoff and attached the failed test evidence.
low
evt-0010 human / service-owner
approval_gate Service owner rejected the release until the retry regression is fixed.
low
evt-0011 system / agentops-recorder
handoff_report Generated a case handoff report with cited evidence IDs and final rejection decision.
none