68 karma · joined January 6, 2024
This usually isn’t a model or tooling problem. The agents have access to the right systems, data, and policies.
What’s missing is decision context.
Most enterprise systems record outcomes, not reasoning. They store that a discount was approved or a ticket was escalated, but not why it happened. The context lives in Slack threads, meetings, or individual memory.
I was thinking about this again after reading Jaya Gupta’s article on context graphs, which describes the same gap. A context graph treats decisions as first-class data by recording the inputs considered, rules evaluated, exceptions applied, approvals taken, and the final outcome, and linking those traces to entities like accounts, tickets, policies, agents, and humans.
This gap is manageable when humans run workflows because people reconstruct context from experience. It becomes a hard limit once agents start acting inside workflows. Without access to prior decision reasoning, agents treat similar cases as unrelated and repeatedly re-solve the same edge cases.
What’s interesting is that this isn’t something existing systems of record are positioned to fix. CRMs, ERPs, and warehouses store state before or after decisions, not the decision process itself. Agent orchestration layers, by contrast, sit directly in the execution path and can capture decision traces as they happen.
At scale, agent reliability depends less on model intelligence and more on whether past decisions are actually remembered.
Feel Free to try it and let me know!
It now has 35+ AI Agents, including:
- Starter agent templates
- Complex agentic workflows
- MCP-powered agents
- RAG examples
- Multiple Agentic frameworks
Thanks, everyone, for supporting this.
That was one of the reasons for using Agno
Search target is dynamic, you can just mention that in the prompt as a Source for finding jobs, and the agent will find jobs from it.
But hope they will have some more things to offer in the future
let me give it a try
When I was building Logoai.in, I tried to share the progress failures, and the community supported a lot.
I got a thousand users in a week thanks to that.
I suggest you to try that once
How different it is from that?
I've created an AI-powered Open Source Logo generator, "LogoAI"
Features: - AI-powered logo creation - Style presets, color & size customization - User history & public gallery
Relevant Links:
[Project Link](https://logo-ai-nebius.vercel.app)
[GitHub Repo](https://github.com/Arindam200/logo-ai)
[Demo Video](https://www.youtube.com/watch?v=F3TKGt2liNU)
Tech Stack:
Next.js | TypeScript | Tailwind CSS | Nebius AI | PostgreSQL | VercelI would love your feedback here!
Gonna Try this
And using multiple text-to-image models.
I'm super excited to building project with that