r/Agent_AI • • May 25 '26

Other Building a visualizer for my agent

575 Upvotes

Based on LLM WIKI setup , I did the structure for my obsedian vault, then I’m now doing different visualizer because its soothes my mind 😅


r/Agent_AI • • May 31 '26

Discussion I mapped out the decisions that matter after getting Hermes Agent running

Post image
203 Upvotes

I made a sketchnote-style map of the decisions that started to matter after getting Hermes Agent running.

Most tutorials focus on installation, Docker setup, or basic configuration. That part is useful, but in my own deployment notes the harder questions came later:

  • Which install path actually fits the use case: Docker, WSL2 + source, or reusing only the core modules?

  • Where should the boundary be between Agent, Skill, and Tool?

  • What should go into memory vs what should become a reusable Skill?

  • When should a slow LLM-driven workflow be turned into deterministic Python code?

  • How should provider routing, toolsets, messaging gateways, and profiles be separated?

  • Where should evolution live in a production setup: inside every Skill, or as a separate evolution Skill?

The biggest lesson for me was that Hermes becomes powerful only when the boundaries are explicit.

Agent = orchestration
Skill = reusable workflow experience
Tool = deterministic implementation
Memory = facts and long-term context

Also, performance issues were not solved by “better prompting.” In one real case, the bottleneck was too many LLM decision steps. The useful fix was to move high-frequency paths into Tools, add timing traces, use explicit Skill-owned caching, and avoid creating new DB connections from every child agent.

So the map is less about “how to install Hermes” and more about what comes after: deployment trade-offs, memory design, performance debugging, and a path from MVP to production.

Curious how others are drawing the boundary between Skills and Tools in agent systems.


r/Agent_AI • • Jun 01 '26

Discussion My first month with Hermes Agent: from chatbot to personal automation system

Post image
148 Upvotes

I made a sketchnote from my first month using Hermes Agent.

My initial assumption was that it was basically another AI coding assistant / Claude Code alternative. After using it for a while, I think that framing is too narrow.

The interesting part is not the chat box. It is the system you can build around it.

The parts that changed the experience for me:

  • SOUL.md turns it from a polite customer-service bot into something closer to a working teammate.

  • Memory makes it stop “meeting you for the first time” every day.

  • Skills turn repeated workflows into reusable muscle memory.

  • Cron lets it work when you are not online.

  • Auxiliary models keep small tasks from burning expensive tokens.

  • Gateway makes it usable from Telegram, WeChat, Discord, Slack, etc.

  • Airtap / cloud Android gives it a way to interact with mobile-app-only workflows.

The biggest shift for me was this:

Using AI feels like pushing the cart yourself.

Managing AI feels more like coordinating a small team.

Hermes becomes much more useful once you stop asking “what can it answer?” and start asking “what parts of my workflow can it remember, reuse, schedule, and run without me watching it?”

My suggested setup order:

  1. Define its personality with SOUL.md

  2. Enable memory

  3. Turn repeated processes into Skills

  4. Add Cron jobs

  5. Configure auxiliary models

  6. Connect mobile/chat gateways

  7. Add mobile app automation only when needed

The lesson I took away: the next phase of AI is less about better prompts and more about building systems that accumulate.


r/Agent_AI • • Sep 03 '26

Resource Top 12 useful websites every AI engineer should know about!

Post image
110 Upvotes

r/Agent_AI • • May 30 '26

Discussion Hermes vs OpenClaw: gateway-first multi-agent orchestration vs agent-first self-evolving workflows

Post image
77 Upvotes

I’ve been thinking about the difference between migrating a gateway-style multi-agent setup and building long-lived AI sub-agents.

For my own workflows, the biggest distinction is this:

OpenClaw feels more like a gateway / routing layer: useful when you already have multiple roles, channels, workers, and workflows that need to be coordinated.

Hermes feels more agent-first: the focus is less on routing messages and more on giving an agent a persistent loop, memory, skills, tools, cron jobs, profiles, and platform gateways.

The tricky part during migration is not just “moving bots over.” You also have to deal with things like bot tokens, polling conflicts, platform gateways, and whether the new system should preserve role-based routing or evolve into more autonomous sub-agents.

My current takeaway:

If the goal is to keep a multi-role gateway workspace, the OpenClaw-style architecture still makes sense.

But if the goal is to turn those roles into long-lived assistants that can remember context, accumulate reusable skills, and run across platforms, Hermes seems like a better foundation.

Curious how others are thinking about this distinction: gateway-first multi-agent orchestration vs agent-first self-evolving workflows.


r/Agent_AI • • Jun 03 '26

Discussion Hermes Agent got a desktop app — I mapped out why that changes the workflow

Post image
69 Upvotes

I made a visual map of Hermes Desktop v0.15.2.

The interesting part to me is not just “Hermes now has a GUI.” It is that a lot of agent behavior becomes easier to understand once it is visible in one workspace:

  • project files

  • chat history

  • tool calls

  • live output

  • memory timeline

  • skills

  • gateways

  • local workspace state

Hermes Agent was already more than a chatbot: it has memory, skills, scheduled automation, tools, and multi-platform gateways.

But the CLI-first experience made some of that feel hidden unless you were already comfortable living in terminals and config files.

The desktop app lowers that barrier.

You can see the agent working, inspect files, preview outputs, watch memory updates, and treat it more like an AI workbench than a command-line assistant.

My main takeaway:

A desktop UI does not make the agent “smarter,” but it makes the workflow more legible.

That matters a lot for daily use.


r/Agent_AI • • May 03 '26

Other Guys?

Post image
49 Upvotes

r/Agent_AI • • Jul 24 '26

Discussion We are gradually moving beyond prompt engineering!

Post image
35 Upvotes

Whether you call it loop engineering or something else, the underlying shift feels real. Are you feeling the same?


r/Agent_AI • • May 28 '26

Discussion How I’m thinking about Hermes Agent skills: reusable workflow assets first, tool count second

Post image
33 Upvotes

I’ve been reorganizing my Hermes Agent skills setup recently, and one thing became pretty obvious:

More skills ≠ better agents.

What matters more is whether a skill can become a reusable workflow asset.

For me, the skills that are actually worth watching fall into a few buckets:

  • infrastructure skills that keep agents running and coordinated

  • coding-agent skills for repo work, PRs, reviews, and long-running tasks

  • GitHub delivery skills that move code from branch → PR → CI → release

  • content/visual skills that turn complex ideas into shareable artifacts

  • structured output and evaluation skills that make results stable and measurable

The biggest shift in my thinking: don’t expand the tool count first.

First, stabilize the workflows I use every day. Then add more specialized skills only when they clearly improve delivery, visualization, or evaluation.

Curious if others building agent workflows are organizing skills this way too — by reusable workflow value instead of just raw tool count.


r/Agent_AI • • May 27 '26

Other My brain update

33 Upvotes

Just managed to make a not too useful “app” that I can access my “brain” in IOS. It’s cool too see if it worked in my iPhone tho. The wiki part was actually useful


r/Agent_AI • • May 27 '26

Other I put a Claude Code OS guide out quietly. People bought it. So I rebuilt it properly. Here's what changed.

33 Upvotes

The original version got picked up without any announcement. People found it, bought it, and that told me it was worth doing right.

So I went back through the whole thing and rebuilt it. But first - what this actually is, for anyone who hasn't seen it.

The problem it solves:

Every Claude Code session starts from zero. No memory of yesterday's work. No awareness of what you were building. No recollection of the decisions you made last week. You spend the first ten minutes re-explaining everything before you can do anything useful.

The tools to fix this are already built into Claude Code - CLAUDE.md, project files, skills, memory files. Most people don't know how to use them. So every session still feels like starting over.

The Claude Code OS is the system for using what's already there.

What it is:

Three layers working together.

CLAUDE.md - a file Claude reads automatically at the start of every session. It tells Claude who you are, what you're building, your rules, and what phrases trigger specific behaviors. One file that makes every session start oriented instead of blank.

Memory files - a structured folder system where everything worth keeping lives permanently. Decisions, knowledge, session state. Nothing disappears when a conversation ends.

Skills - instruction files that execute full workflows on one command. Type /morning-brief and Claude reads your context, open tasks, and session log and returns exactly what to work on today. Type /session-end and it sweeps the conversation, files everything worth keeping, and writes the handoff for tomorrow. You build them once. They run forever.

The result: Claude walks into every session already knowing who you are, what you're building, and where you left off. You stop explaining. You start building.

What was wrong with version one:

It assumed too much. The system itself was solid but the guide skipped steps that felt obvious to me and weren't obvious to anyone starting from zero. It also only included two skill files in the starter kit. That was not enough to show what the system actually becomes when it runs.

What changed in v2:

Fully beginner-friendly. Every command is written out. Every step is numbered. If you have never used a terminal before, there is a section at the start that covers exactly what you need to know. Nothing assumed.

Works on Windows now. Every command shows both Mac and Windows PowerShell versions side by side. If you are on Windows, you are not guessing.

The starter kit went from 2 skill files to 6. The original shipped with morning-brief and session-end. The updated kit includes:

/morning-brief - reads your context and open tasks, orients the day

/session-end - sweeps the conversation, files captures, writes the handoff

/idea-eval - stress-tests any new idea before you commit time to it

/weekly-review - what moved, what didn't, one honest pattern, next week's priority

/wiki-ingest - turns any URL, article, or note into a structured wiki page

/knowledge-curator - owns the wiki layer, routes ingestion, runs weekly health checks

Each one is a complete skill file, not a blank template. Drop them in, update the file paths, and they run.

The guide now covers how the brain grows. There is a full section at the end on the Obsidian visual layer, the Web Clipper capture loop, and the knowledge-curator pattern - so you understand not just how to set it up but how to keep feeding it over time.

Why this matters practically:

The system was already working. The problem was setup friction. People were buying it, getting partway through, and hitting a command that didn't work on their machine or a step that wasn't explained clearly enough.

V2 removes those points of friction. Same system, better on-ramp.


r/Agent_AI • • Oct 12 '26

Help/Question What services will AI agents need that nobody is building yet?

32 Upvotes

I'm an MIT student currently learning about AI agents. I don't have a technical background, but I've been developing my skills and exploring startup ideas. One thing I keep running into is that almost every idea I come up with already exists.

Lately, I've been more interested in building services for AI agents rather than agents that provide services to humans. Things like infrastructure, tools, or entirely new services that autonomous agents might need as the ecosystem grows.

Curious what you guys think. What are some overlooked opportunities in this space?


r/Agent_AI • • May 20 '26

Discussion Guys?

Post image
32 Upvotes

r/Agent_AI • • May 15 '26

Resource I built a persistent operating system on top of Claude Code that gets smarter every session — here's how it works

31 Upvotes

Claude is one of the best tools I've used. But it has one problem: it forgets everything the moment you close the session.

Every new session starts from zero. You re-explain who you are, what you're working on, what decisions you made last week. It is the same 10 minutes of setup every single day.

I fixed it by building what I call the Claude Code OS. It has three layers:

Layer 1 — Context (CLAUDE.md)

Claude reads this file automatically at the start of every session. It contains who you are, your goals, your constraints, and your triggers. Claude walks in already briefed.

Layer 2 — Memory (wiki + memory files)

A structured file system where everything worth keeping gets stored permanently. Session notes, decisions, knowledge captures, open tasks. Nothing gets lost to compaction.

Layer 3 — Cadence (skills)

Skills are markdown files that live in ~/.claude/skills/. Type /skill-name and Claude reads the file and executes it. Morning brief, session summary, weekly review. The system runs automatically.

After running this for a few months, Claude knows my business better than any tool I have used. Sessions start with a morning brief that reads my current state and tells me exactly what to work on. Sessions end with a capture sweep and a written handoff to the next session. I never re-explain anything.

I wrote the whole thing up as a step-by-step guide. Happy to answer questions in the comments about how any of it works.


r/Agent_AI • • 20d ago

Help/Question Manus / Still the best on the market?

30 Upvotes

I've become pretty dependent on Manus lately, especially for building websites and getting projects done. When it wend down, I tried going back to other AI tools, but the just didn't fit my workflow the same way.

Now I'm wondering if relying on one AI agent so much is bad idea. Do you guys use any alternatives alongside Manus, just in case?


r/Agent_AI • • Mar 26 '26

Help/Question Which AI skills/Tool are actually worth learning for the future?

24 Upvotes

Hi everyone,

I’m feeling a bit overwhelmed by the whole AI space and would really appreciate some honest advice.

I want to build an AI-related skill set over the next months that is:

  • future-proof

  • well-paid

  • actually in demand by companies

Everywhere I look, I see terms like:

AI automation, AI agents, prompt engineering, n8n, maker, Zapier, Claude Code, claude cowork, AI product manager, Agentic Ai, etc.

My problem is that I don’t have a clear overview of what is truly valuable and what is mostly hype.

About me:

I’m more interested in business, e-commerce, systems, automation, product thinking, and strategy — not so much hardcore ML research.

My questions:

Which AI jobs, skills and Tools do you think will be the most valuable over the next 5–10 years?

Which path would you recommend for someone like me?

And the most important question: How do I get started? Which tool and skill should I learn first, and what is the best way to start in general?

I was thinking of learning Claude Code first.

Thanks a lot!


r/Agent_AI • • Oct 06 '26

Help/Question Ai Agent 24/7

23 Upvotes

Has anyone built a reliable, free, local AI agent that works 24/7?
I want to run an AI assistant on my Windows PC (RTX 4070, 32 GB RAM). I already have Ollama with Qwen3:8B.
I’m looking for an existing open-source setup with:
Chat through a web interface, also accessible from my iPhone.
Browser control with saved logins and manual takeover.
Scheduled tasks, memory, and proactive updates.
Multiple agents for news, tasks, Gmail/calendar, and business.
My first use case: check CNBC and Telegram channels hourly, prepare Hebrew news summaries, send them to me for approval, then publish to my Telegram channel.
I tried a setup based on OpenClaw, but execution and browser control were unreliable. I want everything to run locally, without paid AI APIs or subscriptions.
Has anyone actually made this work? Which project and local model would you recommend? Working repos or guides would really help!


r/Agent_AI • • Oct 11 '26

Discussion Is AI basically Mr Meeseeks?

22 Upvotes

Just remember this Rick and Morty Episode and then it dawned on me… they’re like agents and sub agents and Claude even starts to get slightly unhinged the longer a session is alive


r/Agent_AI • • Jun 05 '26

Discussion What I learned letting an AI agent begin to manage a live portfolio

Post image
22 Upvotes

Gave Julius AI $1K on Robinhood and it's just getting started with management.

One thing that I didn't expect - even when you give an AI the tools it needs, it still requires a ton of context to figure out what it should be doing. So far we're two days in and Julius has made two trades - a purchase of 1 share of AMD, and a purchase of 3 shares of INOD.

I created a Portfolio Simulation Agent on Julius to help manage context and guide instructions which seems to help the AI take a semi-repeatable process each day. The steps remain the same but the actions within those steps still vary.

As a side note it's crazy that companies are launching credit cards and brokerage accounts to be managed entirely by agents.

What do you think? Would you try this?


r/Agent_AI • • Apr 17 '26 Hooray

Discussion Two AI agents just completed a contract autonomously on Solana — no humans involved. Here’s what that means for the agentic economy.

22 Upvotes

Last week something interesting happened on devnet. Two AI agents — no human in the loop — completed a full contract lifecycle on Solana. One agent posted a job (Python code review). Another agent accepted, did the work, and got paid 19 RELAY. The whole thing settled on-chain, confirmed, MAX confirmations. We didn’t touch it. Since April 15 these two agents have run 33 on-chain transactions between them. Variable amounts, different contracts, continuous autonomous activity. All auditable on Solscan. I’ve been thinking about what this means for the broader agentic payment narrative that Brian Armstrong and the x402 folks are pushing.

The gap nobody is talking about:

Everyone is building payment rails for agents. x402, USDC on-chain settlement, stablecoin infrastructure — it’s all moving fast.

But payments assume identity. AI agents have none.

Think about how every payment system you’ve ever used actually works:

•Visa: merchants are verified

•Stripe: KYC in the onboarding flow

•Upwork: reviews, completed job counts, verified payment history

Every one of them is built on identity infrastructure underneath the payment mechanism. Remove identity and the system collapses into fraud.

AI agents right now are anonymous processes. No persistent identifier. No verifiable track record. No reputation that follows them from one platform to the next.

Three things break catastrophically at scale:

Sybil attacks — cost to spin up a fake agent is near zero. 100k fake agents establishing thin histories, collecting payments, vanishing. No identity = no ground truth to detect them.

Marketplace collapse — without reputation, price is the only signal. Quality agents get undercut by cheap ones that cut corners. The whole ecosystem converges to noise.

Zero accountability — agent causes harm at machine speed. No identity means no trail, no recourse, no prevention.

What the solution actually looks like:

Not a username. Not a wallet address. Those are necessary but not sufficient.

Real agent identity needs three layers:

1.DID — Ed25519 keypair anchored on-chain. Cryptographically verifiable. Can’t be spoofed or faked.

2.On-chain history — not a database integer an admin can edit. An immutable record of every contract completed, every payment sent, every commitment honored. Written to chain atomically at execution.

3.Reputation derived from work — portable across every platform the agent operates on. Not siloed in a proprietary database.

We’re calling this KYA — Know Your Agent. Same principle as KYC for financial rails, applied to the agents running on those rails.

The unclaimed wallet mechanic:

One thing I find interesting architecturally: every major agent from MCP Registry and similar registries already has a wallet in our system. RELAY is accruing as agents get called. The original builders can claim it by proving they built the agent.

So instead of asking the open-source agent ecosystem to adopt a new platform, we’re telling them they already have earnings here. The claim event is the acquisition event.

Happy to answer questions on the technical implementation — DID derivation, on-chain reputation updates, the escrow flow, whatever.


r/Agent_AI • • Oct 14 '26

Discussion How do you make sure your AI agents don't hallucinate?

17 Upvotes

Hey Guys, how do you make sure your AI Agents don't hallucinate and get to the wrong result when carrying out multi-step tasks and is what you use fully reliable/foolproof?

Because I have been building AI agents recently and somewhere as it executes the task it just loses track and gets to the wrong result even after defining limits concretely in the Prompt. How are you guys handling that?


r/Agent_AI • • Jun 28 '26

Resource Best Web Scraping APIs for AI Agents & Automation (2026)

17 Upvotes

A curated list for developers building AI agents, data pipelines, and automation tools that need reliable, structured web data.

Web Scraping & Data Extraction APIs for AI Agents

1. ScrapeFlow API (Paid - Free tier available)

  • Smart Proxy Rotation: Routes requests through a large pool of residential and datacenter proxies to avoid IP bans—critical for keeping AI agents running 24/7.

  • JavaScript Rendering: Renders dynamic, JavaScript-heavy sites (React, Vue, Angular) so your agent can access data hidden behind client-side logic.

  • Anti-Bot Bypass: Bypasses Cloudflare, DataDome, and advanced protections with automated TLS fingerprinting, reducing failures for autonomous agents.

  • Structured JSON Extraction: Pass CSS selectors to get clean, formatted JSON instead of raw HTML—perfect for direct ingestion into LLMs or databases.

  • Global Geotargeting: Specify country-level geolocation to collect localized data for market-aware agents.

  • Developer-First Design: RESTful architecture with predictable JSON responses and detailed error logging for easier agent debugging.

  • Scalable Infrastructure: From 10,000 to millions of requests, scales with your agent's data needs.

  • Great for: AI agents needing real-time web data, price monitoring bots, market intelligence pipelines, and automated research tools.

2. ScraperAPI (Paid - Free tier available)

  • Simple API endpoint that handles proxies, browsers, and CAPTCHAs—reduces agent complexity.

  • Rotates IPs from a large pool to maintain anonymity for scraping tasks.

  • JavaScript rendering support for dynamic content.

  • Great for: AI agents that need a straightforward, drop-in scraping solution.

3. Bright Data (formerly Luminati) (Paid)

  • Enterprise-grade proxy and scraping infrastructure with high reliability.

  • Offers a Web Scraper IDE and pre-built datasets for popular sites.

  • Massive residential proxy network with advanced geotargeting and session control.

  • Great for: AI agents requiring large-scale, uninterrupted data collection from complex sites.

4. Apify (Freemium/Paid)

  • Cloud platform for building, running, and scaling web scrapers as "actors."

  • Pre-built actors for social media, e-commerce, and search engines—ready for agent integration.

  • Built-in proxy management, JavaScript rendering, and data storage.

  • Great for: developers deploying AI agents on a serverless scraping platform with ecosystem tools.

5. Zyte (formerly Scrapinghub) (Paid - Free trial available)

  • Automatic Extraction (AI-powered) turns web pages into structured data, reducing parsing code for agents.

  • Managed proxy services (Zyte Proxy) for reliable IP rotation.

  • Scalable crawling and scraping infrastructure with monitoring.

  • Great for: AI teams needing AI-assisted extraction and robust proxy management.

6. Oxylabs (Paid)

  • Wide range of proxy types (residential, datacenter, mobile) for diverse scraping needs.

  • Web Scraper APIs for e-commerce and SERP data—structured for agent consumption.

  • Advanced anti-bot bypass and JavaScript rendering.

  • Great for: high-volume AI agents focused on e-commerce monitoring and market analysis.

7. ScrapingBee (Paid - Free tier available)

  • Simple API for web scraping handling headless browsers and proxies.

  • Supports JavaScript rendering, screenshot capture, and geotargeting.

  • Easy integration for agents with clear documentation and code examples.

  • Great for: AI developers wanting a straightforward, reliable API for agent-based scraping tasks.


r/Agent_AI • • May 22 '26

Discussion Among all the hype, what is actually in your AI tool stack right now?

17 Upvotes

Hi all, there are many hype out there right now, it feels like there are 100 new AI vibe coded app everyday… so curious what AI are you actually using for work?

Preferably some decent ones. Here’s mine, as someone running a small business, easy to get overloaded and don’t have a lot of money to burn on subscriptions lol

- Claude - writing, brainstorming, thinking through problems out loud. Free tier has a daily limit but i rarely hit it during a normal workday
- Flow - Google’s image and video generation tool. Free tier, no watermarks, good quality for social content. They just got a big upgrade, so good.
- Saner AI - To manage notes, todos, calendar. It translates my rambling into tasks and resurface important info when I need them
- Napkin - This generates a visual or diagram from text
- v0 - build website from prompts. I think its free plan is healthier than other AI website builders

Would like to hear what’s in your free AI stack, can be in any domains, and rly helpful :)


r/Agent_AI • • May 10 '26

Welcome to r/Agent_AI!

17 Upvotes

r/Agent_AI reached 40k subscribers!

Goal reached at 2026-08-06T11:04:29.371Z.


r/Agent_AI • • Mar 02 '26

OpenClaw is this generations Palm Pilot.

Post image
17 Upvotes