Auto-included Context Files for recipes

[millsaj]

Please explain the motivation behind the feature request.
Does this feature solve a particular problem you have been experiencing? What opportunities or use cases would be unlocked with this feature?

I have a typst document that I am generating multiple versions of based on some input. I have 1 recipe with 2 sub recipes for this process. It works well but is a little inefficient when it comes to API calls made.

The problem I have is that the required context is larger than I can convey in instructions and prompt.
I have documents the LLM needs to interact with (like a .typ file it will need to edit and then compile) - merging this content into the recipe .yaml would mean loss of important context.

Describe the solution you'd like
A clear and concise description of what you want to happen.

I'd like an extra field in the recipe YAML that allows us to define some file paths to files that will be automatically included (as a separate system or user message).

I'd also expect this to be usable in the desktop and cli interfaces (as well as the yaml)

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

What I have now is I copy the files into a directory and I tell the LLM to read the files. It is okay but is unnecessarily slow.

Another (maybe better) option would be: instead of a list of files; configure a command to run on the recipe startup and before the LLM. Something like this might work.

startup:
  cmd: "python"
  args: ["./scripts/startup.py"]

Additional context
Add any other context or screenshots about the feature request here.

• I have verified this does not duplicate an existing feature request

[DOsinga]

hmm, I am not sure I follow. if we would allow you to include files into a recipe ({% include ... %} gets you somewhere. but if you include the files into the conversation, it will still eat up the context tokens, no?

[michaelneale]

if you don't want it to blow out context - you can just tell it where the files are - a path, and goose will know to read them (and if large will only read portions as needed) but if the content is larger than any context window you don't want to inline it - so I would literally tell it to refer to those files, I do that all the time. like "refer to file xyz.typ when... " etc. it will (now) be smart enough to not eat the whole huge file into the context.

[millsaj]

I wasn't worried so much about the context (in my case I always want to include the full files anyway).

I was more frustrated that whilst I can tell the AI where the files are and it can read those files, doing so requires additional API calls. (Because the AI has to request to see a file that I always wanted it to see).

This takes up the first 3-10 seconds of each recipe run.

Maybe I should just be passing them as parameters and including them as part of the instructions (but I thought it might be too much for one message).

TL;DR yes, the LLM can always just request the files. Just thought it'd be nice to have a way to save it the effort (and me the time).

[millsaj]

Similar to how you can add files to a conversation in cursor or the like and they are included by default in the coversation from the start

[DOsinga]

ah, thanks for the clarification. I can see the use case now.

[DOsinga]

closing because #4558 is merged