How do I get good answers from very long inputs?
- Put your question after the material, and repeat the key instruction at the end.
- Label sections ("FILE: src/app.ts", "CHAPTER 3") so it can refer to them.
- Ask it to quote the lines it bases its answer on; you can check them.
- Send only what matters. A focused 50K-token prompt often beats a 600K one, and it's cheaper (no 1.5× rate).
- Use Max or Heavy for reasoning across many parts of a long input.
Good to know#
- Not sure which tier?
autolets the product choose per step. What auto does - SuperCosmos answers in your language, including Egyptian Arabic. Languages
- Line Code was retired on Nov 1, 2026; its ids answer
410 model_retired. Line Code retirement
Still need help?#
- General support: support@clatterlabs.com or team@clatterlabs.xyz
- Infrastructure questions, or permanent deletion of your data (your whole account or one service): infrastructure@clatterlabs.xyz
We usually reply within the first hour, and always within 24 hours. A full support team is with you.
Related articles
Still need help?
Tried the steps above and still stuck? Email us. We usually reply within the first hour, and always within 24 hours. A full support team is with you.
Infrastructure questions, or permanent deletion of your data
infrastructure@clatterlabs.xyzFor deleting your whole account or the data of one service.