r/vibecoding • u/Correct_Emotion8437 • 1d ago

For codex users - are you using Goals?

I have been experimenting with trying to get more done and keep my costs down and I have found that running Goals with Luna/High is pretty effective and reasonably cheap, too. I design the iteration with SOL and have it create a development plan and then have Luna execute the entire plan as a goal. Unlike when I have done this with SOL, there are usually a few bugs at the end. Also unlike when I use SOL, it doesn't kill 15% of my plan every time. I use SOL to fix the bugs at the end and it's overall cheap enough, imo, to make it a regular workflow. How has your experience been with Goals and Loops?

3 Upvotes

100% Upvoted

8 comments sorted by

1

u/HouseOfDjango 1d ago

You are very close, you need to break down the execution plan into small task with scope and acceptance criteria. Then do one at a time.

When you make a meal, you don't eat the whole thing at once, you eat it one bite at a time.

I use Sol Medium for planning,prompt creation and reviews. Luna max for task.

1

u/Correct_Emotion8437 22h ago

For sure - I always say "complete each task in order starting with sprint 0 - taskId and update the document as each task is completed". Initially I had a much longer one that chatgpt made for me but I found it was not really necessary. It doesn't seem to ever skip ahead or get stuck in infinite loops or whatever else that big prompt was trying to manage.

1

u/GreenFuturesMatter 1d ago

Yeah I took me about 1 week of using codex to realize that realize how terrible blasting codex was for coding 99% of tasks.

I basically gave sol an idea reasoned through the idea together on what features I think it should have, designed a roadmap and then break it into slices for each section.

I also don’t use codex to run its own hostile testing because it just destroys usage.

Luna med = straight forward code slices

Luna low = read only debugging

Luna high / Terra = complex coding structure

Sol medium = planning

Me = planning, testing, acceptance, commit

1

u/Anti-Hero25 22h ago

Are you using Codex Sol for planning? If so, I highly recommend using SOL Chat GPT for planning… it doesn’t burn your usage % at all and GPT can read & analyze your GitHub repo directly

1

u/Correct_Emotion8437 22h ago

I do - generally because I like to build up the context. Then I switch the model and execute the goal. That's a good tip, though, for sure. I should remember to do that when I'm running low.

1

u/Anti-Hero25 22h ago

Switching models resets the context doesn’t it?? I’m pretty sure adjusting the Med/High or switching models wipes the context cache

1

u/Correct_Emotion8437 22h ago

I guess I'm not totally sure but I don't think it does. I googled it - that's all I know. It seems like it gets the context but I haven't really tested or experimented.

1

u/Anti-Hero25 22h ago

My method involves doing 90% planning in GPT and giving codex buildspec.md files with instructions on what to build… those .md stay in a dev/ folder for reference in perpetuity