 if an Oak CLI is running the program normally. Neither seem very elegant, and I'm waiting to see what I need and prefer in usage before committing to an API change.</p><p>It would also be useful to be able to include assets other than <code>.oak</code> source files in the packed binary, so that I can include assets when building and distributing a web server written in Oak, for example. Go does this using compiler pragmas (<code>//go:embed</code>), which Oak itself uses to include the Oak standard library 