🧵 a bit too late
#env vs. environment vs. context
acoustic tendon
raven bay
yep with the extra verbosity, it does make me wonder if the ability to prepare the env or context ahead of time is that useful.
if I could just prep an llm instead.
llm1=$(llm --model gpt-41 | with-container-input "foo" $ctr "foobar"| with-string-input "string" $str "my string" | with-file-output "file" "my file of stuff")
but of course the env/context is not the bulk of the verbosity, it's in annotation of the with-x-input/outputs.
so env/context and with-env/with-context is just a couple of strings. The bulk is in the rest of the object prep.
quasi leaf
the motivation for having a separate type was a) a clean foundation for mcp support and b) a clean foundation for solving environmental problems shared between LLMs and other clients. For example configuration of default secrets by loading a file
This was in the context of 1) optimism as to a quick MCP server implementation, 2) optimism as to a quick multi-object implementation, and 3) excitement about the ability to sync variables betweem the LLM and the shell