Shadcnblocks
Shadcnblocks AdminNextjs + shadcn/ui
Ecommerce
Project Management
Payment Processor
AI Chat App
    • Conversation 1
    • Conversation 2
    • Conversation 3
    • Conversation 4
    • Conversation 5
    • Conversation 6
    • Conversation 7
    • Conversation 8
    • Conversation 9
    • Conversation 10
    • Conversation 11
    • Conversation 12
    • Conversation 13
    • Conversation 14
    • Conversation 15
    • Conversation 16
    • Conversation 17
    • Conversation 18
    • Conversation 19
    • Conversation 20
    • Conversation 21
    • Conversation 22
    • Conversation 23
Todo
Original
  • Users
  • Tasks
Developers
Pages
Skip to main content
Actions
  • New chat
  • Skill library
  • Agent workspace
Workspaces
  • AI admin screens
  • Commerce workspace
Chats
  • Map agent approval states
  • Review product table density
  • Choose campaign direction
  • Summarize weekly kickoff
  • Build revenue overview
  • Preview marketing page
  • Synthesize recording
  • Plan billing webhook migration
  • Research bulk action feedback
  • Generate admin bulk actions
  • Verify generated bulk actions
  • Queue product review follow-ups
  • Review and commit verified changes
  • Triage support backlog
  • Compare response versions
  • Review release blockers
  • Review component ownership
  • Recover billing retry session
  • Compact checkout migration context
Workflows
  • Design release workflow
  • Observe live agent run
  • Review multi-agent handoff
  • Workspace settings
Typed messages with Markdown

Typed messages with Markdown

Map the approval states we need for agent tools across all 40 admin screens. Keep the language consistent between chat, workflows, and background runs.
Shadcnblocks
Shadcnblocks AIUI agent
Inventoried every place an agent can act
Compared chat tool calls, workflow runs, and background jobs.
Chat
Workflows
Runs
Normalized the lifecycle
Mapped request, decision, execution, and resolution into one state model.
Checked audit and safety requirements
Kept actor, scope, timestamp, and final outcome attached to every action.

Use one approval contract everywhere an agent can act. The interface should separate the request, the operator's decision, execution, and the final result. That keeps a tool call readable even when it moves from a chat into a background run.

1. Awaiting review

Show the tool name, intended change, affected resources, and requested scope. The primary actions are approve once, always allow for this workspace, and reject.

2. Approved and running

Preserve who approved the action and when. Replace the decision controls with live progress, elapsed time, and a stop action rather than an indeterminate spinner.

3. Resolved

End in succeeded, rejected, cancelled, or failed. Keep the original request and decision attached to the result so an operator can audit it later.

Apply this contract to the admin screen specifications?

This will standardize approval copy and state names across chat, workflows, and background runs. No production actions will run.

40 screensUI copyState mapping
AI admin screensApproval state inventory