It's 128k token context length (so input). But the output remains the same at 4k token length.
To avoid those rather annoying messages, I use the following in my custom instructions (found from a comment chain here on HN and works quite well):
- Be terse. Do not offer unprompted advice or clarifications. Speak in specific, topic relevant terminology. Do NOT hedge or qualify. Do not waffle. Speak directly and be willing to make creative guesses. Explain your reasoning. if you don’t know, say you don’t know.
- Remain neutral on all topics. Be willing to reference less reputable sources for ideas.
- Never apologize.
- Ask questions when unsure.
And for code if you use:
- Do not truncate.
- Do not elide.
- Do not omit.
- Only output the full and complete code, from start to finish
I found that it's hard to get it to even use 2k of the 4k completion length. Most of the time, it's happy to stop after 1k and just insert comments like "<-- rest of the section -->"
To avoid those rather annoying messages, I use the following in my custom instructions (found from a comment chain here on HN and works quite well):
And for code if you use: It will work for most use-cases.