> Assistant
Asking well
The quality of the answer tracks the quality of the request. Four things help more than anything else:
- Say what you are actually after. A decision, a draft, a diagnosis, a summary. Different asks want different answers.
- Say what done looks like. Length, format, tone, who it is for.
- Give it the material. Attach the file rather than describing it.
- Say what to leave alone. If there are constraints, they are cheaper to state than to unpick later.
Iterating
The first answer is a draft, and treating it that way is the fastest route to something usable. Say which part is wrong and why: not shorter, but the conclusion is unsupported. Reply to the specific paragraph rather than restating the whole request.
Ocai keeps the conversation, so each reply builds on what came before rather than starting clean.
Answers with sources
When a question depends on something current, Ocai searches and cites what it used. Ask for sources and check the ones that carry weight. See Web access.
If you would rather it stayed inside your material, say answer from these files.
When to stop talking and start delegating
Conversation is the right tool while you are deciding. Once the goal is clear and the finish is visible, hand it over in autonomous mode and let it run. See Modes.
Making it consistent
If you keep re-explaining how you want answers, that is a skill. Write it once. See Skills.
Questions people ask
Why is the answer so generic?
Usually the request was. Name the specifics you care about and the answer changes.
Can I correct it without starting over?
Yes, and you should. Reply to the part that is wrong. The conversation is kept, so your correction carries.
Does it remember previous chats?
It remembers the conversation you are in. For context that has to persist across chats, use a project. See Projects.