[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3gaiio40nwd70":3},{"code":4,"message":5,"data":6,"timestamp":67},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":31,"summary_md":32,"topic":33,"github_topics":36,"license":57,"homepage":58,"updated_at":59,"history":60},"macro-inc\u002Fmacro",5,"Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.","Rust",4904,476,33,350,[16,22,27],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},48546561,"Show HN: Macro – unified system for email, chat, tasks, docs, agents (AGPL\u002FRust)",8,1,"2026-06-15",{"id":23,"title":24,"points":8,"comments":25,"posted_at":26},49169254,"Macro: Unified email, messages, docs, tasks, agents, CRM for teams",0,"2026-08-04",{"id":28,"title":29,"points":20,"comments":25,"posted_at":30},49309321,"Macro is a unified workspace for teams","2026-08-15","面向小团队的 All-in-one 工作台，用一个 @ 互链的系统取代 Slack、Notion、Linear、邮箱和 CRM 的拼装组合。","## 解决什么问题\n\n小团队的工具栈是一堆各自为政的优秀产品：聊天、文档、任务、邮箱、CRM 谁也不认识谁，只能靠 Zapier、MCP、复制链接硬连起来。结果是「为什么做这件事」到「谁做完了」这条链路断在原地。Macro 的做法是把这些界面全部重建在同一个后端上，共享一张双向关联图，人 和 agent 共用团队级记忆。\n\n## 有什么不同\n\n常见路线是分别买 Slack、Notion、Linear 再粘起来，或者选一个本质是文档工具加数据库的轻量「全家桶」。Macro 的核心主张是每个界面都为自身场景专门设计，但共用一张图：邮件可以在文档里被 @ 引用，任务能从频道消息一键创建并追溯到关闭它的 PR，CRM 联系人可以直接在收件箱里查。第二个差异是 agent 被当作一等成员，拥有跨工作区的检索能力——README 举例说 agent 可以直接搜从邮件里解析出的 PDF 附件，而不是先翻邮件线程。第三是任务刻意做轻、贴着聊天走，直接押注「专用 issue tracker 不如轻量任务」这一判断。\n\n## 适合谁\n\n大约 10 到 50 人、被五六个 SaaS 的集成成本折磨、愿意把整个公司搬进一个产品里的创业团队最合适。工程驱动的团队尤其受益，因为聊天和任务天然挨着代码链接。反过来说，已经在 Jira、Salesforce 或几百个集成的 Slack 工作区里沉淀了深度定制流程的团队应该避开：它的卖点是整合，把一个成熟流程迁进年轻产品恰恰是反整合。需要私有化部署的团队要先确认自托管方案再决定。\n\n## 上手成本\n\n这是整个工作台的替换，真正的成本在迁移和重新培训，而不是安装。技术栈是 Rust 加 SolidJS，AGPL-3.0 许可：内部自用没问题，但如果你想嵌入或换皮发布就会受限。项目很年轻（2025 年 11 月创建），README 更像产品导览而非部署文档，自托管细节、数据导出保证、API 稳定性都得去翻官方文档；版本控制等功能明确标注为 v1。\n\n## 点评\n\nMacro 是一个全新项目而非成熟项目：约 350 天、4,902 star，只在趋势榜上出现过 2 天，本周 +202 star。这说明有初期关注，但还谈不上被验证的增长曲线，唯一一条 8 分的 Show HN 帖子也说明受众仍小。但「邮件、聊天、文档、任务、CRM 共用一张图」确实抓住了工具碎片化这个真问题，一个 ~15 人团队两年的自用，比 star 数更有参考价值。把公司的操作系统押在它上面，意味着接受 AGPL、承担迁移成本，以及承受一个年轻产品随时变化的风险；建议先在一个团队里试用，别一上来就全量搬迁。",{"slug":34,"name":35},"productivity","效率与系统工具",[37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56],"agent","ai","ai-agents","all-in-one","crm","crm-system","email","linear","mcp","messaging","notes","notion","office","rust","slack","slack-alternative","startup","startup-tools","typescript","workspace","AGPL-3.0","https:\u002F\u002Fmacro.com","2026-10-25T00:05:37Z",[61,65],{"date":62,"stars":63,"stars_gained":64},"2026-10-24",4902,32,{"date":66,"stars":11,"stars_gained":13},"2026-10-25",1792901804]