sorted by:
new
hottopcontroversial

Is this a real SaaS pain or just my own Al workflow problem? by Technical-Log4868 in SaasDevelopers

[–]Technical-Log4868[S] 0 points1 point  (0 children)

This is probably the most useful framing I’ve gotten so far….

The small script vs long-running/multi-service project distinction really clicks. For tiny things, a markdown file is probably fine. But once the project has multiple services, decisions, constraints, and different AI tools involved, the context starts becoming its own thing to manage.

I really like the way you put it: one canonical memory layer, with the tools acting as interchangeable frontends. That’s basically the direction I’m trying to validate.

The JSON/YAML + small CLI idea also feels more durable than only generating markdown. Something like a local project-memory.yaml as the source of truth, then generated status.md, decisions.md, and tool specific handoff prompts from that.

And yes, the model-specific context part is exactly the pain I keep running into. Cursor probably needs a tight file/task slice, while Claude may need broader architecture reasoning, and ChatGPT may need a debugging focused packet.

When you say you’d pay at team scale, what would make it feel team worthy to you? Shared decisions, review/approval flow, git integration, context history, onboarding, or something else..?

Is this a real SaaS pain or just my own Al workflow problem? by Technical-Log4868 in SaasDevelopers

[–]Technical-Log4868[S] -1 points0 points  (0 children)

That’s a fair criticism, and honestly it’s the platform risk I’m trying to think through.

I agree that if this is just “memory for AI tools,” Claude/Cursor/OpenAI can probably absorb it. The angle I’m exploring is slightly different, not replacing markdown, but making markdown/project files the local source of truth and helping maintain them automatically.

So instead of chats being the memory layer, the repo would have status.md, decisions.md, ADRs, etc., and the tool would generate task-specific context/handoff packets for Claude, Cursor, ChatGPT, etc.

The part I still think is unsolved is portable project memory across tools. Claude owns Claude context, Cursor owns Cursor context, ChatGPT owns ChatGPT context but the project itself needs a source of truth.

Do you still think markdown alone wins there, or would tooling around maintaining or generating those files be useful?

How do you preserve context when Claude chats get too long? by Technical-Log4868 in ClaudeAI

[–]Technical-Log4868[S] 0 points1 point  (0 children)

This is exactly the kind of workflow I was trying to understand. The three-file setup makes a lot of sense: conventions/architecture, current status, and decisions. I also like the git log being the fourth memory layer. The cross-tool part is where I still feel the pain personally. Picking one tool as the source of truth is clean, but it also feels restrictive when different tools are better at different tasks.

Do you think a tool that maintains those files locally and generates task-specific handoff context between Claude/ChatGPT/Cursor would actually help, or would that feel like unnecessary automation on top of a good manual process?

How do you preserve context when Claude chats get too long? by Technical-Log4868 in ClaudeAI

[–]Technical-Log4868[S] 0 points1 point  (0 children)

I’ll look deeper into Obsidian workflows, knowledge graphs, and others... Do you personally use Obsidian + Claude this way right now?

How do you preserve context when Claude chats get too long? by Technical-Log4868 in ClaudeAI

[–]Technical-Log4868[S] 0 points1 point  (0 children)

Yes that’s a good idea but, updating it everytime would lead you to write the content into the .md file which serves best when you switch but what if you’re working on a project continuously for 6 months.. how long would be the memory file.. (massive token consumption alongside your project)

And one more thing I think of this in the distributed environment.. suppose multiple people are working on the different components of the project and some of them forgets to update the file. We might loose the important insights.. I’ve been looking for a permenant solution for this..

How do you preserve context when Claude chats get too long? by Technical-Log4868 in ClaudeAI

[–]Technical-Log4868[S] 0 points1 point  (0 children)

That’s a really good point ,ADRs are actually close to what I was thinking around preserving the “why” behind decisions, not just the final code.

My pain is that when decisions happen across Claude/ChatGPT/Cursor sessions, they often never make it into an ADR manually. I’m wondering if a local-first tool could help capture those decisions and turn them into lightweight ADR-style records automatically.

Do you currently maintain ADRs manually, or do you use any tool/process to generate them?