[pona-a]

Maybe you can hack some context management and hidden state with custom functions? The scratch buffer can literally be an endpoint that returns OK and has a field like "plain: list[str]", assuming it keeps function call data in memory. Better context memory can be done perhaps by reminding in the system prompt to always call getPinned() each 5 messages, perhaps...

But yes, the whole thing does seem bound to regress to low-quality "I'll enter 1/5th of your request in for you". You can probably even make a script that uses GPT-3.5 to generate these "GPTs".

[ianbicking]

Yeah, you can definitely do a lot with Actions, and I've seen some examples of that. But if I want to deploy a service then I'd rather make a nice frontend along with it, and Custom GPTs aren't that! (But the fact I don't have to monetize just to support OpenAI API costs is still very appealing.)

At the moment Actions are pretty brutal to the experience, with constant confirmations and they seem to halve both the speed and the quota since I think it takes two GPT responses, one to assemble the Action and another to react to the result. Using a Custom GPT that uses extensive actions means sitting and watching it think, waiting to hit a button, then sitting and watching it think for a long time, only to run out of quota before you get to anything interesting.