Original Summary

I use AI for work that lasts a lot longer than one conversation. After enough weeks of doing that, I kept running into the same problems: - decisions quietly disappearing - old context becoming stale - duplicated work - different AI sessions having different versions of the project - constantly explaining what we already did - occasionally watching the AI confidently resurrect something we'd killed three weeks ago I started solving it for myself by keeping the important project state outside the individual conversation. Current state. Decisions. Evidence. Open work. Authority. Handoffs. Recovery information. That gradually grew into something I call Manager OS (MOS). The “operating system” part is shorthand. It isn't an operating system for your computer and it isn't another AI model. It's a lightweight management layer that sits around the AI and tries to make long-running AI-assisted work more durable and recoverable. Eventually it also grew into coordination between different AI systems, human approval rules, update governance, recovery procedures and regression checks. At some point I realized I had crossed the line from “personal pile of Markdown files” into “possibly an actual thing.” So I'm doing the uncomfortable part now: letting strangers use it. It's free. Public bootstrap: https://www.ijaspers.com/post/manager-os-public-bootstrap-v2026-09-20 GitHub: https://github.com/iJaspers/manager-os I'm not particularly interested in compliments right now. I'm trying to find out whether the problem exists outside my own workflow. If you try it, I'd love three answers: Did you understand what MOS was without me having to explain it? Did it improve a real workflow? What part is confusing, unnecessary, or just plain stupid? If nobody finds it useful, that's valuable information too. If people do, I'll keep building it.   submitted by   /u/ijasperz [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/22 21:47:42