Getting help: what to include so the answer is one reply, not five

[VladoIvankovic]

Ask anything here — setup, providers, a command that did not do what you expected, a model that behaves oddly. Questions are answered in the open so the next person with the same problem finds the answer instead of asking again.

Four lines make the difference between one reply and five:

codeep --version
node --version

• Which provider and model you were using (/provider, /model)
• What you ran and what happened — the exact command and the output, not a paraphrase
• Your OS — macOS, Linux, or the Mac app rather than the CLI

If it looks like a bug rather than a question, open an issue instead — issues get tracked to a fix, questions get answered.

Before asking, these cover most of it:

• Installation — including what to do when codeep is not on your PATH
• Providers — keys, endpoints, and which models each one exposes
• Approvals — what the agent asks permission for, and why
• Prompt caching — usually the answer to "why is this costing so much"

One thing worth saying plainly: never paste an API key here. If a log line contains one, replace it before posting. A key in a public thread is a key you have to rotate.