MySetup.ai: Mapping the Evolving AI Builder Stack

Mysetup.ai is a new community platform designed for builders to share and compare their AI development workflows. It was created to help engineers navigate the overwhelming variety of new tools, agents, and techniques like graph engineering. By documenting these setups, the author hopes to foster a space where everyone can learn from each other's experiments and progress.

Key Points

• The rapid pace of AI development and new concepts like graph engineering can feel overwhelming for builders.
• There is a lack of a dedicated space to see the full workflows and systems behind how others are building with AI.
• mysetup.ai provides a platform for engineers to share their specific toolsets, agent harnesses, and governance layers.
• The community aspect helps users realize they aren't alone in still trying to figure out the best AI configurations.
• The platform encourages transparency and collective learning through shared, up-to-date setup profiles.

Sentiment

The overall sentiment is cautiously positive but skeptical. HN agrees with the article's core premise that real AI workflows are worth studying and that builders are hungry for concrete setup details, but the community is wary of unsafe contribution flows, narrow platform assumptions, and the incentives around exposing hard-won workflow knowledge. The strongest support comes from people who immediately shared setups or asked for better ways to browse them; the strongest opposition comes from people who object to account/tool access, distrust MCP-based submission, or believe AI workflow knowledge should remain private.

In Agreement

• A dedicated hub for AI setups is useful because the most valuable knowledge is how tools, agents, prompts, and habits fit together in practice.
• Concentrating setup information in one place can be more useful than scattering it across social posts, source repos, and one-off forum threads.
• Detailed examples from practitioners show that AI workflows can involve meaningful engineering choices around local tools, security, model routing, quality checks, and long-running agent work.
• The creator's responsiveness to feedback, including adding manual contribution options and search features, made the project feel actively maintained and more useful.
• The site can help users discover approaches they did not know to look for, especially in a fast-changing tooling environment.

Opposed

• Requiring or foregrounding MCP-based contribution makes the site feel unsafe or self-selecting, especially for users unwilling to connect external tooling or accounts.
• Plain text, GitHub repos, HN or Reddit threads, or a transparent local collector may be simpler and more trustworthy ways to share setups.
• AI workflows may be too personal, stack-specific, and fast-changing for copied setups to remain useful without freshness metadata and strong filtering.
• Some developers view private AI workflows as competitive advantage or job security and therefore see public sharing as economically risky.
• The product needs broader coverage and better discovery, including search by tool, hardware, local setups, cost, images, and update recency.