Clean prompt composition

[ilyaZar]

Hi

first, thank you very much , this is a cool project

I wonder what your thoughts are , and if thats worth exploring more deeply atm or rather not

implement:

would a user-configurable prompt order / composition layer/interface be aligned with the project direction assuming current defaults remain unchanged ?

motivation:

the idea is that behaviorly nothing would change atm at the defaults (so nb. gets mad): just the interface gets more flexible for users to play around with re-ordering prompt parts if they wish so

the reason I’m asking is that prompt assembly order seems mostly fixed; I would, e.g., move the user prompt at the very very top above context/visual selection, files, rules

for sending large contexts, it might be suboptimal to sandwhich the user prompt in between other stuff; it wouldnt be the usual way to interactively prompt opencode , so maybe it shouldnt be the way the prompt is sent over to the very same harness (assuming behavior is equal in both cases; I would be surprised if not but have never checked that tbh)

also, prompt compositin/order could be dealt with (rather ...) independently from what has been outlined in #144 , session ID support or changing opencode serve -> opencode run , if I understand the codebase correctly

I saw a couple of comments in the code around prompt context classes ("prompt should generate its prompt via prompt() instead of passing it into the provider as a string..." in the TODO)

should one try to work on this ?