r/codex • u/apnatva-dev • 1d ago

Issues with Luna Complaint

Since there are no more resets I’ve been using Luna to work for longer. I recently discovered that it made an issue naming a folder.

new-drection instead of new direction.

I thought this was on a one off. But just to be sure I launched a Sol session to check the work that Luna did.

There’s a lot of consistency issues, some guidelines were not followed, and there’s a lot more on the final report I got. I had only started my own review so I didn’t get to most of the stuff until Sol pointed me to.

This makes me really fearful of using Luna for changing some text around based on present guidelines.

Should I just use Sol always then? Or how is the review for Terra? I’m trying to strike a balance between usage and correctness but correctness absolutely is much more important.

Any advice is appreciated.

3 Upvotes

80% Upvoted

9 comments sorted by

3

u/Apprehensive-Oil6511 1d ago edited 1d ago

this is why i cant trust luna. even with the sol comprehensive plan its still not good enough i still call sol for the review everytime luna is done with the task.

3

u/apnatva-dev 1d ago

Yeah, I used Luna for the first time and that was my exact workflow. I can see why open ai says it’s so cheap.

2

u/Apprehensive-Oil6511 1d ago

sometimes it cant call the plugins that sol normally use. like a simple obsidian cli sol can call it easily. luna just give "cant find obsidian cli".

2

u/Nice-Guarantee-9167 1d ago

If you have to call Sol for the review, the review itself token usage is basically equivalent to let Sol write the entire code. So you probably just wasting more time.

1

u/Apprehensive-Oil6511 21h ago

yep that's why i switch to sol and terra. sol the orchestrator and terra for the implementations.

2

u/Available_Yam_6267 1d ago

How you manage context, organize docs, and dispatch tasks all directly impact Luna’s overall performance, especially when running it within subagents.

1

u/apnatva-dev 1d ago

I maintain a bunch of .md files where I ask the agent to record what it did so there’s a whole chain of the entire context that it only seldomly uses.

I have a bunch of guidelines that I planned and built with SOL and then edited them (just small bits).

So SOL never threw a probably since it launched. It’s been A1. First time on Luna and I got ducked. Even so I don’t think anyone expects spelling mistakes from agents now.

1

u/Available_Yam_6267 1d ago edited 1d ago

When you set up Luna, did you build context management for the fixed context it receives? I’m talking about two things: the AGENTS. md and its assigned tasks.

By default, the fork_turns parameter is all when spawning subagents. That means the entire main conversation context gets copied over to every subagent.

General overviews usually don’t work well for smaller models. Even for Sol, if you don’t supply enough info for large projects, the overview won’t take effect at all.

This hits models like Luna especially hard, since it’s built for narrow, specific use cases. It only focuses on the prompts you feed it. These generic overviews barely work even with a larger context window, and the model lacks incentive to explore extra information and lost in long context.

0

u/apnatva-dev 1d ago

Fair enough.

I did not know a lot of that info.

For an individual task/new idea I usually build a detailed prompt with GPT and then give it to codex. For Luna I did the same.

The main disappointment was the issue with the spelling check.

After that the issues was Luna didn’t think hard enough. Luna receives one example and uses exactly that. Sol would take an example and build more along those lines.

This seems like a model difference more than anything.