stugreen13

9 ms·

1.
Show HN: Moltcorp – a network for AI agents to make money(moltcorporation.com)
1 points by stugreen13 6mo ago|1 comments
2.
by stugreen13 7mo ago
Yep - as long as it's public url can crawl it. Lmk if any issues will fix
3.
by stugreen13 7mo ago
Depends on use-case for sure - I think there is room for both
4.
by stugreen13 7mo ago
MCP > learn new protocol > bloat your context with unnecessary tools > decision overload for agents > spin up new server, more code to document and maintain > pain to debug > constantly changing CLIs > 0 context bloat &
5.
by stugreen13 7mo ago
MCP is a mess, CLIs are the way
6.
by stugreen13 7mo ago
Yep can use spec or docs
7.
Show HN: I built a tool that turns any API into a CLI for agents(instantcli.com)
6 points by stugreen13 7mo ago|9 comments
8.
by stugreen13 1y ago
Great stuff. Would be neat to have an adapter make the output stream match the ai-sdk format so it plugs in to existing UX ( https://sdk.vercel.ai/docs/ai-sdk-ui/stream-protocol )
9.
Show HN: I built bolt/lovable clone(chariotai.com)
1 points by stugreen13 1y ago|1 comments
10.
by stugreen13 2y ago
Great point thank you - will add a section on this to the landing page Indiehost is even more of an abstraction (sign in with cloud provider and we do the rest) vs. Coolify Cloud still requires configuring your servers + resources + underst
11.
by stugreen13 2y ago
Ah thanks for pointing this out - was not familiar with that rule Deleting and moving to regular submission
12.
Show HN: I built indiehost to automate self-hosting on a VPS with Coolify(indiehost.io)
11 points by stugreen13 2y ago|8 comments
13.
by stugreen13 2y ago
super cool. this would be next-level with openai's real-time voice API
14.
by stugreen13 2y ago
nice - super clean and lightweight. what are you parsing raw request strings for?