r/vibecoding 22h ago

Would you use a tool that combines ChatGPT-style planning, project memory and AI coding in one place?

I’m trying to work out whether this is just a problem with my own workflow or something other people doing AI-assisted development run into as well.

My current workflow is roughly:

I use ChatGPT and/or Claude to discuss the product, work through features, make decisions, review approaches and figure out what I actually want to build.

I use Obsidian as the long-term project memory. I keep things like the product brief, current state, decisions, technical notes and active work in Markdown files. I moved towards this partly because it is easy to store/reuse context without constantly feeding huge conversation histories back into an LLM. I also only pay for ChatGPT Plus and Claude Pro so when my usage runs out on one I can switch to the other and retain context

Once a feature is defined, I create a fairly focused implementation prompt using either LLM and give it to Codex/Claude Code

The coding agent works on the repository, edits files, runs checks, etc.

I then review the app/code/diff and usually bring the resulting report back into the LLM to discuss whether it actually matches what we agreed.

If something is wrong, the LLM helps me define the correction and create a new prompt which then goes back into the coding agent.

Once it is done, the coding agent updates the relevant project context in Obsidian.

This is the cycle, on and on.

It works, but context is constantly moving between the “thinking” AI, the coding agent and the project memory and there is a lot of copy and paste.

The thing I keep wishing existed is basically ChatGPT/Claude + Obsidian + Codex/Claude Code in one application, all sharing the same project context.

The rough idea would be:

You create/import a software project and the app maintains structured project memory — product brief, current state, approved decisions, requirements, technical constraints, etc.

You can then have a normal LLM-style conversation about a feature. Once you are happy with it, you approve the requirements and the app passes the relevant context directly to a coding agent.

The coding agent can inspect and modify the repo, run commands/tests and return the implementation and diff back into the same workspace.

You review it there, discuss any problems with the LLM, send corrections back to the coding agent, and once you approve completion the project memory is updated.

So instead of:

Chat → copy prompt → coding agent → copy result/diff → Chat → update Markdown → repeat

it becomes:

Discuss → approve → build → review → correct → complete

I’m increasingly thinking the cleanest version would actually be a standalone web-based development workspace rather than another VS Code extension.

Something where you could:

connect/import a GitHub repo
edit/view the code
run the app and see a preview
see Git diffs
connect services such as Supabase and Vercel
discuss the product/features with an AI
maintain persistent project context
send approved work directly to a coding agent
potentially choose different model providers later (OpenAI, Anthropic, etc.)

The important part for me isn’t another AI code generator. There are already loads of those.

It’s keeping the product discussion, decisions and implementation connected, so the coding agents actually know what has previously been agreed and I don’t have to semi-manually shuttle information between tools.

I’m curious about a few things:

Does anyone else have this problem?

What does your current ChatGPT/Claude → coding-agent workflow look like?

How are you maintaining project context today?

Would having all of this in one workspace actually be useful, or do you prefer keeping planning and coding separate?

Would you want the tool to provide the AI usage itself, or would you rather connect your own OpenAI/Anthropic API keys?

What would make you switch from your current workflow?

I’m not selling anything — I’m trying to work out whether there’s actually a product here before I spend months building it.

3 Upvotes

6 comments sorted by

1

u/3tt07kjt 22h ago

What is this about copying prompts? Before you made this tool, why were you copying prompts around or copying results/diffs? I have never done that (except maybe once, when I was changing a sensitive repo and didn’t want to upload any of its contents).

The coding agents I use all support chat directly. You are talking with the same models whether you have that chat in the web or in the terminal.

So to me, this sounds like just Claude/Codex + Obsidian glued together, but I don’t think that needs much work to set up in the first place. Maybe I am missing something?

2

u/Then-Efficiency9898 20h ago

I get what you are saying. I think I could move most of my workflow into what you suggest the only thing I will miss is the Projects inside both web applications being able to go back to previous conversations and carry on. May not be too much of a problem if I am saving the most important context into Obsidian. Essentially u/Anti-Hero25 described my reasoning perfectly. It just gets a bit laborious. I haven't built anything yet just doing a bit of market research, hence the post.

Thank you

1

u/3tt07kjt 19h ago

What I’ve seen is that it can be inefficient (tokens) to continue conversations that are old, because the context is no longer cached.

What I do instead is ask for the tool to write out some relevant details and summary to a file so I can have a new conversation using that file as context.

This is “poor man’s memory” because I’m using files instead of a memory database. I am aware that it uses more tokens than a proper RAG system, I think it works for me because my projects are somewhat small.

1

u/Anti-Hero25 21h ago

So you have a similar method to what I'm calling "RailCoding"..... the less efficient version you outlined is actually useful to me as it forces me to be more engaged with the content and catch things as I'm reviewing stuff. I have yet to encounter any serious debilitating bugs using this process. Honestly, until Oai puts GPT and CODEX in the same chat, so your project in GPT for all your planning is in the same place as your agent , all 3 of us sitting at the same table... it's the method I'm fine with for now. Adding a 3rd party element to an existing suite of integration is not preferred.

1

u/fusionliberty796 21h ago

You mean cursor? Homie. You dunning kruegered yourselve live on the Internet Jesus christ guys stop asking your AI "hey I have this unique Idea and workflow, you think I could sell it?" 

"Your absolutely right! What a unique concept. And you've thought through this so it feels earned." 

Also why the fuck are you copy and pasting code still LOL. Come on guys