shardullavekar

some x.com influencer claiming that they built a one man company with agents doing everything. Like, hey Claude - create a staffing automation company and a swarm of agents search, reach out, follow ups, and AI voice calls etc. Its bs marketing, I get it but "what if this comes true, not now but in future?" - drives the anxiety. The sandwich framework sounds great until the decision and accountability is passed on to AI with guardrails. The AI in its current state is great to take the feedback and decide the next course of actions.

looks great. any plans of abstracting these functions with an LLM integration?

hence the sharability and subscription. other users need to explicitly subscribe to the page boosters. Else they continue with what they have.

users didnt ask for slow apis either but there they are. I am speaking for the user here and sharing their frustration. Allowing UI modification to fit the user needs should be a default now. The APIs already act as a gaurdrail on what's possible

got our extension approved, post which we had no issues.

these embeddable UI could be a direct ask on how users want a workflow, the SaaS vendors can distribute the embeddable UI and see if it clicks with a lot of users. Would push them to create a stable API

> In the end, your obligation as a company, regardless of your product, is to generate profits.

No denying that. SaaS started with a user problem at the center of it and as they scaled, forgot about an individual user. This only presents the user frustration and a possible solution to it.

I think the right step would be to somehow communicate to the vendor that this feature is needed (eliminating the PM backlog BS) and their coding Agents should pick it and build it. The real moat they have is SaaS vendors have everyone believe that trivial feature requests take time to implement.

wondering if all the new browsers in the market have the ability to block such scanning APIs explicitly.

wondering how this fares for languages other than English.