r/AutoGenAI

▲ 14 r/AutoGenAI+8 crossposts

I built an open-source Agent Verifier for Claude Code, Cursor & other Coding Assistants that catches security issues, hallucinated tools, infinite loops and anti-patterns in Agent built using LangChain, LangGraph, and other frameworks. (free, open source, 100% local)

I've been using Claude Code for a few months and noticed AI agents consistently skip the same things: hardcoded secrets, unbounded retry loops, referencing tools that don't exist, and massive system prompts that blow context windows.

So I built Agent Verifier — an AI agent skill that acts as an automated reviewer which does more than just code review (check the repo for details - more to be added soon).

GitHub Repo: https://github.com/aurite-ai/agent-verifier

Note: Drop a ⭐ if you find it useful to get more updates as we add more features to this repo.

----

2 Steps to use it:

You install it once and say "verify agent" on any of your agent folder in claude code to get a structured report:

----

✅ 8 checks passed | ⚠️ 3 warnings | ❌ 2 issues

❌ Hardcoded API key at config.py:12 → Move to environment variable
❌ Hallucinated tool reference: execute_sql → Tool referenced but not defined
⚠️ Unbounded loop at agent/loop.py:45 → Add MAX_ITERATIONS constant

----

Install to your claude code:

npx skills add aurite-ai/agent-verifier -a claude-code

OR install for all coding agents:

npx skills add aurite-ai/agent-verifier --all

----

Happy to answer questions about how the agent-verifier works.

We have both:
- pattern-matched (reliable), and,
- heuristic (best-effort) tiers, and every finding is tagged so you know the confidence level.

----

Please share your feedback and would love contributors to expand the project!

u/Chance-Roll-2408 — 9 hours ago
▲ 11 r/AutoGenAI+9 crossposts

Need feedback

Been working on something which im deciding to call Dexi - a proactive agent to help you get stuff done. The problem it solves: you're juggling multiple clients or projects, and every context switch means re-checking calendars, todos, and notes scattered across your tools. Dexi now keeps a live picture per client/project deadlines, open tasks, recent changes and when something shifts (a cancellation, a new due date), it updates everything related and tells you what changed instead of you hunting for it. Switch contexts, everything's already current.

I've been running my own week on it daily through beta and it's the stickiest thing we've built. It's free to try right now, tryna get it out this sunday https://discord.com/invite/7VRZpSZGFN

All feedback welcome!!!

u/Glittering-Speed2210 — 3 days ago
▲ 8 r/AutoGenAI+4 crossposts

Need Help Choosing the Right AutoGen Teams Architecture

​

Hi everyone,

I'm currently working on a project where I need to migrate an existing multi-agent workflow to Microsoft AutoGen.

The current workflow is pretty simple:

- One node collects data from different sources.

- Multiple specialized node process that data in parallel (each has a different responsibility).

- A final validation node combines all the results and decides the final output based on some rules.

I first started using GraphFlow because it felt very similar to my existing graph-based workflow. However, my client wants the implementation to use AutoGen Teams instead.

I've gone through the documentation, but I'm still confused about which Team type is the best fit:

- Selector Group Chat

- Swarm

- Round Robin

- Or something else?

My goal is to keep the workflow efficient, allow parallel processing, and maintain the same quality of results.

If you've built projects using AutoGen Teams, I'd love to hear:

- Which Team would you choose for this kind of workflow?

- Any tips or common mistakes to avoid?

Thanks in advance for your help!

reddit.com
u/Ninjapakoda — 11 days ago