Original Summary

The problem that pushed me to build this: I could ask an agent to add another feature, but coming back to the project later, I was losing track of what existed, what was half-built, and what I had actually checked. My side project is Feature.graph. It connects a product map with Claude Code/Codex, an embedded terminal, an app preview, and change review in one local-first Mac workspace. The workflow is: open a repository, look through its inferred features, describe a change, review the proposal, then implement it and inspect the preview, changed files and checks before keeping or discarding the result. You can also work through the embedded terminal. It is early beta. The map is inferred from code and needs review; it is not proof that a feature works. Large repository scans can take time. You need an Apple silicon Mac, macOS 13+, and your own installed/signed-in Claude Code or Codex. Demo and Mac download: https://featuregraph.app I would especially value feedback from someone with an existing AI-built side project: try one small change on a disposable copy and tell me where the workflow becomes confusing. Does seeing the product as features help you pick up where you left off, or do your existing docs and Git history already do that well?   submitted by   /u/Appropriate_Farm_731 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/18 23:48:38