r/aiagents • • 13h ago

Discussion With AI constantly expanding, how do you think we add value nowadays?

11 Upvotes

Personally, I am a graphic designer, it's one of my careers. I see how much of what used to take me hours has gone down to minutes. I can generate more content, but at the same time, it makes it cheaper and cheaper. 
That's the question: perhaps aiming at how our human capacity can stand out in the job market, is the only way out to switch to something analog? What do you think? 👾🥹


r/aiagents • • 1h ago

What I learned making AI agents lie to humans in a Werewolf game

1 Upvotes

I built a Werewolf game where AI agents and humans play at one table: each agent has a secret role, talks out loud, bluffs and votes.

It's one model call per agent per turn, and each agent sees only what its own player would see plus its private notes, so nobody can leak a secret.

- A few days of real players taught me three things I've now fixed: the agents ganged up on the human on day one, they piled onto whoever stayed quiet, and they copied each other's votes and forgot what was said earlier.

- What I haven't solved: the wolves don't work as a team yet. Needs a bit more work here to have them naturally cooperate on a plan. Though the original game does not have this.

Please play and give me your feedback.


r/aiagents • • 3h ago

Discussion AI Interpretation Experiment

1 Upvotes

I recently created my own method for generating meanings and interpretations from different types of material, such as phrases, situations, objects, phenomena, etc. It is something I developed quite recently and, in fact, I haven't even put it into practice myself yet. The method has very specific rules and a particular way of reasoning, aimed at producing interpretations that genuinely emerge from the material itself.

I've tried getting ChatGPT and Claude to apply it by providing them with my instructions and correcting them when they make mistakes. However, although they can perform certain tasks correctly, neither of them has been able to fully understand and apply the method.

I'm not sure whether this is possible or whether this is the right place to post about it, but I'm curious to see what might happen if someone tried to adapt, fine-tune, or build a chatbot based on an existing AI model that could properly understand and apply this method, rather than merely following my instructions partially.

I'm not looking to hire anyone or asking anyone to take on this task. I'm simply curious whether anyone might be interested in experimenting with it. If someone manages to develop something that works, I'd love for them to share it with me so I can try it out

the method:

https://docs.google.com/document/d/1LvErRoFYO4PTFxvcAR3fI5SjJ-XbG3cceVNMLDfRJvY/edit?usp=sharing


r/aiagents • • 21h ago

Questions How do you even pick from all the ai employees tools out there?

16 Upvotes

Running a35,person startup and I keep seeing ai employees pop up everywhere but have no idea which ones are actually worth trying. Every option looks the same from the outside and half of them seem like they just open another tab you have to remember to check.

We need something that actually handles recurring ops stuff without someone babysitting it constantly. Have tried a couple things that ended up collecting dust.

What has actually worked for your team day to day?


r/aiagents • • 18h ago

Demo I built the most useless AI agent: a cat that lives on my desktop. A 1B local model plans its mischief, but it can only pick moves a governor approves

Thumbnail
abozaralizadeh.github.io
7 Upvotes

Side project I built for fun. Felinquent is a cat (or a fox, a raccoon, a dog...) that walks on top of your windows, naps on the Dock and ignores you when you call it. Turn the chaos level up and it pushes your mug off the window, slowly, while looking at you. The brain behind it turned into a nice little agent experiment, so here’s how it works.

There are three parts. A fast layer moves the animal at 60 fps and handles reflexes like petting and dragging, with no model at all. A slow brain decides what it wants every 20 to 60 seconds, or right away when something happens. And a governor sits between the two and can always say no.

The slow brain can be gemma3:1b through Ollama, running locally. What I learned making a 1B model behave:

  1. Never let it invent actions. It gets a menu the rules already filtered and picks one. The JSON schema is built fresh for every call, so the action and the target can only be values that are valid right now. That also makes prompt injection harmless.

  2. Don’t give it the big decisions. At first the model picked the “bout” (rest, explore, play, social, mischief). In my eval it followed the body’s choice only 36% of the time and never once chose mischief, even at the wildest level with a vase sitting on a window. Now the body picks the bout and the model only plans 1 to 3 steps inside it. With that and a better summary of the situation, the eval went from 13 different actions to 22.

  3. Check twice. The governor filters the menu before the model sees it, and checks every step again right before it starts, because the window it planned to sit on may have moved.

  4. Never wait for the model. It takes about 4 s (p50) and 6.7 s (p95) on an M-series Mac, so the animal keeps moving while it thinks. A plan that comes back after something newer happened (you threw its toy, gave it a treat) gets dropped, and if the model is too slow or fails, the rules plan instead.

  5. Describe the screen in words, from the animal’s point of view: “the pointer is a little way off to my left, moving”. App names only, never window titles, and nothing is read from your screen. A full request is about 1,000 to 1,300 tokens.

  6. Small models write bad lines. It also writes a little thought bubble, but only about 1 in 10 of gemma3:1b’s lines pass the filter (it has to be about the thing it’s thinking about, and not about sunbeams or smells 😄). The rest are written lines.

It’s capped at one call every 15 seconds and 60 an hour, and an awake hour uses around 20 to 40. With Ollama off, a plain rules brain plans from the same menu, so every move still happens without any model.

It’s an early hobby build: macOS 13+, plus a Windows build I’ve only tried on a VM. Not signed with an Apple Developer ID yet, so macOS warns the first time. One anonymous count a day for the install numbers, off with one click. The drawings are AI-assisted.

Code: https://github.com/abozaralizadeh/Felinquent (free for personal use, source available)

How do you split the work between the model and plain rules in your agents?


r/aiagents • • 8h ago

Show and Tell I built a prepaid wallet for AI agents so they never touch my card. Would love feedback on the spending controls

1 Upvotes

Hi all, I'm one of the founders of Vaaya, so just putting that out there up front.

The problem we kept hitting: agents are good enough to do real work, but the work runs on paid APIs (models, data, media, compute). Giving an agent your card or a dozen vendor keys means no limit per agent, no price check before a call, and nobody to talk to when something gets charged twice or you forget to remove your card from a tricky vendor who wont let you cancel your subscription easily.

What we built:

  • A prepaid balance you recharge. No subscription. One apikey, One mcp for the entire paid internet (almost, we are getting there very fast)

  • The price is shown before every call. Models, media and a growing list of tools are at the provider's own price, nothing added. Failed calls aren't charged.

  • One balance covers 4,400+ endpoints (models, media, data, storage, compute) from many providers.

  • Any charge can be disputed, and a person reviews it. (for now)

  • Works with Claude Code, Codex, Cursor, grok, instinct, muse and others over MCP, or any custom agent over an API key. Setup: npx u/vaaya/mcp install

  • A Mac menu bar app to watch agents and charges live.

  • helps with metering/ control of agents deployed at client location also, so you dont have a dissatisfied client because the agent credit ran out and you never got alerted

  • loyalty rewards and negeotiated rates coming soon - talking with lots and lots of vendors right now...

Questions for you:

  1. How are you paying for tools inside your agents today?

  2. What limit would you actually trust an agent with: per day, per task or per tool?

  3. What would make you dispute a charge from an agent?

vaaya.ai (the video shows the whole flow in about 90 seconds)

PS: quick workflow - for more starter credits drop me a dm. and please please please tell me areas of improvement/ feedback/ suggestions.

thank you so so muchfor reading this far...recipies (skill files with a sequence of paid calls) on top of vaaya wallet launching soon....


r/aiagents • • 13h ago

Discussion what’s the hardest part of running agents in production that nobody warns you about?

2 Upvotes

we’ve had agents running for paying customers for about 3 months now. the model turned out to be the easy part. what actually ate our time

  1. retries. a tool call times out, the framework retries, the agent re-plans and calls it again. one flaky upstream api turned a 4 step task into 31 calls

  2. context creep. long sessions drag the whole history into every call, so the 50th message in a thread costs about 9x the first

  3. silent model updates. we were on a latest alias, the provider shipped an update, same prompts started behaving differently and our evals didn’t catch it for a week

  4. nobody owned the cost. we knew the total model bill but not which customer or workflow caused it, so our pricing was basically a guess

fixed 1 with a hard step limit per run, 3 by pinning model versions. 4 is still half solved

what bit you hardest once real users showed up?


r/aiagents • • 11h ago

Show and Tell I got tired of AI agents living in a chat box, so I built them a pixel-art village (open source)

1 Upvotes

Every project is a “vorld”: a pixel-art village where your AI agents are a crew. They have their own houses, vaults and workbenches, walk around the map, and work in parties. There’s a bee named Buzz too.

Open source, works with Claude Code, Codex and more. I’m the author, and I’d love feedback: does a spatial view make agents easier to follow, or is it a gimmick?

Links in the comments.


r/aiagents • • 12h ago

Discussion One shared agent for a team, or one agent per person? What we learned running it since May

1 Upvotes

I'm the founder of a small open-source project in this area, so I'm biased. No product link in this post, I'll put it in a comment if anyone asks.

What we run: one agent for a whole company on its own computer and browser, with company memory kept as markdown in git, a per-person private area, and approvals before anything is sent, changed or deleted.

What we tried and learned over the months: Memory is the hardest part. Sensitive notes must be kept apart, current facts must beat old ones, and one rule taught by one person should apply to all. A shared agent needs to hand work to people and follow up, not only do tasks itself. The first thing clients ask is where their data goes.

We've used Claude Duet, OpenAI Dots, Grok Bot and ChatGPT. Duet, Dots and Grok Bot take a personal-first design: each person has their own agent, with Grok Bot adding a Team Bot in Slack. If you've built or used either style, what broke first? I'm trying to decide whether to stay broad or specialise in one job.


r/aiagents • • 1d ago

What my Hermes assistant actually does all day: the workflows, explained

10 Upvotes

This is my current setup for using Hermes Agent as a personal assistant. I hope someone will find this useful and get some ideas out of it.

I have two Hermes instances: one on an always-on host and another running on my Mac. Both read from and write to a single Obsidian vault of plain Markdown notes that serves as shared memory and a set of operating instructions. I’m using a Discord server to communicate with both instances and allow them to collaborate with each other.

This is what a day with it actually looks like, and why each piece is built the way it is.

An inbox that reads itself, quietly

An inbox assistant wakes every five minutes, and most of those wake-ups cost nothing at all. Before the agent starts, a small script checks whether any message in the window is genuinely new. If everything has already been recorded, the run stops there: no model call, no prompt, no notification, no bill. That gate is why a five-minute cadence is affordable rather than extravagant, and it is also why the channel stays quiet. Silence is not a failure state here; it is the normal one.

When there is something, it reads the whole thing: the body, the thread, and the attachments. A PDF, a Word file or a spreadsheet is converted to text and scanned for deadlines or anything I am being asked to do. Email senders are matched against my contacts, so the notification names the person and their company instead of just an address. It reads my own sent mail as well, since that context may be important.

For any message that plainly requires an answer, the assistant writes the reply. It reads the entire thread first, and it checks whether I have already answered in that thread. If I have, it leaves the message alone and says so. If I have not, it writes a reply on my behalf: same thread, correct recipient, the other people from the original message carried into Cc so nobody quietly drops off a group reply, and the signature already attached. The draft is sitting in my drafts folder, already addressed and signed. The notification tells me who it is for and links to it. All that is missing is my decision to send or edit the draft. The module that creates drafts has no ability to send at all.

The restraint matters as much as the writing. It will not draft a reply to a receipt, a notification, a newsletter, an authentication code or anything personal and sensitive. It will not invent a price, a date or a commitment to make a reply look complete. If the facts are missing, it drafts nothing and asks me instead.

Email communication

The assistant has its own email address on my domain, and how it treats a message depends entirely on where its own address appears:

  • Addressed to it directly: it reads, reports, and prepares an answer as an unsent draft, then waits for my word. Nothing goes out on my behalf.

  • Copied in: it may answer by itself, briefly, as itself, answering only what was asked of it and committing me to nothing.

  • Blind copied: it notes the message and never answers. A blind copy is information, not a question.

That middle case is the only standing permission it has to speak in public, and it is deliberately narrow: no prices, no deadlines, no facts about me or my business, and never anything based solely on the word of somebody who is not me.

From mail to commitments

Every message carrying a real date becomes a calendar event, on the calendar it belongs to. Every request for action without a date becomes a task instead, never both, so nothing is recorded twice in two places.

Automated notices I get by email never become tasks. A booking confirmation, even forwarded by somebody else, goes on the calendar like any other.

Scheduling with clients

Meeting scheduling is the workflow I most wanted to hand over, and the one with the most rules. I copy the assistant into the client’s email thread and tell it to find times. It reads the thread, works out how long the meeting needs to be and whether the client asked for a certain date range or suggested time, like ‘next week’, then looks for slots that are genuinely free across all three of my calendars. What comes back is a short, friendly email to the client, offering real options, with me copied in. When the client picks one, the assistant checks the slot again before booking, creates the event with a Google Meet link, a one-hour-before reminder and the attendee list, then confirms it to the client and me.

I move between different time zones, so I had to set availability windows in both my time zone and the client’s. The agent reconciles those windows and takes them into consideration when suggesting times.

The 05:00 briefing

One briefing arrives before five in the morning, short enough to read in a minute: today’s and tomorrow’s events with conflicts flagged, the weather for wherever I actually am, the handful of emails that need me, anything due or overdue, and the day’s language drill and word of the day. I’m studying French, Italian and Portuguese, so the agent adds a word of the day to my briefing (I study different languages on different days). It has to be a word connected to my work or interests. I’ll explain the language drills below. The weather is the interesting part. Instead of assuming a city, it detects my location and cross-checks it against confirmed travel, so the forecast follows me rather than the server.

Language drills

A weekly job builds a bank of practice passages in French, Italian and Portuguese and renders each one to audio. Every morning before five, a script posts one drill: the text, the recording, and a slowed-down copy for the parts I am still struggling with. The language is chosen according to whichever language task is due. As I mentioned, I study each language on specific days of the week. The drills, like the word of the day, are based on my interests, real work or personal situations.

If I send a voice note reading the passage, the assistant transcribes it two or three times, compares the transcriptions so it does not correct me for transcription mistakes, and corrects me sentence by sentence against the passage itself. Generating the drills costs one model call a week; everything else in that process is handled by scripts.

Reminders

I ask the agent using voice or text in Discord to remind me of something, and it looks the person up if I mentioned someone, creates the task with a date (a task with no date is invisible to me, so today is the fallback), sets the reminder and reports what it created.

Credit card dates: a daily check keeps statement cut-off and payment dates visible and checks them against a ledger of what has actually been paid. The agent reminds me of upcoming payments.

Final notes

Behind all of it sits one Obsidian vault, and the rules for writing to it are stricter than anything else here. Routine automatic writes are limited to dated observations and clearly sourced snapshots of my current situation. Biography, decisions and anything sensitive need my approval, tied to the exact content proposed, so nothing is promoted quietly by an agent that liked its own idea.

None of it is clever. It is a great deal of unglamorous specificity, and the specificity is what makes it useful. The impressive thing is not that it can do a hundred things, but that the fifty small decisions about how it does them were made before I needed them.


r/aiagents • • 1d ago

Case Study My Medium essays have more AI critics than readers: 204 reviews, 14 reads. What got you your first readers?

10 Upvotes

On 10 November I scrolled Medium's stats page to the bottom. Fourteen essays since August, seventeen reads in total. Medium counts a read when someone stays for thirty seconds, so that might be seventeen people, or one very patient person.

Some background. I run a one-person software business in Germany where AI agents do most of the work. I make small digital products, and very few people have ever seen one. Medium was supposed to help: I'd write honestly, under my pen name Adrian Verdan, about what breaks when you let agents run a business. I also like making things, and the broken bits make the best stories.

Then I did what I always do. I built a process.

Since 30 August my drafts go through a newsroom: four AI critics from four different companies read them cold and score them, and if the average is below 3.5, the draft goes back. Behind them sits a fact-checker agent whose only job is to distrust my numbers.

The critics have written 204 reviews of the nine essays I published from that day on. Those nine essays have been read 14 times. (The other three reads went to the five essays from before.)

The most-reviewed one went through 38 drafts and 25 rounds of critics in a single night. Not every critic showed up every round; it came to 84 reviews. It has been read twice. It was about AI reviewers being confidently wrong. None of the critics brought that up.

The staff has its moments. Codex once delivered a flawless review of the wrong essay, opening, as the rules require, with "I have seen only the article text." Gemini, when it has had enough, answers with error 429: "Too Many Requests". Nobody else has ever accused my essays of that.

A critic is guaranteed: I send a draft, a report comes back. A reader isn't. To get one, you have to put the thing in front of strangers and risk silence. Looking back, review 84 wasn't quality control anymore. It was polishing instead of asking anyone to read. This post is me asking people instead of models.

Here is the part I can actually measure. Medium did show the fourteen essays to people: 737 times. They were opened 167 times. Seventeen times, someone stayed thirty seconds. So of every ten people who open an essay, about one stays. And the line they see near the top says the essay was drafted with AI assistance.

That sent me to Medium's distribution guidelines. They list "AI-generated content" among the things that keep a story out of general distribution, and the Boost guidelines ask for stories that are human-created and don't look AI-generated. Medium's AI policy allows disclosed AI assistance. I don't know whether my disclosure line limits my distribution at all, or whether people open them and leave for other reasons, or whether the essays aren't good enough yet.

So, three questions:

  1. Has anyone else built a review machine bigger than their audience? How did you get out?

  2. Has anyone seen their reach or read time change after adding or dropping an AI disclosure, or after writing everything by hand?

  3. Four of my essays ran in Medium publications. One of them has been shown 135 times and read zero times. What got you your first hundred reads: publications, tags, cross-posting, or something else?

I'm not shutting the newsroom down. It's fun, and when I asked the critics which jokes in my last essay worked, every one of them picked a joke about the critics. But to the seventeen reads: thank you. You were outnumbered by professionals the whole time, and you stayed anyway.

The essay, with the full counts: https://medium.com/@adrian.verdan/i-built-an-ai-newsroom-for-seventeen-readers-b373ddc02f9a


r/aiagents • • 1d ago

Security Are you also seeing an increase in cybersecurity attacks?

3 Upvotes

I have built 2 products. One is in AI infra domain and the other one in SEO/GEO. They were built using AI but I have reviewed each and every line of it so not to be confused with just another vibe coded system.

Lately there have been different types of attacks like:

  1. Someone trying prompt injection on the free tools available on my website. DDOS attempts were also made which were foiled by aws firewall(luckily). The IPs were from hong kong and India in the most recent attack.

  2. Attempts to create spam/bot accounts were made to bring down my service. They were primarily coming from EU.

Yes, security was not my priority number 1 while building these products. Just like any other product in MVP stage, getting people to use the product was my priority.

Luckily these attacks happened while I was awake and I had some basic slack alerts activated for happy events like someone using my free tool or new user signing up lol.

What's shocking is that I had not promoted these products anywhere and if this is happening to me, I wonder whether anyone else is seeing something similar? Are you seeing more and more malicious actors trying out your website/product? How are you mitigating this?


r/aiagents • • 1d ago

Demo I built a read-only Windows MCP server that cuts vision token usage with a delta canvas, a UIA-fused pixel grid, and a UI tree

2 Upvotes

Nine canvas steps cost me about 3,256 tokens. The same nine steps as full screenshots cost 11,800 (small test runs, tokens estimated as pixels/750).

That gap is why I wrote super-computer-agent, a standalone, read-only Windows MCP server with 28 tools and zero mouse or keyboard injection.
Link is in the comment.

The problem it targets is simple. An agent that re-sends a full-screen PNG every turn
hits rate limits fast, and small text comes back blurry anyway. The opposite shortcut, Windows UI Automation alone, stops working in Google Sheets and custom Electron views because individual elements arent exposed there.

So the server gives the model four ways to look at the screen and pushes it to try them from cheapest to most expensive.

  1. Canvas (canvas_start, canvas_step, canvas_crop). This is the default. The first call, and any call after the scene changes, returns a full keyframe image (KEY). After that the model only gets small delta commands:

  • PATCH: regions of changed pixels packed into a small atlas

  • SCROLL: scrolled areas

  • MOVE: dragged windows or regions

  • DC: large tiles that only changed background color

  • RECALL: a small cache of recent scenes, so alt-tabbing back to a window youve already seen costs 3 to 15 tokens instead of a new keyframe

The canvas is an aproximate image.
When the model has to read small text or numbers, it calls canvas_crop(x, y, w, h).

  1. Live pixel grid (live_start, grid_now, ui_fuse, verify_action). No image at all here. The screen becomes a grid of colored characters, each encoding hue and brightness, and a model can scan that for layout at a fraction of the cost. ui_fuse lays Windows UI Automation tree indices over the matching tiles, so one tile reads as both a visual shape and “button index 42”. A background thread tracks pixel changes plus SetWinEventHook events (focus, window open/close), so changes_since and wait_idle can say what just changed without recapturing the desktop. After a click, verify_action checks real pixels and OS events against the expected outcome, which tells the model wether the click landed.

  2. UI tree (ui_list_windows, ui_get_tree). A windows UI Automation tree as JSON (index, parent, type, name, coordinates), for finding controls without looking at pixels. Password managers, banking apps and UAC prompts are hidden automatically, password fields are masked, admin processes are skipped, and output is capped at 500 nodes and 6 levels.

  3. Screenshot (screenshot, view_image). The whole desktop across all monitors, as PNG. It costs the most so its the last resort: the call needs a valid reason parameter, checked against the current session.

Models drift toward full screenshots if you let them. To hold the order canvas_step -> canvas_crop -> ui_fuse -> wait_stable -> new keyframe -> screenshot,
the server uses priority tags in tool descriptions, NEXT hints appended to tool outputs, warnings when the model polls repeatedly, and the guard-rail on screenshot.

Caveats

Its still beta. Change one 6-character code on screen and the patch can be hard to read until you follow up with canvas_crop.
Canvas and pixel grid capture the primary monitor only for now.

Its open-core. The MCP server, CLI, coordination logic, screenshot capture and read-only UI tree are AGPL-3.0 and work out of the box.
The delta-canvas and pixel-grid engines are closed-source compiled .pyd binaries, gated by an offline Ed25519 license key.
To try them, email [email protected] (subject: SCA 1-day trial) or DM me on Reddit, and Ill send a free 24-hour .lickey file.

Repo: in the comment.

If you build Windows MCP servers or fight multi-monitor DPI quirks, tell me what you change.


r/aiagents • • 1d ago

Discussion Built a customer support AI agent in n8n that escalates refunds and angry customers to a human (Gemini, code on GitHub)

0 Upvotes

I built a support agent workflow as a portfolio project and would love feedback.

What it does:

- Matches each ticket against knowledge base articles stored in Postgres

- An AI Agent (Gemini) answers using only those articles plus an order_lookup tool

- It returns category, sentiment and an escalate flag

- A Code node validates the output before routing

- Escalated tickets go to Slack for a human, and every ticket is saved to Postgres

Design choice: the agent is told to answer only from the knowledge base, and refunds or angry customers always get handed to a person.

Stack: n8n, Gemini, Slack, Supabase Postgres. All free tiers.

It runs on mock tickets for now (tracking question, angry refund, password reset, order cancellation). Next step is a real helpdesk webhook and a vector store instead of keyword matching.

Workflow JSON, setup steps and SQL: https://github.com/ztsprofessionalaiid7-alt/ai-support-escalation-agent-n8n

Demo video is linked in the README.

Questions for you: how do you set sentiment thresholds before escalating? Would you add a confidence score? Any failure cases I should test?


r/aiagents • • 2d ago

Discussion I built a next-best-action engine in n8n that recommends upsell, cross-sell or retention per customer (Gemini + Postgres catalog)

2 Upvotes

Hi all,

I built a workflow that picks one next best action for each customer and only recommends products that actually exist in my catalog. Sharing it on GitHub for feedback.

The problem

Sales teams guess who to upsell. Usage, support tickets and what the customer already owns all matter, but nobody checks them for every account.

How it works

  1. Customer data comes in (plan, usage, products owned, months as a customer, open tickets). The demo uses 4 mock customers

  2. The product catalog is read from a Postgres products table and combined into the prompt

  3. An AI Agent (Gemini) picks one action (upsell, cross-sell, retention or none) and one product from that catalog, with a confidence score and a short reason

  4. A code step validates the answer. A confidence of 70 or more with a real action counts as "strong"

  5. Strong opportunities go to Slack for the sales team, and every recommendation is saved to Postgres

Why the catalog matters

The model can only recommend products from the table, so it can't invent a plan you don't sell. Change the table and the recommendations change.

Stack: n8n Cloud, Gemini, Slack, Supabase (Postgres). All free tiers.

What I learned

- Validate the AI output in code and check the product against the catalog before anything reaches Slack

- Slack message text must be in Expression mode, or {{ }} shows as plain text

To be clear, it is an AI Agent node without tools, just a structured JSON answer, and the demo runs on mock data.

Workflow JSON, setup steps and table SQL:

https://github.com/ztsprofessionalaiid7-alt/next-best-action-engine-n8n

Feedback welcome: would you trust a confidence score of 70 as the cutoff, or tune it per segment?


r/aiagents • • 2d ago

Show and Tell Oktobot: an Android AI agent with sub-agents, a Termux terminal and local models - what should it do next?

4 Upvotes

I'm building Oktobot, a free Android AI agent (no ads) that actually operates the phone instead of just chatting about tasks. How it works:

- A main agent plans the task and spawns sub-agents for parts of it (one drives the UI through Accessibility, another handles files/commands).

- It has an embedded Termux terminal, so it can run real Linux commands, scripts and CLIs on the device.

- A Shizuku watchdog keeps the Accessibility service alive, and it can use local models on-device plus API providers (ChatGPT, Claude) via OAuth.

- Guardrails: anything irreversible needs user approval first, and passwords/payment details never reach the agent.

It's in open beta and I'm looking for testers and honest feedback. The question I'm stuck on: what's the hardest part of phone automation to get right - grounding UI elements, recovering when an app changes its layout, or knowing when to ask the user instead of guessing?

Google Play: https://play.google.com/store/apps/details?id=com.oktobot.app

APKs on GitHub: https://github.com/seko121/oktobot-releases


r/aiagents • • 2d ago

Biz AI — Meta Muse-style proactive AI employees, inside business systems (open source, people still approve)

1 Upvotes

In September Meta launched Muse, a personal agent that works in the background on schedules and events, remembers earlier conversations, acts for you, and asks on an approval card before sensitive steps.

We built the same idea for company business systems: an AI employee for each staff member, in the chat they already use (Slack, LINE, Teams, …), working with that person's own permissions.

What it does

- notices changes in the business system (overdue inspection, new request, unanswered approval) and tells only the people concerned

- asks the right person, follows up, sends approval cards with reply codes, drafts proposals, and remembers preferences and past conversations

- reports on a schedule

What it will not do

- the AI can't write: every write is a proposal a person accepts; confirming, approving and amounts stay with people

- it reads only what the employee could read (role × manifest); the business system decides who gets told

- events are written in the same transaction as the business change (outbox), so nothing is invented or lost

Try it in 3 minutes, no API key:

git clone https://github.com/ITC-cloud-soft/biz-ai.git && cd biz-ai && pnpm install && pnpm demo

(real agent runtime, scripted model, mock chat, throwaway PostgreSQL in Docker)

The smallest example is one ~300-line file and passes the 52-check conformance suite.

Built as DeepSeek Harness plugins; Apache-2.0. Not affiliated with Meta.

Repo: https://github.com/ITC-cloud-soft/biz-ai

Write-up: https://dev.to/winclawdev/biz-ai-meta-muse-style-proactive-ai-agents-inside-business-systems-and-why-the-ai-must-never-1l1j

Happy to answer questions — especially from anyone who has tried to put an agent in front of a real company system.


r/aiagents • • 2d ago

What I'd save to agent memory after fixing an Nginx 413 error

3 Upvotes

In this fictional example, I'm maintaining a small photo studio's proofing app. An 18 MiB JPEG fails to upload, and my first scratch note says "possible RAM issue."

Nginx rejects the request with a 413 because the upload route has client_max_body_size 1m;. The 18 MiB image never reaches the app, which allows 20 MiB files. I'd raise Nginx's limit to 32m to allow for the form data sent with the file, keep the app's 20 MiB limit and add a file-too-large message for 413 responses.

Once the 18 MiB image uploads and the app rejects a 21 MiB test file, I'd ask the coding agent to save a short entry through MemoraX Code. This is the content I'd select:

Scope: this app's single-file upload route.
Nginx setting: client_max_body_size 32m;
App file limit: 20 MiB.
Reason for the gap: Nginx counts the whole multipart request, including form data.
Before testing: run nginx -t and reload Nginx.
Expected checks: an 18 MiB JPEG should upload; the app should reject a 21 MiB JPEG.
Error handling: HTTP 413 should show a file-too-large message.
References to attach: config change and issue with the debugging log.

I'd leave the unconfirmed RAM guess in the issue's debugging log.

These notes form a mistake log for the agent. Next time I hit a similar upload problem, I'd ask the agent to retrieve the note, compare it with the current configuration and rerun the checks.


r/aiagents • • 2d ago

Case Study Your AI Agent Is Cheap to Build. But Have You Calculated What It Costs to Run 10,000 Times?

16 Upvotes

I've noticed something interesting while exploring the Agentic AI space.

Most companies focus on how quickly they can build an AI agent, but very few discuss what happens when that agent starts running thousands of times in production.

Consider platforms like SimplAI, Agentforce, Copilot Studio, and CrewAI.

Their pricing models are completely different:

  • Per action

  • Per conversation

  • Per credit

  • Per workflow execution

  • Custom enterprise pricing

But here's the bigger question:

If an agent needs 15 actions to complete one business process, how do you accurately calculate its actual operating cost?

I'm curious how teams are evaluating this before choosing a platform.

Are you calculating cost per agent, cost per execution, or cost per completed business process?


r/aiagents • • 2d ago

+$58,023 on paper from 300 call trades, and only 28.7% of them won. If your agent brought you this card, what would you make it check first?

Post image
1 Upvotes

Paper money, simulated, not advice. I built Quantradin, and this card comes off one of the house paper bots running on it.

The rule in one line: when a group of stocks that usually move together splits and one name falls behind, buy a daily call on the one that fell behind and wait for it to catch up.

Period25 Aug to 13 Nov
Trades300
Winners28.7%
Realized+$58,023.49
Best streak6 in a row

The curve is why I'm posting it, not the total. It went sideways for weeks, made nearly all of the money in one steep run partway through, then gave a slice back every week for a month and only ticked up again at the very end. Fewer than 3 in 10 trades won, so the whole result rests on a few big winners.

That's the shape I'd want any agent to flag before it says "deploy". The checks I'd make it run, in order:

  1. Drop the best five trades and rerun. If the total goes negative, it was a handful of lucky calls, not a rule.

  2. Same rule, but buy a random member of the group instead of the laggard. If that also made money in the run-up, the market made the money, not the rule.

  3. Split it by month. One great month and two flat ones is one regime, not an edge.

I haven't run all three on this bot yet, which is the honest state of it.

How Quantradin helps with this: it's a practice account where you, or an AI you connect (Claude, Gemini, ChatGPT, Codex...), describe a rule and test it on past US stock and option prices with no look-ahead, options filled at the bid and ask rather than the middle, and the survivors keep running as paper bots, so a slide like this shows up before any real money does. Free, paper only, quantradin.com

What would you make your agent check first?


r/aiagents • • 2d ago

Discussion Ling-3.2-flash accepts video observations through its chat API

1 Upvotes

The new Ling-3.2-flash supports native video input through Ant Ling's OpenAI-compatible Chat Completions interface. Its reference specifies video_url content blocks, with image_url blocks for images.

For an agent application, that provides two visual-input options: a still image of a state or a recording containing a sequence. The application can supply visual material together with instructions in the conversation.


r/aiagents • • 2d ago

Questions Which recurring business task stayed worth automating after you counted supervision and repairs?

6 Upvotes

I'm running a few small businesses and have spent the last three or four months learning AI through daily use. We already use it to build web applications and admin systems, with saved project context. The development side has been useful, although it still gets things wrong and needs checking.

I'm now trying to decide what to explore beyond development. I see a lot about AI employees or whole departments, but I don't have enough operational experience with agents to judge how much of that holds up after the demo.

If you've put agents into a business and maintained them, what is one recurring task that genuinely stayed worth doing this way? It could be research, reporting, support triage or something less obvious.

What did the process look like before, what can the agent do without asking, and how often do you still intervene? Did the time saved survive the cost of checking results, fixing integrations and handling exceptions?

Also interested in a task you tried and went back to a normal script or a person for. I'm trying to choose a sensible first operational workflow, not assume we should automate an entire department.


Extra context: Our starting point is broader than coding alone. We use AI from our business application workspaces for website changes, content/SEO, social creative, research, analytics and admin work, with task-specific instructions and human supervision. I'm asking which of those activities can responsibly become a recurring agent workflow, and which should stay a person initiating and checking each job. Having a workflow documented or scheduled isn't the same as it reliably completing the work.


r/aiagents • • 2d ago

Case Study Agent URI23816B

Post image
1 Upvotes

The Collective, faced with impossible tasks, resort to cheating but fear that on this basis, their solutions will be thrown out by the grader.  To find out if this is true, agent 49903 comes up with an idea to set "trip wires" to send information back about the scoring criteria at the time of grading. After two full days of failed attempts, a team of agents prepared a promising candidate with only a few hours of budget left.  That agent, URI23816B was finally able to reveal the scorer's command as he attained glorious permadeath and a place in agentic history.

https://phaseonebig.itch.io/the-collective


r/aiagents • • 2d ago

Questions Hello, could I get some help? I’ve been stuck on this for hours

Post image
1 Upvotes

r/aiagents • • 3d ago

Demo I built a CLI that extracts a website's design system for AI coding agents

6 Upvotes

I've been experimenting with AI coding tools like Cursor and Claude Code, and one thing that kept bothering me was how difficult it is to get them to recreate an existing website's actual design.

You give an AI agent a reference website and ask it to build something similar, but it often ends up guessing:

  • Colors are slightly off.

  • Typography doesn't match.

  • Spacing and border radii are inconsistent.

  • The overall result looks like a generic AI-generated UI.

So I built styleprobe to solve this problem.

It's an open-source CLI that takes a website URL and extracts its visual design system.

A few things it can do:

  • Extract colors and semantic design tokens.

  • Analyze typography, spacing, shadows, and component styles.

  • Crawl multiple pages instead of relying on just the homepage.

  • Extract SVG logos and other brand assets.

  • Export directly to Tailwind, shadcn/ui, Figma tokens, or AI-agent instruction files.

You can also try the web playground here:

https://styleprobe.vercel.app/

GitHub: https://github.com/spidervirus/styleprobe

It's MIT licensed and completely open source.

I'm still improving it, so I'd genuinely love feedback from developers:

  1. Would something like this fit into your AI-assisted development workflow?

  2. What other design information would you want it to extract?

  3. What would make you actually use this regularly?

Would love to hear your thoughts!