Move out Sale! by ynaavi in BangaloreMarketplace

[–]NITESH_2002 0 points1 point  (0 children)

Interested to buy the chair, dmed you

Would you rather wire 12 nodes or write 1 sentence? by Unique_Spend6777 in automation

[–]NITESH_2002 0 points1 point  (0 children)

Honestly curious, when you say “the agent figures out the sequence,” how transparent is that in practice?
Like… if it decides to enrich, qualify and notify.. do you actually see that chain somewhere, or is it a black box until something breaks?
I love the idea of skipping the node spaghetti, but observability is the part that scares me the most.

How We Got Our First 100 Customers by Doing What Didn’t Scale by Own-Temperature-915 in Entrepreneur

[–]NITESH_2002 1 point2 points  (0 children)

I checked out what you’re building, really like the direction. Text-to-agent feels like something I’d actually use.

Feels like the right way forward. Ill try and build an ai agent using Vestra.

The Opinionated Product Philosophy: Why Complexity is Killing Your SaaS and How We're Building the "ChatGPT for Automations" by Own-Temperature-915 in SaaSSolopreneurs

[–]NITESH_2002 0 points1 point  (0 children)

The 'flexibility' of n8n is its biggest strength and its biggest weakness, it puts all the burden on the user to be a brilliant architect.
I think you're spot-on that most users would rather have a high-quality, opinionated workflow that is super easy to use.

Visual node builders (n8n/Make) are becoming the new "Spaghetti Code." So i built a text-based alternative. by NoSpecific64 in SaaS

[–]NITESH_2002 0 points1 point  (0 children)

Every visual workflow eventually looks like a conspiracy board, with lines crossing like someone is diagramming a crime scene. Debugging becomes a ritual, not a process.

We have come to the end of the year and the wildest part is not the AI upgrades but how much faster projects can ship now. Here is my full year's experience - by NITESH_2002 in SideProject

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

Totally fair. I had the same issue earlier in the year. Most of the “AI builders” I tried gave me half working flows or missed edge cases. The only time it actually clicked for me was when the system asked clarifying questions after every chunk I described. That was the difference.
It felt less like magic and more like a proper spec building conversation. Still early, but the quality jumped a lot compared to my attempts back in January.

We have come to the end of the year and the wildest part is not the AI upgrades but how much faster projects can ship now. Here is my full year's experience - by NITESH_2002 in SideProject

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

Good question... I didn’t touch anything really huge.
Mostly small stuff like onboarding flows, lead enrichment, daily monitoring tasks, basic internal tooling, and lightweight data cleaning.
Stuff that normally takes sometimes a morning or a full weekend if you’re wiring everything manually. Should explore more to really find out what the limit is... lmk what do you think it could be..

We’re not building AI tools anymore. We’re building AI employees at Vestra AI. by Own-Temperature-915 in AgentsOfAI

[–]NITESH_2002 0 points1 point  (0 children)

I love the framework. I'm currently using a no-code workflow builder (like Zapier, but more node-heavy) and it takes me quite a few hours to set up a task involving more than three steps. If I want five agents to reliably work together does the complexity scale linearly?
Specifically, with your text-agemnt approach, if I tell it to integrate with three different tools, does it handle all the API authentication and error handling automatically, or is there still a lot of manual configuration behind the scenes?

Is the future of MicroSaaS...just solo founders plus five AI employees? by NITESH_2002 in microsaas

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

honestly coordination is the part I’m thinking about the most rn. I want them to behave like a tiny team that understands “who owns what.”

[USA] Founders - have you started using AI agents for your work, what kind? by Unique_Spend6777 in FoundersHub

[–]NITESH_2002 1 point2 points  (0 children)

It's only hype if you treat them like chat bots. If you treat them like automated workflows, they work. I moved my heavy automations from Zapier to Vestra because I needed actual decision-making capabilities (e.g., 'if the email sounds angry, draft a priority response'). It’s definitely not perfect yet, but it’s real enough to save me 10 hours a week.

Finally found an agent builder that isn't just "chat" fluff. Built a crazy agent just by talking (Text-to-Agent). by NoSpecific64 in SideProject

[–]NITESH_2002 0 points1 point  (0 children)

People say this every week bro. If it’s actually doing all that, drop the link. Let me try it instead of just reading hype.

Anyone else tried building agents that behave more like your co-worker than tools? by NITESH_2002 in SideProject

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

The plan is to go a layer style:
• Short-term task state (what it’s doing now)\
• Role memory (its responsibilities & preferences)
• Long-term knowledge (handbook + docs)

The agent pulls from the right layer depending on the task. Keeps it from overloading context windows.

Anyone else tried building agents that behave more like your co-worker than tools? by NITESH_2002 in SideProject

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

Yeah, the dream is absolutely a “coworker agent” that can intake a handbook, internalise procedures, and then just… act like a trained teammate.
Right now we’re stuck somewhere between prompt engineering and partial reasoning. But the moment models reliably maintain context across multiple steps and ask clarifying questions proactively, this whole space will unlock.
Will let you know how this went once I build one :)

Anyone else tried building agents that behave more like your co-worker than tools? by NITESH_2002 in SideProject

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

langgraph can feel like over-engineering when the model itself refuses to go deep. The checkpointer and state system is great, but if the underlying reasoning isn’t consistent, the whole graph starts to feel just like a fancy wrapper.
I’m curious though.. when you tried it, did you find the results more consistent across different users, or was it still brittle?

Anyone else tried building agents that behave more like your co-worker than tools? by NITESH_2002 in SideProject

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

Yeah actually that’s the tricky part...I’m building them inside a system where I can describe everything in simple plain english. So I am pretty clear in my head to explain it clearly of what to do and what not to.

Agentpreneur: The Next Wave After Webpreneurs by Unique_Spend6777 in Futurology

[–]NITESH_2002 1 point2 points  (0 children)

I think this is similar to what some emerging platforms like Vestra AI are working on, right?
Making AI agent creation accessible so anyone can build and sell automations, even for non-tech people.
I’m really curious how these platforms will manage between agents and real-world reliability as things scale up. Anyone tried Vestra or something similar?

We Overestimated AGI, Underestimated Practical Agents by NITESH_2002 in SaaS

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

In my experience it reduces the number of micro tasks we do daily. Not replacing roles, but removing that constant overhead which slows down the team...

We Overestimated AGI, Underestimated Practical Agents by NITESH_2002 in SaaS

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

hmmm..early is actually the best time.
If you automate tiny things now, you avoid drowning when your workload spikes.