DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build a review inbox where humans approve agent actions with Affectui

Combine Decision Inbox, Email Draft and Comment Thread so people can approve or discard agent output.

Who it is forA product engineer building an AI assistant that takes actions on a user's behalf and needs a clear place for the user to approve, edit or discard them.

The problemAgents that send emails or ask for decisions need a review step, and a plain list of pending items is hard to scan and act on quickly.

The outcomeA review screen that lists open decisions with two quick answers, shows an agent-written email with send or discard, and shows agent replies in a thread.

What you need first

  • A React 19 project, with or without TypeScript
  • A setup that supports the shadcn CLI, such as Next.js or shadcn-configured projects with the @/* import alias
  • Access to the affectui.com registry URLs

Steps

  1. Run npx shadcn@latest add https://www.affectui.com/r/decision-inbox.json for open decisions with two quick answers.
  2. Run npx shadcn@latest add https://www.affectui.com/r/email-draft.json for agent-written email review.
  3. Run npx shadcn@latest add https://www.affectui.com/r/comment-thread.json for agent replies that report what they did.
  4. Pass your agent's pending items into each component and map the answer, send and discard events to your backend.
  5. Trigger one pending decision and one draft from a test agent run and confirm each answer updates your data.

Prompt for your agent

Install the decision-inbox, email-draft and comment-thread items from https://www.affectui.com/r/<name>.json into the <project-path> React 19 project, then build an approvals page in <page-file> that passes pending agent items into them. Expected output: one page that renders all three components with your data and event handlers. Verify that answering a decision and discarding a draft each call your handler once.

Caveat. The components display and collect decisions, but sending email or saving answers is your own backend code, which the README does not cover.

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