Comment by chr15m 2 months ago Good idea. Will figure out a way to do this. 5 comments chr15m Reply benatkin 2 months ago Perhaps instead of writing an llm abstraction layer, you could use a lightweight one, such as @simonw's llm. chr15m 2 months ago I don't want to introduce a dependency. Simon's tool is great but I don't like the way it stores template state. I want my state in a file in my working folder. threecheese 2 months ago Can you explain this decision a bit more? I’m using ‘llm’ and I find your project interesting. 1 reply → khimaros 2 months ago simple solution: honor OPENAI_API_BASE env var
benatkin 2 months ago Perhaps instead of writing an llm abstraction layer, you could use a lightweight one, such as @simonw's llm. chr15m 2 months ago I don't want to introduce a dependency. Simon's tool is great but I don't like the way it stores template state. I want my state in a file in my working folder. threecheese 2 months ago Can you explain this decision a bit more? I’m using ‘llm’ and I find your project interesting. 1 reply →
chr15m 2 months ago I don't want to introduce a dependency. Simon's tool is great but I don't like the way it stores template state. I want my state in a file in my working folder. threecheese 2 months ago Can you explain this decision a bit more? I’m using ‘llm’ and I find your project interesting. 1 reply →
threecheese 2 months ago Can you explain this decision a bit more? I’m using ‘llm’ and I find your project interesting. 1 reply →
Perhaps instead of writing an llm abstraction layer, you could use a lightweight one, such as @simonw's llm.
I don't want to introduce a dependency. Simon's tool is great but I don't like the way it stores template state. I want my state in a file in my working folder.
Can you explain this decision a bit more? I’m using ‘llm’ and I find your project interesting.
1 reply →
simple solution: honor OPENAI_API_BASE env var