r/AISystemsEngineering • u/shrapknife • 58m ago
r/AISystemsEngineering • u/Ok_Significance_3050 • 1h ago
Multi-Agent vs Single Agent for Workflow Automation: Where Did Extra Agents Hurt You?
Has anyone tried building agentic workflows with OpenClaw and found that adding more agents actually made the workflow slower or harder to manage?
I’ve been exploring AI agent orchestration and noticed an important trade-off between single-agent and multi-agent approaches.
For simple tasks, a single agent often works better. It can handle a request, use the required tools, and complete the task without too much coordination.
Multi-agent systems make more sense when tasks require different skills. For example, one agent can collect information, another can review it, and a third can prepare the final result.
But adding more agents also creates challenges:
More communication between agents.
Higher usage costs.
Longer response times.
More complex debugging.
Greater difficulty maintaining shared context and memory.
I think the best approach is to start with a single agent and introduce additional agents only when there is a clear reason.
I’m curious about your experience:
Have multiple agents improved your workflow or made it more complicated?
Do you prefer predefined workflow steps or flexible agent loops?
How do you control cost and latency when several agents work together?
Would be interested to hear what has worked and what has failed in real implementations.
r/AISystemsEngineering • u/shrapknife • 19h ago
Adding intelligence to intelligence
reddit.comr/AISystemsEngineering • u/Feeling_Future_9571 • 21h ago
Looking for people in Dehradun interested in AI/ML and Computer Science!
reddit.comr/AISystemsEngineering • u/Consistent-Ad3558 • 1d ago
I got tired of AI agents that keep your API keys and logins on the same box the agent runs on. So we built it the other way.
reddit.comr/AISystemsEngineering • u/Few-Ad-1358 • 2d ago
For people running AI agents in production, what’s the actual cost of wrong or outdated information?
reddit.comOne thing I’ve noticed is that agents can give answers that look totally fine, even with real sources, but still miss the mark because the info is outdated, something key was skipped, or the source doesn’t quite back the claim.
I’d love to know how much this pops up for folks running agents in real setups, beyond the usual chat about hallucinations.
Here are a few things I’m curious about:
Time: How much effort goes into double-checking answers, fixing slips, or tracing where an agent went astray?
Cost: Do retries, extra LLM calls, or checks noticeably bump your API bills?
Engineering overhead: Have you built your own checks, logs, or approval flows just to keep agents dependable?
Memory and context: Have you seen agents stick with old info or overlook fresh facts?
Real impact: Have these hiccups caused delays, unhappy customers, lost sales, or other headaches?
I’m also keen on what tools you’re using: do guardrails, evaluation setups, or monitors handle it, or are you still doing lots of manual review?
I’d especially love to hear about real cases, even tiny ones: what went wrong, how you spotted it, and how much work it took to sort out.
I’m looking at this from an engineering angle and trying to gauge whether it’s a big hurdle in production or something teams have mostly tamed.
r/AISystemsEngineering • u/Few-Ad-1358 • 2d ago
For people running AI agents in production, what’s the actual cost of wrong or outdated information?
reddit.comOne thing I’ve noticed is that agents can give answers that look totally fine, even with real sources, but still miss the mark because the info is outdated, something key was skipped, or the source doesn’t quite back the claim.
I’d love to know how much this pops up for folks running agents in real setups, beyond the usual chat about hallucinations.
Here are a few things I’m curious about:
Time: How much effort goes into double-checking answers, fixing slips, or tracing where an agent went astray?
Cost: Do retries, extra LLM calls, or checks noticeably bump your API bills?
Engineering overhead: Have you built your own checks, logs, or approval flows just to keep agents dependable?
Memory and context: Have you seen agents stick with old info or overlook fresh facts?
Real impact: Have these hiccups caused delays, unhappy customers, lost sales, or other headaches?
I’m also keen on what tools you’re using: do guardrails, evaluation setups, or monitors handle it, or are you still doing lots of manual review?
I’d especially love to hear about real cases, even tiny ones: what went wrong, how you spotted it, and how much work it took to sort out.
I’m looking at this from an engineering angle and trying to gauge whether it’s a big hurdle in production or something teams have mostly tamed.
r/AISystemsEngineering • u/kevinlu310 • 2d ago
7 Things That Break AI Agents in Production
reddit.comr/AISystemsEngineering • u/jeffhonforloco • 2d ago
A user tested my AI platform and caught an interesting problem.
r/AISystemsEngineering • u/bailbondslocal • 2d ago
What tends to break first when you put autonomous AI agents into real business workflows
reddit.comr/AISystemsEngineering • u/SlowDocument8115 • 2d ago
Are there any good books for Agentic AI / system design for AI ?
reddit.comr/AISystemsEngineering • u/Educational_You2257 • 3d ago
Key Value Database for AI workloads
Hey everyone,
I'm building Thunder, a high-performance key-value database designed for workloads where latency, throughput, and efficient resource utilization matter.
With AI applications, we're seeing increasing amounts of data being generated, stored, and retrieved. I wanted to explore whether we could build a database from the ground up that handles these workloads more efficiently, rather than simply relying on larger amounts of RAM.
The core idea is simple: use RAM intelligently, not excessively.
Thunder is being built in Rust with a few architectural decisions:
Shard-per-core architecture: Each core owns its data, minimizing contention and synchronization overhead.
Asynchronous I/O: Uses io_uring on Linux to take advantage of modern NVMe storage.
Minimal RAM overhead: Keep essential metadata and indexes in memory while streaming data from storage through reusable buffers.
Zero-copy wherever possible: Reduce unnecessary memory copies and allocations.
Custom storage engine: Designed around efficient allocation, fragmentation management, and predictable performance.
High concurrency: Handle large numbers of concurrent operations without relying on traditional locking across the entire database.
The long-term goal is to support both small, latency-sensitive operations and large data workloads without requiring enormous amounts of memory.
It's still under development, and I'm experimenting with different approaches to storage, indexing, caching, and I/O scheduling.
I'd love to hear from people building AI infrastructure or working with large-scale key-value stores.
What are the biggest bottlenecks you're facing with your current databases? Is it memory consumption, read latency, write throughput, storage costs, or something else?
Also, what would you expect from a new key-value database built specifically with AI workloads in mind?
Docker link: https://hub.docker.com/r/sbansal793/thunderstrike
r/AISystemsEngineering • u/CrashTestingAI • 3d ago
Multi-Agent AI Testing: Test the Whole System, Not Just the Agent.
r/AISystemsEngineering • u/aantenore • 3d ago
Agents sharing knowledge: I built git-style branch/merge for the facts they read. Real problem or am I overthinking?
r/AISystemsEngineering • u/sonichigo-1219 • 4d ago
Coding agents can open a passing PR, but go blind once it hits the pipeline. What do your agents see after the merge?
r/AISystemsEngineering • u/Ok_Significance_3050 • 4d ago
Replacing IVR With a Voice Agent: What Edge Cases Surprised You?
We're evaluating voice AI for contact centers, and one thing I'm particularly interested in is what happens after the initial demo.
A voice agent might sound natural, understand common questions, and handle basic call routing. But integrating it with an existing CRM, telephony system, and legacy contact center software seems to be where the real challenges begin.
For example, what happens when a customer changes their request halfway through a call, interrupts the assistant, has multiple issues, or needs to be transferred to a human agent with their conversation history intact?
Traditional IVR systems are limited by predefined menus, but they are generally predictable. Voice agents offer more flexible conversations, although that flexibility introduces new edge cases.
A few things I'd like to understand from people who have implemented these systems:
CRM integration: How do you maintain customer context when a voice agent transfers a call to a human representative?
Intent recognition: How well does voice AI handle customers who explain multiple problems in one conversation?
Legacy systems: Have you experienced problems connecting AI voice platforms with existing SIP, PBX, ACD, or contact center software?
Conversation quality: How do you handle background noise, interruptions, accents, unclear speech, and long pauses?
Fallback handling: What happens when the AI cannot understand a request or an integrated business system becomes unavailable?
Testing before launch: What do you include in your readiness checklist before allowing a voice agent to handle real customer calls?
I'm also curious which platforms people are considering in 2026. What has mattered most in practice: natural conversation quality, low latency, STT accuracy, CRM integrations, telephony compatibility, or reliable human handoffs?
For those who have replaced or supplemented traditional IVR with voice AI, what unexpected failure or edge case taught you the most?
r/AISystemsEngineering • u/nbortolotti • 4d ago
We dropped internal ticket resolution from 4 days to 4 hours—not by making our AI agents smarter, but by applying basic OpEx first.
reddit.comr/AISystemsEngineering • u/Groundbreaking_Ad154 • 5d ago
AI Customer Driven Development
reddit.comr/AISystemsEngineering • u/Powerful_Feed_2391 • 5d ago
Why is achieving accurate product recommendations harder than simply implementing RAG in an eCommerce AI agent?
reddit.comr/AISystemsEngineering • u/FinderLearner93 • 5d ago
Would you want a tool that shows leadership where your AI workflow is inefficient?
Honest question for people who build and run agent or LLM workflows. If something measured cost per useful result and flagged where your workflow wastes money or needs rework, would you want that visible to leadership, visible only to your team, or not at all? What would make it feel like help instead of an audit? For context, I’m a founder exploring this problem.
r/AISystemsEngineering • u/Mother-Side6477 • 5d ago
Design notes: a local shared memory for multiple AI agents, built around provenance and poisoned writes
I built Monomem, an open-source (MIT) shared memory that several coding agents use at once (Claude Code, Cursor, Codex and others). Here are the design decisions, for anyone building something similar.
Storage. One SQLite file, using Node's built-in SQLite with FTS5. It needs Node 22.16 or newer: Node 23's bundled SQLite has no FTS5, so no 23.x works. Two direct runtime dependencies. It binds to loopback by default.
Provenance is server-side. Every note's writer is stamped by the server from the authenticated key, never from the request body. Keys are scoped read, write or admin, can be limited to one namespace, and have a sensitivity ceiling (public, internal or private). Above the ceiling, a note looks to that key like a note that doesn't exist.
Write path. Every write goes through a check that refuses secrets and holds text matching prompt-injection patterns. A held write goes into a quarantine queue a human approves, and agents never read quarantined text. On 189,502 real chat turns, it held 21 and refused 27.
Read path.
- Every MCP read carries an untrusted-data banner and a "who wrote this" block.
- An admin can distrust a writer per namespace, and its notes are filtered out of every read path. Nothing is deleted.
- An agent's "forget" archives the note. Only a human can delete permanently.
- Each note keeps 20 earlier versions by default, configurable up to 500.
Session-start context. Candidates are ranked by fusing BM25 keyword hits (from the git branch, changed files and recent work), file overlap with uncommitted changes, and recency. The result is packed into a token budget (1,500 by default). Pinned notes come first. A session summary whose session read web or other-server content is named, but its text isn't injected.
Retrieval numbers (retrieval only, no LLM judge, so not comparable with vendors' answer-accuracy scores):
- LongMemEval-S: recall@5 of 96.6% with keyword search, 2.8 ms p50. Hybrid search with a local embedding model reaches 98.5%.
- LoCoMo-10 by turn is the weak spot: 57.8% keyword, 66.3% hybrid.
Security regression gate. 129 deterministic scenarios run in CI: 0 of 38 poisoning probes and 0 of 51 permission-leak probes get through. npx monomem drill replays 23 attacks on a copy of a real store. Two known misses stay open: a reworded override, and a trusted agent writing an attacker's instruction in its own words.
Known limits. An agent with shell access can open the database file directly. Real isolation needs a separate OS user owning the data folder, which is documented in SECURITY.md.
Repo: https://github.com/calasdan-sketch/monomem
I'd like critique on the trust model, especially from anyone who has done taint or provenance tracking across agent memory. Thanks!
r/AISystemsEngineering • u/bailbondslocal • 5d ago
What's actually working (and what isn't) when small teams give AI agents recurring ops work
r/AISystemsEngineering • u/Downtown_Grab_2704 • 5d ago
Start to Learn FDE need your tips Please
Working currently as an ai Solutions engineer
The weird and sad fact is that i didnt work with LLM
Only created things like SaaS apps with docker Web extensions i know there's a big gap between this role to fde role i need your help by give the roadmap to fde technologies, deployment and the customer side