https://docs.all-hands.dev/ logo
Join Slack
Powered by
I would love a review on these 2 PRs: - <https://g...
# proj-agent
m
c
Totally a side note: could you fill in the HUMAN: section - a sentence or two will do, or as much as you’d like
As we’re moving forward, I’d love it if we can feel the structure of the prompt as it’s forming
m
Yes. Give me a moment. I will answer in github
c
Thank you! Sorry, I read but I still have a few questions. One I haven’t added to an issue is if we have considered breaking down the sections in separate jinja files, just to see them and to be able to overwrite them, if that makes sense? I'll look for where this question belongs 😂
m
One I haven’t added to an issue is if we have considered breaking down the sections in separate jinja files, just to see them and to be able to overwrite them, if that makes sense?
I think this will come down to constructing a registry, right? Because you will need some code to manage these pieces.🙂
JFYI: the migration will be just one line in the future. For now, the idea is to write the code to make it happen. That way, we can experiment and think about what the right structure is to meet all our needs.
@calm-artist-7206 This is the continuation https://github.com/OpenHands/software-agent-sdk/pull/3659 So you can see how it will be the sistem prompt. Theoretically, instead of hardcoding the section in the code, we could also use jinja files. We can always change that. the structure is already in place. What do you think? Is there a feature or something that push for jinja?
❤️ 1
c
I tend to think jinja files are much more approachable for people thinking to customize their prompts. It's difficult to explain, I feel strongly that viewing a folder with e.g. 
memory_section.j2
will immediately map to my brain. It feels easy
I'd give it a little thought and brb in a bit
m
We can have the section saved in jinja file perhaps... my point is: do we want the user to be able to override just one section or the user have to rewrite the whole prompt? Moreover, I really want something easy to understad with a clear structure which is easy to test. And which permits us to change the system prompt very dinamically and do AB-testing
nod 1
But I think the register thing is good because we have a really nice overview on what is going where. For instance, I put the web_broswer tool indication too high in the static part and these should go in the dynamic one 😞
c
Left a tiny question on both
m
Answered on the one for dynamic context 🙂
2 Views
Open in Slack
PreviousNext
Powered by