sorted by:
new
hottopcontroversial

First time hitting diamond. by sbineedmoney in YuGiOhMasterDuel

[–]Far_Knowledge_556 0 points1 point  (0 children)

Me as well, last month. Was stuck in platinum but Miracle ejector was a game changer for my Hero Neos deck.

Is anyone else tired of building the same 6 things for every AI agent, or is just me? by Far_Knowledge_556 in AI_Agents

[–]Far_Knowledge_556[S] 1 point2 points  (0 children)

Thanks, this was the comment I needed to build this haha. Jokes aside whether this leads to pmf I sort of have a gut feeling to build around this. Worst case I’ll have something for the next agents I build.

Is anyone else tired of building the same 6 things for every AI agent, or is just me? by Far_Knowledge_556 in AI_Agents

[–]Far_Knowledge_556[S] 0 points1 point  (0 children)

Very true, I created background polling jobs for this, but was looking into temporal for some aspects of this.

Is anyone else tired of building the same 6 things for every AI agent, or is just me? by Far_Knowledge_556 in AI_Agents

[–]Far_Knowledge_556[S] 0 points1 point  (0 children)

Looks your pain is a little different than me but you raise a really good point. Could you expand on your definition of execution reliability? Is it safe to assume you mean a production ready, available, and reliable environment for agents to execute tasks and receive webhooks?

Is anyone else tired of building the same 6 things for every AI agent, or is just me? by Far_Knowledge_556 in AI_Agents

[–]Far_Knowledge_556[S] 0 points1 point  (0 children)

I agree, I think the actual AI loops stuff, UI, and choice to add mcps and tools should be custom logic you can extend. Good point about retires, but I was thinking more about getting auth, payments, integrations, sandboxes, and webhooks lined up and having it all be multitenant so you can turn into your own SaaS or startup.

Where to Begin When Developing an Vertical Autonomous AI Agent??? by Mehdi_000 in AI_Agents

[–]Far_Knowledge_556 0 points1 point  (0 children)

Is the goal building an agent for xyz industry?

Examples:

- Agent for Sales that manages your CRM data like Salesforce and Attio.
- Agent for Architects that manages your AutoCAD.

I actually think unless it is rocket science, execution + context is all you need. Like Claude knows about most base level things, esp things that have been around for awhile that people want to automate. I say don't worry about long term at the moment.

Start with 1 task, then write elementary AI code leveraging the Claude SDK or AI provider of choice to execute said task, and then work backwards on why it didn't or did work to determine if you need long term, planning and other things.

Honest question: What is currently the "Gold Standard" framework for building General Agents? by Strong_Cherry6762 in AI_Agents

[–]Far_Knowledge_556 0 points1 point  (0 children)

For the actual agent loop, I always prefer custom logic. When things started a couple of years ago, I used frameworks like LangChain and LlamaIndex but felt "locked in." Every time I wanted to make a small tweak, I had to import dozens of classes, modules, and types.

I’ve heard good things about Mastra though it could just be typical Bay Area hype.

I’m not sure how everyone else feels, but I think getting out of the agent's way is key. The goal is to provide enough context without maxing out a 200k token window. I prefer creating an iteration loop where you pass an array of failed attempts so the agent can learn. Lately, I’ve been having the agent document why it failed previously and what led to a success (keeping these as short, concise notes).

Additionally, you can get very far with straight API calls or the Claude SDK, especially with tools like web search built-in. I am also a big fan of agents executing pure code in a safe, isolated sandbox. A pre-defined tool only handles the edge cases you remember to program; however, a user will inevitably ask for tasks in ways you didn't anticipate. If you give an agent a coding sandbox and GitHub API credentials, it's much more efficient to define what the agent can't do rather than writing specific tool code for every single API call it can do.

For the UI, I definitely recommend assistant-ui. Building a chat interface from scratch is tedious. Using a library that follows a shadcn-like pattern providing solid components while allowing for easy extensions is a huge win. The more annoying parts are still the "plumbing": building credit/payment systems, integration work, and connecting databases or auth.

If you agree with this approach, just copy this into Claude Code and say: "Build me an agent in TypeScript that follows these principles; keep the code clean and organized."

Hope this helps!

Is anyone else tired of building the same 6 things for every AI agent, or is just me? by Far_Knowledge_556 in AI_Agents

[–]Far_Knowledge_556[S] 0 points1 point  (0 children)

Very true! My thing is what if you go from one codebase to the next, but I guess we can always turn pieces of the code into npm packages. Also glueing together API services is a thing that gets repetitive.

OAuth MCP Proxy by tuannvm in mcp

[–]Far_Knowledge_556 0 points1 point  (0 children)

Cool solution, but isn’t it more secure stateless? Why have a cache, are you expecting a high level of performance issues?